Forward Deployed Engineer, Maps Client Qe Intelligence

Apple Apple · Big Tech · Cupertino, CA +1 · Software and Services

This role focuses on building and deploying AI-native tooling for the Maps Client Quality Engineering organization. The engineer will work closely with users to understand their workflows, identify pain points, and translate these insights into tools that improve triage, release readiness, test automation, and root cause analysis. The role emphasizes end-to-end ownership, from discovery and build to ship and adoption, with a focus on making AI capabilities a consistent and supported part of daily workflows. The engineer will partner with various teams including QE leads, SDETs, SWE platform teams, Maps Eval, Release Engineering, and Apple's AI/ML platform organization.

What you'd actually do

  1. Stay close to the users. Build a working understanding of how a triage lead handles a presubmit session,how a release readiness review runs, where SDETs lose time on flaky tests. Earn that understanding through review attendance, shared channels, and one-on-ones — not by waiting for a spec.
  2. Choose what to build. The most consequential decision is what to take on next. Most ideas will not make the cut. Picking well — and being willing to drop work that is not landing — is the core of the role.
  3. Build end-to-end. Python services (FastAPI, aiohttp), Next.js, and TypeScript front-ends, RAG pipelines, agents, and MCP integrations. End-to-end includes auth, deployment, observability, and the rollback path.
  4. Make sound trade-offs. Choose between scope, speed, and quality under release pressure. Adjust plans early to protect delivery rather than late to explain a miss.
  5. Stay hands-on in the code. Read and review across services and front-ends. Step in directly when progress or clarity depends on it, even on code you do not own.
  6. Stay with the work after launch. Adoption is the deliverable. After a release cycle, the question is who is using it and how often. If the answer is no one, you go back and find out why.
  7. Generalize what works. Patterns proven in the field become shared building blocks — agents, skills, MCP servers, and services that other tools depend on. You own that path back to the platform.

Skills

Required

  • Python
  • TypeScript
  • FastAPI
  • Next.js
  • LLM API usage
  • RAG pipeline debugging
  • end-to-end production software shipping
  • engineering judgment in scoping
  • working from observation

Nice to have

  • Forward Deployed Engineer experience
  • Solutions Engineer experience
  • Applied AI Engineer experience
  • internal tools engineer experience
  • developer experience engineer experience
  • MCP servers
  • agents
  • RAG systems
  • QE background
  • developer tooling background
  • internal platforms background
  • test infrastructure background
  • XCTest
  • XCUI
  • Apple-internal engineering platforms
  • vector database

What the JD emphasized

  • 5+ years shipping production software end-to-end
  • Strong Python and TypeScript
  • A specific, recent example of a tool or feature you built that another team picked up unprompted
  • A specific, recent example of a feature you decided not to build, and the reasoning behind it
  • Comfort working from observation rather than from a written spec
  • Working knowledge of LLM application building
  • You can describe one time you removed or retired a feature you personally built, because adoption did not justify keeping it

Other signals

  • AI-native tooling
  • AI adoption
  • evaluate emerging models, agents, and tooling patterns
  • harden the ones that prove out into reusable building blocks
  • graduate field-tested work back into the platform
  • applied AI experience
  • LLM application building
  • shipped something using an LLM API
  • debugged a retrieval-augmented system