Senior Mobile Engineer

About the role

This is a build-from-the-ground role. You'll own the mobile app end to end. The native shell, the native functionality, the embedded web views where they make sense, and the Rails APIs underneath. The "I'm blocked waiting on my endpoint" dynamic doesn't work here. The person who owns the screen owns the API behind it. You’ll work with another paired engineer and PM/design partners to build on mobile over time. Part of the job is leaving behind patterns for platform library usage, web views, release, and on-call, so everyone can move fast. You’ll ship every week, own what you ship in production, and set the standard for how mobile gets built at Tern.

Why Tern?

• Tern is building the platform travel advisors run their entire business on, and we believe the next great aggregator in travel gets built right now, on AI.
• We're growing the engineering team this summer to put fuel behind what's already working.
• This role owns a real part of how Tern works. Mobile is a net-new surface for our advisor product and you'll define it.
• We hire engineers with high agency and the trust to execute independently, set direction through their work, and lift the standard of everyone around them.

What You'll Do

• Own the advisor mobile app end to end including the native shell, hybrid surfaces, embedded web views, and the Rails APIs behind them
• Get a usable app into advisors' hands as soon as possible by shipping working pieces every single week along the way
• Build and extend the Rails APIs the app depends on, rather than waiting for someone else to spec them
• Iterate on the foundations the team will live with by developing the build and release pipeline, app store process, crash reporting, and on-call for mobile
• Establish the hybrid and web-view patterns that two advisor pairs and a new designer can build on
• Watch your app in production and catch issues before advisors do

What You Have Shipped

• mobile ownership: You've personally shipped a mobile app to the App Store and/or Play Store and kept it healthy after launch. You have real stories about what broke in production and how you fixed it for good.
• Full-stack range: You're comfortable writing the backend and the screen. You've built or extended the APIs your app consumed, and "blocked on my endpoint" isn't a phrase you reach for.

Bonus Points

• Comfortable in Ruby on Rails or a comparable MVC backend
• Experience standing up a mobile app and its release process from zero
• Background at a smaller company or startup where you owned a product surface end to end
• Built consumer or pro-tool apps where reliability and polish mattered