About the Role
We’re looking for mobile engineers across experience levels, from strong mid-career engineers to seasoned senior and staff-level builders, who can build reliable, scalable mobile experiences with strong attention to usability, performance, offline realities, edge cases, and production robustness. We value engineers who think beyond screens and understand how mobile systems behave in real operating conditions.
Senior engineers here have outsized impact: you’d shape architecture decisions, mentor other engineers, and own critical subsystems end to end.
What We Are Looking For
- 5+ years of mobile engineering experience (Android, iOS, or cross-platform)
- Ability to build reliable, scalable mobile experiences that work in real-world conditions
- Strong attention to usability, performance, and offline-first design patterns
- Experience handling edge cases that are common in field operations, including poor connectivity, device diversity, and battery constraints
- Production robustness mindset: you think about crash handling, graceful degradation, and monitoring
- Comfortable working closely with product designers, backend engineers, and operations teams
- Experience with logistics, field operations, or enterprise mobile apps is a strong plus
- For senior/staff candidates: experience leading technical direction, mentoring engineers, or owning a platform layer
What Success Looks Like
In the first 6 months, the strongest engineers here ship meaningful work to production consistently, become dependable in at least one core area of the product, and understand the operational workflows behind the features they build. They start owning a subsystem or product surface with increasing independence. Senior engineers are expected to influence technical direction and raise the bar for the team.
The Environment
Product decisions are tied to operational reality. Engineers are expected to understand workflows, not just APIs. Documentation, reviews, instrumentation, and iteration matter. Delivery is visible and predictable. Speed matters, but not at the cost of judgment.
Non-Negotiables
- Understand the problem before coding.
- Care about edge cases, offline scenarios, and production robustness.
- Collaborate well with design and backend teams.
- Maintain code hygiene across naming, structure, testing, and documentation.
- Accept critique without ego.
- Ship iteratively and measure impact.