Build build/release infrastructure and dev tooling for Lyft's mobile engineers

This is a mid-level iOS-focused engineer role on Lyft's Mobile Tooling team, building build and release infrastructure — including Bazel-related tooling and CI — serving hundreds of internal mobile engineers, plus early AI agent workflows for developer productivity. Expect questions on developer tooling design, CI/build performance, and internal product sense.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Mobile build/release infrastructure at scale (Bazel, CI pipelines)
CLI tooling development in Python/bash
Native mobile testing practices (unit, snapshot, UI)
Cross-functional project management and stakeholder alignment
Product sense for internal developer tools
AI/agentic workflows for developer productivity (bonus)

Common question themes

How would you diagnose and fix a slow iOS build in a codebase with hundreds of modules

Describe a developer tool you built end to end and how you got engineers to adopt it

How do you approach maintaining a CI pipeline that needs to stay under 15 minutes

Tell me about a Bazel or build-system challenge you solved

How would you prioritize tooling work based on feedback from internal engineers

Have you built or used AI agent workflows to speed up code migrations or reviews

How candidates describe it

Real iOS Tooling Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Lyft interviews