About the RoleSpam Blocker identifies unknown callers, blocks spam and scams, and screens suspicious calls before they ring. It's a consumer product operating at the intersection of mobile platforms, real-time calling, and Hiya's global reputation and security systems.
The team is small and owns Spam Blocker end to end, from the native apps and backend services to subscriptions, entitlements, and releases. We don't split work by platform. Engineers move between Swift, Kotlin, and the backend depending on what the product needs.
You do not need equal depth on both platforms. We are especially interested in engineers with deep Kotlin and Android expertise who have already shown they can cross technical boundaries, and who want to become productive on both. The team has strong iOS depth today; this hire adds Android depth and works across both. If you want to spend your career inside one platform's toolchain, this is not the team. If you want to broaden what you can own, you'll have the room and support to do it here.
As a Senior Mobile Engineer you will ship features across both apps, own releases, and raise the team's engineering bar. This is an AI-native team. Coding agents carry much of the routine implementation, and part of the job is deciding where they help, where they do not, and building the tools and guardrails that let the team ship safely with them.
What You'll Do- Design, build, and ship features across the iOS and Android apps, including the backend changes each feature needs
- Own releases from cut to store on both platforms, and extend the release automation so it needs fewer people and catches more before it ships
- Build the tests, instrumentation, and review gates that let a small team ship at high quality without a manual QA pass
- Drive architecture decisions on the mobile codebases and see them through to adoption
- Work with product and design to decide what we build, and bring a point of view on whether we should build it at all
- Use coding agents where they create leverage, and improve the tools, guardrails, and workflows that let the team ship safely with them
What We Are Looking For- Demonstrated Kotlin Multiplatform experience in production applications. Specifically shipping shared KMP code, or deciding where a shared boundary belongs.
- Production code shipped outside your primary platform in the last two years, on iOS, backend, or web, that you can show us. Shipping on both iOS and Android is a strong plus
- Experience carrying a significant architecture or platform change through a mobile team, from proposal to adoption, including bringing other engineers along
- Comfort in the services behind the app: APIs, entitlements, analytics. You do not wait for a backend engineer to unblock a mobile feature
- A high quality bar with automation as the default. You build automation around repeatable failure modes and use device testing deliberately, for the things only a device can tell you
- Active use of AI coding agents. You separate planning from execution on non-trivial work and can say what has worked, what has not, and where you draw the line on trusting an agent's output
- Clear written and verbal communication. You write clear PRs and design notes, and you flag blockers early
- Pragmatic judgment. You make sensible tradeoffs between speed and quality and can explain why
You'll Likely Stand Out If You Have- Experience with Compose Multiplatform
- Experience with CallKit or the Android telecom framework
- Experience building companion experiences for CarPlay or Android Auto, or for watchOS or Wear OS
- Experience with in-app subscription platforms such as RevenueCat
- Experience with mobile CI/CD and release tooling such as Bitrise or Runway
*This is a hybrid role with 3 days per week in-office in Seattle