Open role
Frontend Engineer, Flutter
Engineering
Full-time
Remote-friendly, with time together in person
Build the app people actually want to open.
About the role
Kai is a mobile game that pays people for what they know. Quests, XP, streaks, leaderboards. It's live on Android and iOS, built in Flutter, and played across Latin America, the Caribbean and Asia, on whatever phone and whatever connection people have. You'll own the experience of the Kai app, end to end. About 75% of your time goes to the Flutter app and 25% to our Management Dashboard in Next.js. This is a product-minded engineering role, not a pixel-pushing one. You'll work directly with the founders and our external design firm, and you'll have real say in how the product feels.
What you'll do
The Kai app (most of your time)
Work closely with the backend team to build new client-requested features and data collection methods
Own the gaming layer: XP and level-ups, badges, daily quests and the rewards store
Make the app feel alive with motion (Lottie, flutter_animate, confetti, custom transitions) without hurting performance on mid-range Android phones
Build offline-first: an encrypted local SQLite database (Drift) that syncs with our API, so people can finish quests with low or no signal
Work with device capabilities: location, Bluetooth, sensors, background tasks, push and local notifications, and permission flows that respect both users and App Store review
Ship often. New builds go out to the App Store and Google Play about every week
The Management Dashboard
Build admin and client screens in Next.js: project authoring, audience targeting on maps, submission review queues and analytics charts
Keep the dashboard and app in step, so what a client configures on the web renders correctly on the phone
Design and UX
Be the engineering counterpart to our design firm. Review Figma files early, flag edge cases (empty, error, loading, offline, small screens) and help grow a shared component library
Turn designs into polished, animated, accessible screens, and push back when a design doesn't survive real users, real devices or patchy connectivity
Improve the product with data: read PostHog funnels and replays, spot where people drop off, and propose fixes
What we're looking for
5+ years building and shipping mobile apps, with at least 3+ years of production Flutter
Solid Riverpod (or a comparable reactive state pattern you can map onto it quickly) and a clean grasp of widget composition and rebuild performance
A strong UX eye: you notice spacing, motion and copy, and you can explain why a flow works or doesn't
Experience working with design agencies or in-house designers from Figma, including giving feedback before build starts and flagging edge-cases
Experience with Figma Dev MCP
Offline-first or local-database apps (Drift, SQLite, sync conflicts)
Gamified, consumer or rewards products; animation-heavy UI with Lottie or Rive
Accessibility and localization at scale
Nice to have
React and Next.js experience (TypeScript, Tailwind) for dashboard work
Native iOS (Swift) or Android (Kotlin) for plugin and platform-channel work
Comfort with product analytics (PostHog, Amplitude, Mixpanel)
Tooling: Figma, GitLab (CI/CD), Linear, Xcode and Android Studio. We use AI coding assistants (Claude Code) daily and expect you to be comfortable reviewing and steering AI-written code.
How we work
We build for the long term. Before we ship, we ask where it breaks, how long it lasts, and whether it can grow
EQ matters as much as code here. We'll trade some raw skill for someone the team wants to build with
We write simply. We're remote-friendly, and concise writing is how we think clearly
Probably not for you if
You'd rather leave the UX to someone else. Or you need a big team, a spec for everything and a dedicated QA crew before you ship. Here, you'll wear more than one hat.
Why now
Hard, valuable, fun. Making data collection feel like a game, on any phone, anywhere, hasn't been done well. Your first week, you'll build side by side with Maks, our CTO, in person if you like, and ship something real.
How we hire
No AI screens, coding challenges, etc. A couple of hours building with us instead.