The role
As a Senior Mobile Engineer, you will help lead the development of the mobile apps, support and mentor your teammates, and help drive technical decisions that impact performance, security, and user experience. Your expertise will be key to ensuring the app’s smooth operation, as well as its scalability across different devices and platforms. We don't hand seniors a queue and assign tickets — we expect you to lead yourself, your tasks, your initiatives, and your projects, and to take them to the finish.
You'll work across verticals — Trading, Onramp/Offramp, Onboarding, Explore, Core, Seeker — and across boundaries with Backend, Web, QA, Product, Design, Data. You'll mentor teammates and drive technical decisions that change how performant, secure, and lovable the app feels.
Core responsibilities:
- Drive continuous improvement. Look for what can be better — in the code, the process, the product, your own workflow — and act on it without waiting for permission. An engineer who works the same way after a year as they did on day one isn't doing this job.
- Reason from first principles. Question inherited assumptions before reaching for the convenient answer. Argue ideas hard, then commit fully when another path wins on its merits.
- Own the outcome, not just the code. Watch crash reports. Read store reviews. Notice when the app feels slow on a mid-tier Android. The job ends at the user, not the merge button.
- Make pragmatic trade-offs. Decide when to over-engineer and when to ship the ugly thing. Hold opinions about tech debt without moralizing about them. Make the call, document the trade-off, move on.
- Treat the codebase as a product. Write code that other engineers — and QA automation — can read, test, and change safely. Structure, naming, and testability are part of the deliverable, not afterthoughts.
- Use AI as a force multiplier, not a crutch. Lean on AI tools for the work that doesn't need a human brain — scaffolding, refactors, test stubs, exploration. Reach for agent-style workflows when the task warrants it. Review AI output with the same rigor as a junior engineer's PR. (We already do this in production — our release reports are AI-generated and reviewed by humans.)
- Communicate in writing. Document the tricky bits in Notion. Explain decisions async. If it only lives in your head or in a Slack thread, it doesn't exist for the team.
- Stay current with the platform. Track WWDC, Google I/O, and the broader mobile ecosystem. Bring ideas back. Keep the app from aging out.
Requirements:
- 7+ years of mobile experience. You've shipped, broken things, and learned from both — and you can run your own work without needing it queued up for you.
- Deep mobile fundamentals. A strong grasp of how mobile platforms actually work — lifecycle, memory, threading, networking, storage, rendering.