Software Engineer, Dev Environments

The Dev Environments team sits within Door Dash's Foundations group (Platform Engineering). We own the local and remote developer experience across the Door Dash group of companies supporting over 5000 engineers. Our mission is to enable engineering velocity, quality, and efficiency at significant scale by removing friction from the day-to-day developer loop: spinning up a working environment, getting code building, and getting feedback fast, whether the  developer  is a human or an AI agent.

As a Staff Engineer on Dev Environments, you'll be recognised as an expert across the dev environments space, covering both local and remote dev flows, devcontainers, IDE/remote backends, and how they all fit together, including owning accountability for outcomes that span multiple teams. You'll set technical direction for the team's roadmap, unblock deep cross-cutting technical problems other engineers can't resolve alone, and mentor senior and mid-level engineers.

You'll partner closely with engineering leadership across the group to translate ambiguous, company-wide developer-experience problems into a concrete, sequenced technical strategy.

Technical direction

• Define the architecture for how thousands of engineers across Door Dash, Wolt, and Deliveroo actually develop and ship code: local and remote dev containers, remote IDE/VM lifecycle, and the full local-to-remote loop.

• Build monorepo dev tooling 's part of consolidating all the companies under Door Dash’s umbrella onto one global backend - you're setting the standard, not patching one org's tooling.

• Provision production-shaped environments in seconds, keep state in sync over the network, and make a remote machine feel local, reliably and cheaply, at thousands-of-concurrent-engineers scale.

• Expect to invent as much as you adopt: much of this is genuinely unsolved elsewhere in the industry.

• Design for AI agents as first-class consumers of the environment, not an afterthought: sandboxes that spin up on demand, run in parallel, and are safe to handle a real repo.

• Support agents launched from an IDE, a CLI, or a Slack message – with no laptop required to review and ship what the agent did.

Collaboration & leadership

• Align teams that don't naturally sit adjacent to each other (e.g. Security, Infrastructure, Product Engineering) around unstructured, ambiguous problems where there's no existing playbook.

• Mentor engineers at all levels: run design reviews; raise the engineering bar through code review, pairing, and architectural guidance when appropriate.

• Help set the hiring bar: lead interview loops, help calibrate, and support onboarding of senior hires.

Essential:

• A track record of shipping production systems and leading cross-team initiatives with group level impact – comfortable owning delivery end to end, from design through to production and adoption.

• Hands on fluency with the languages and tooling used to build developer tooling (e.g. Go, Python, Type Script) and infrastructure-as-code (Terraform).

• Experience managing compute via Kubernetes (multi-tenant workload isolation, autoscaling, cost management), or lightweight VM/sandbox technology (e.g. Firecracker).

• Working knowledge of cloud networking, including securely and cost-effectively routing traffic across network boundaries (VPNs, service meshes, etc.)

• Experience integrating LLM/AI tooling into developer workflows – e.g. Claude Code – both locally, and remotely.

• Excellent written and verbal communication; able to influence senior stakeholders and align multiple non-adjacent teams without formal authority over them.

• Experience building close working relationships with the engineering teams who consume your platform, not just the platform team itself.

Nice to have:

• Experience in developer platforms or adjacent infrastructure: devcontainers, remote development, remote IDE backends, or developer workstation tooling.

• Practical experience with Jet Brains remote-backend flows, Code spaces/Code server-style products, or equivalent.

• Experience with remote build/execution systems (e.g. Build Buddy), or large-scale build caching.

Solve meaningful problems at real scale…