Your devices are lost. They have no network connection. Find My locates them anyway, using a crowd-sourced network spanning nearly a billion Apple devices worldwide.
Making that work at this scale, reliably and without compromising anyone’s privacy, is the engineering problem. You’ll be building the interfaces people actually touch.
We operate as an independent team inside Apple: small, autonomous, and accountable end to end. You’ll own what you build, from the early design conversations through production.
Our roadmap changes. A capability lands, a threat model shifts, a partner team reprioritizes, and the plan from six weeks ago is now the wrong plan. We rewrite it. If you need a stable twelve-month backlog to do your best work, this will frustrate you. If ambiguity reads as opportunity rather than risk, you’ll like it here.
Priorities and the problems worth solving are given. How they get solved is largely yours to figure out. We’re looking for people who take a goal and run with it, and who push back when the goal looks wrong.
You’ll work directly with designers and product managers to turn requirements into something people can use, and with the back-end engineers whose services you’re building on. Managing those dependencies without letting quality slip is part of the job rather than an afterthought.
We build in React and TypeScript, containerize with Docker, and review everything on GitHub.
The work is on-site in Malmö, Sweden. You’ll need to be here, or willing to move here. Working language is English, written and spoken
Minimum Qualifications
- Enough production experience that you’ve shipped something to real users and lived with the consequences. We care about the depth, not the number of years.
- Deep JavaScript, not just framework fluency. The event loop, async semantics, the module system, memory and rendering behavior in the browser. We’ll ask you to explain a decision you made at this level.
- Professional experience with React, TypeScript, and modern CSS. We care more about depth in the platform than allegiance to a framework. A keen eye for user experience and interaction design. You can tell when a design won’t survive contact with real data, and say so early.
- You’ve debugged something that only reproduced on a real device, a slow network, or under real data volume. Comfortable consuming REST APIs and reasoning about failure, latency, and partial data as first-class UI states rather than edge cases.
- Proven experience building and maintaining complex single-page applications: state management, data-heavy views, and the performance work that keeps them fast, including code splitting, lazy loading, and render cost.
Preferred Qualifications
- Familiarity with modern web platform capabilities (WASM, WebGPU, canvas rendering, browser security model) is a bonus.
- Accessibility is part of your definition of done, not a later pass.
- Back-end familiarity, particularly Java, is useful, since you’ll be working closely with the services team.
- Experience in cross team collaboration and communication across multiple timezones
- Able to work in an ambiguous and highly interdependent work environment to get things done in an efficient and tactful way
- Ability to thrive in a multi-functional team on high-profile, critical projects
- You read the source of your dependencies when the docs run out.
- You test what you ship, and you’re comfortable with CI/CD tooling and full automation testing.
- Strong communication, written and verbal You can explain a technical decision to engineers and non-engineers alike, write a design document others can follow, and hold your position in a discussion without needing to win it. Much of this team’s work is decided in writing and in the room, not in the code.