Senior Software Engineer, Devices

Ship Privacy Pal on every phone and tablet on earth — and go as close to the OS as we have to so on-device privacy is real, not marketing.

Most of the prompts our customers worry about start on a phone. The mobile build of Privacy Pal isn't a port of the desktop client — it's its own product, with its own constraints (battery, thermals, sandboxing, App Store review, enterprise MDM fleets) and its own opportunities (Keychain, Secure Enclave, on-device inference accelerators, system extensions). As Senior Engineer on Devices you own the iOS, iPadOS, and Android clients end-to-end, set the bar for what 'native' means here, and ship the parts of the product that actually live on the device.

Reports to the Head of Engineering. This role is hybrid — remote-first, with quarterly on-site weeks at our West Palm Beach HQ.

• Own the iOS, iPadOS, and Android clients end-to-end — architecture, performance, distribution, support.
• Go as close to the OS as the work demands: keyboard extensions, share targets, file providers, accessibility services, system intents, broadcast receivers.
• Ship on-device inference with the right accelerator for the right device — Core ML and the Apple Neural Engine on iOS; NNAPI, Execu Torch, and the Hexagon NPU on Android.
• Hold the line on battery, memory, and thermal budgets. We measure it. We publish it. We don't ship regressions.
• Wire detection into Keychain, Keystore, Secure Enclave, and Strong Box so customer secrets never leave the device.
• Own the release train:
  Test Flight, App Store review, Play Console staged rollouts, MDM-distributed enterprise builds (Intune, Jamf, Kandji, Knox).
• Take part in the on-call rotation for mobile.

• 6+ years writing production mobile code — deep expertise in at least one of iOS (Swift, Objective-C) or Android (Kotlin, Java), and working command of the other.
• You've shipped at scale and lived with the consequences — crash-free rates, App Store rejections, OEM-specific surprises at 2am.
• Comfort below the framework: NDK and C/C++ on Android, Objective-C++ and C on iOS, JNI, and IPC primitives (Binder, XPC, Mach ports) — or the equivalent stack on another platform.
• A real opinion on at least one of: kernel, HAL, BSP, device drivers, custom ROM work, secure boot, TEE, or mobile cryptography APIs.
• Comfort owning the developer experience: build systems (Xcode, Gradle, Bazel), code signing, provisioning, and the failure modes that only show up on a real device.

• Past life on a phone-maker or platform team — Apple iOS/Darwin, Android Framework / AOSP / Pixel, Samsung Mobile R&D, One Plus, Meta Reality Labs, Qualcomm, ARM.
• Built or maintained a custom kernel, HAL, or device driver in production.
• Shipped on-device ML in a real app with Core ML, MLC, Hexagon, or NNAPI/Execu Torch — and can talk about what didn't work.
• Wrote a keyboard extension, share extension, or accessibility service that millions of people used without noticing.
• Familiarity with enterprise mobile distribution: MDM/UEM, Jamf, Intune, Kandji, Samsung Knox.
• Contributed to AOSP, Web Kit, Chromium, or any other open mobile codebase.

$160K–$215K + equity The number on the offer letter is the number we believe in — we don't negotiate against ourselves and we don't expect you to.