Senior Engineering Roles

How We Hire
We hire for strong fundamentals, range, and adaptability — not a specific tech checklist. The stacks named below are what you'd work in today; we expect our tooling to evolve and want engineers who can go deep in an unfamiliar area and help us re-platform when it makes sense. Most named technologies are examples of a competency, not hard gates — but each role calls out a small expected core you should already be strong in, with everything beyond it treated as adjacent or bonus.

How We Work
Small team, high individual ownership, and heavily AI-assisted development. Strong operational discipline is non-negotiable — we've had (and learned from) production incidents around deploys, schema drift, and data safety. We value engineers who are careful with production, obsessive about edge cases, and comfortable owning a slice end-to-end.

AI-Assisted Engineering — Required for Both Roles
Our development is heavily AI-assisted; you'll work daily with AI coding assistants and agents as a core part of how you ship. We need engineers who are genuinely effective at it — not "I've used Copilot," but:
• Direct AI well — decompose work into agent-sized tasks, prompt and steer through complex multi-step changes, and judge when AI accelerates vs. when to hand-craft.
• Verify with full rigor — treat AI output as a draft to be reviewed, tested, and understood: catching subtle bugs, hallucinated APIs, and unsafe changes instead of rubber-stamping. Our prod-safety bar does not drop because an agent wrote the code — it demands sharper review.
• Own the outcome — you're accountable for what ships, AI-assisted or not.


Senior Mobile Engineer (Cross-Platform)
Summary. Own the device-side SDK that is the foundation of the entire platform — the source of all telemetry and the device half of the authentication flow. You are fluent and production-proven on both iOS and Android, and you treat platform parity as a first-class responsibility. This is SDK + platform + security work, not app-UI work.
Level. Senior (~5–8+ yrs): owns the mobile domain end-to-end across both platforms, sets mobile technical direction, makes native-vs-cross-platform and build-vs-buy calls, and mentors.
You'll own. A dual-platform telemetry/auth SDK — signal collectors, device fingerprinting, background/wake scheduling, real-time transport with offline queueing, cryptographic device attestation, secure key enrollment/rotation, and biometric step-up — reliably, within each OS's battery/background/privacy constraints, at parity across platforms.
EXPECTED CORE — you should already be strong here
Swift (iOS) and Kotlin (Android) — production-proven on both; native platform-services (background, secure storage, biometrics, attestation); applied mobile security & crypto; REST + WebSocket with modern async (async-await / coroutines). Everything in the *Adjacent / bonus* column strengthens an application but is not required.
Required — competency areas (examples, not exclusive):
• Dual-platform production depth — shipped, maintained production work on both iOS (Swift) and Android (Kotlin); genuinely both, not one-with-a-dabble.
• Platform-services mastery on both OSes — background execution & scheduling (BGTaskScheduler / WorkManager, JobScheduler, Doze/App-Standby), location & motion (CoreLocation·CoreMotion / Fused Location·SensorManager), secure storage (Keychain / Keystore, Secure Enclave / StrongBox·TEE), biometrics (Face/Touch ID · LocalAuthentication / BiometricPrompt), and device attestation (App Attest · DeviceCheck / Play Integrity).
• SDK/library engineering — designing clean, versioned, low-footprint SDKs consumed by other teams' apps: API design, backward-compat., semantic versioning, and distribution (SPM · CocoaPods · XCFramework / Gradle-Maven · AAR).
• On-device performance & reliability — battery/power profiling and correctness under OS lifecycle/permission/background edge cases (the real bugs here are stale sensors, background kills,...