BoodleBox
Senior Native Experience Engineer — iOS & Android
Remote
·
Full time
Company website
You have apps in both stores under your name, and you can tell us exactly why each got rejected once and what you changed. You're strong in Swift or Kotlin and genuinely productive in the other. You've owned signing, CI, the store submission, and the 2am crash spike by yourself, and you didn't need a second mobile engineer to tell you what to do. You think tablets are their own thing, not a stretched phone. BoodleBox has native iOS (Swift) and Android (Kotlin) apps whose first versions are in app-store submission right now and keep getting rejected. We hope they're approved by the time you start. They might not be. Either way, you take ownership of both codebases as our first dedicated native engineer: get them through review if that's still needed, make mobile delivery dependable (CI, crash monitoring, release health, recovery when rollback isn't instant), and then keep shipping features against our shared platform APIs — chat with streaming, documents, collaboration, authentication. You'll work directly with our native product architect and design. Tablet is next, likely with a second native engineer joining you. Browser extensions and a desktop app are things we'd like someday and haven't scoped. If you want to be the person who owns native at a company, rather than one of twenty on a mobile team, this is that job. This role is fully remote, with a company hub in Colorado Springs, CO.
About BoodleBox
BoodleBox is a VC-backed GenAI platform built for higher education. With 100,000+ users across 1,200+ colleges and universities, we partner with faculty, staff, and students to make responsible AI adoption practical, impactful, and lasting. Our platform brings together leading AI tools — including ChatGPT, Claude, Gemini, and Perplexity — under one roof, purpose-built for the unique demands of academic environments. We're guided by three core values: service, education, and collaboration.
Description
What You'll Own
- Both codebases. iOS and Android, as the accountable owner: architecture, debt, releases, the lot.
- Getting the apps released. If they're still stuck in review when you arrive, the blockers are your first problem. If they're out, the release process is yours to make boring.
- Mobile delivery. Builds, signing, CI for both platforms, automated tests, crash and performance monitoring, phased rollout, and a recovery plan for the release that goes wrong after it ships.
- Feature development. Against our shared platform APIs, never a parallel mobile backend, in collaboration with the native product architect and design.
- Tablet readiness. Architecture and layout decisions that keep phone-and-tablet feasible without committing to tablet deliverables before product does.
- Accessibility and upkeep. VoiceOver, TalkBack, dynamic type, OS and SDK updates, dependencies.
- A codebase someone else can join. Documented and structured so the second native engineer is productive in their first week.
Who You Are
- You've shipped on both platforms. Native Swift and native Kotlin, in production, through both stores. Strong in one, real production experience in the other, able to maintain both alone.
- You've been rejected by App Review and gotten through. You know what the reason was and what you changed.
- You've owned the whole delivery lifecycle. Not just the code — the signing, the CI, the submission, the monitoring, the rollback that wasn't instant.
- You've integrated streaming APIs natively. A chat screen that streams tokens without jank, on both platforms, with OAuth or SSO in front of it.
- You make architecture calls alone and explain them well. To backend engineers and product architects who aren't mobile people.
- You're fine being the only one. For a while. And you'd build it so the next person doesn't have to start over.
- You've built something with an LLM. Not a wrapper. Something with real thought behind the architecture — and ideally you've thought about what that looks like on a phone.
We're Not Checking Boxes. We're Looking for the Real Thing.
Didn't come up through a traditional path? Good. Tell us about it.
No big-app-studio logo on your resume? We've hired people who outperformed everyone who did.
Career gap? Weird pivot? Started somewhere completely left field? Bring it. The people who got here the strange way usually have the best instincts.
What we actually want to see: someone who knows what the reviewer is going to reject before pressing submit without thinking about it. If that's you, the path you took to get here is just a good story.
Who Thrives Here
We move quickly, and the speed comes from ownership. You deploy your own apps. The product architect who designs the native experience is a Slack message away, and so is the CTO. When a student opens BoodleBox on their phone between classes, the whole experience is yours.
You'll fit if you're curious about how students actually use their phones for coursework, if you'd rather own two platforms than specialize in one, and if you want the mobile foundation of an education company to be something you built right. It's a small team. There's no legacy mobile org to work around, because you're it.
What We Offer
- Competitive base salary of $175,000–$185,000, plus bonus and equity.
- Unlimited PTO.
- Medical, dental, and vision coverage. BoodleBox covers 75% of premiums.
- 401(k).
- Fully remote work environment.
- Real career growth. Inside a high-growth, mission-driven company.
Salary
$175,000 - $185,000 per year