Engineering Manager, Mobile Developer Experience

Location: Northern

# Engineering Manager, Mobile Developer Experience Door Dash  USAUSAToday## Continue with your CVPDF, Word, or image. Under 10MB.Apply now## Job description

Engineering Manager, Mobile Developer Experience at Door Dash USA.### About the role

This role defines and maintains the foundational systems that enable Door Dash Mobile engineers to perform cess means empowering engineers across Door Dash, Wolt, and Deliveroo to build, ship, and operate with confidence.

About this type of role Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code.

The ability to explain a technical decision in plain words separates strong engineers from the rest.### Key facts
*
* Location:

** San Francisco, CA;
Sunnyvale, CA;
Seattle, WA;
Los Angeles, CA;
New York, NY
** Engagement:
** Cross-functional collaboration with product and engineering leadership
** Team:
** Mobile Developer Experience (Mobile Foundations) and international growth
** Years:
** 7+ years of hands-on software development, 3+ years leading engineering teams
** Degree:
** Bachelor's degree or equivalent practical experience
** Visa:
** Candidates in NYC or remote roles associated with NYC offices are subject to Covey Scout assessments under NYC Local Law 144### What you'll doiOS and Android monorepos are managed and optimized as core horizontal infrastructure pillars.

Data-informed decisions are championed and continuous improvement is driven across the Mobile Developer Experience team.

Industry best practices guide teams through ambiguity, with a clear understanding of when to innovate or adapt.

Technical trade-offs are communicated clearly to executives, and technical strategy is mapped across teams for alignment.

Cross-functional initiatives are led to align teams and disciplines around high-impact outcomes.

The team is built, sustained, and grown to address the expanding needs of the organization.### Requirements7+ years of hands-on software development and expert proficiency in either Android or iOS development are required.
3+ years of experience leading engineering teams is required.

A strong bias for action, pragmatic problem-solving, and deep technical expertise must be demonstrated.

Proven success leading cross-functional initiatives with measurable impact is required.

The ability to dive deeply into low-level detail and know when that depth is necessary is required.

A deep understanding of how to build quality software while balancing delivery of customer value is required.### Practical notes

Confirm details on the official apply page.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer.

Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know Mobile developer experience focuses on tools, processes, and infrastructure that remove friction for engineers.

Quality, velocity, and efficiency are core pillars that guide decisions for platform and toolchain design.

The role works across multiple brands and regions, requiring clear communication and cross-team alignment.

Engineers use native mobile languages alongside monorepo tooling to build and ship features.

Data-driven decisions and continuous improvement practices are central to the team's responsibilities.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.

Apply now
#J-18808-Ljbffr