Mobile Engineer: Android

Build our Kotlin SDK, and find the fastest way to run each model on each Android chip.

• Bring every model to Android, and make each one fast on budget phones and flagships.
• You've made Android apps or libraries measurably faster on real phones, with or without machine learning.

Location Amsterdam, Remote

Time zone UTC-5 to UTC+1

Type Full time

Android phones use hundreds of different chips, NPUs, and drivers. You speed up each model, across audio, vision, and text, until the model meets its latency target on a budget phone as well as on a flagship. Deep Android performance experience matters more here than machine learning experience.

• Profile and speed up inference on Android runtimes such as LiteRT and ONNX Runtime: delegates, NPUs, GPUs, and memory.
• Test on everything from budget phones to flagships, in Firebase Test Lab and in our own device lab.

• Profile before you optimize.
• Write clean, tested code, and spot a weak change in review, whether a person or an agent wrote it.
• Plan and run your work through coding agents such as Claude Code, with a low tolerance for slop.
• Wrote JNI or native code.
• Maintained an Android library that outside developers used.

Start what needs starting without waiting to be asked, and finish what you start. Take on work outside your role when a project needs you.

We ship quickly, so we cut scope until only the part users notice is left. Anyone can comment on your work or redo your draft, and we say early when work isn't ready. We read that feedback as help.

We judge the work by what shipped and what changed because of it. Nobody counts hours.