What we test for
Typical work
- Feature work in Kotlin, with or without Compose
- Migrations from Java or XML views to Compose
- Play Store releases and staged rollouts
- ANR, crash-rate and battery work
The coding test
Build a screen that loads a paged list from an API, caches it in Room and survives rotation and process death, then explain how they would roll it out on Play. Scored on state handling, lifecycle awareness and release know-how.
Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
How do you keep state across rotation and process death?
A strong answer covers: ViewModel for rotation, SavedStateHandle for process death, and the real source of truth in a repository, not in the Activity.
When does Compose recompose more than it should, and how do you find it?
A strong answer covers: Unstable parameters, lambdas built on every call and state read too high in the tree; found with the layout inspector and recomposition counts.
Users report an ANR you cannot reproduce. What now?
A strong answer covers: Play Console vitals filtered by device and OS, the main-thread stack in the report, StrictMode locally, then the blocking work moved off the main thread.
Coroutines or RxJava on a new feature, and why?
A strong answer covers: Coroutines and Flow for new code: structured concurrency, less boilerplate and first-class support in Jetpack. RxJava only where the code base already lives there.
How do you ship a risky release to millions of devices?
A strong answer covers: A staged rollout that starts small, crash and ANR thresholds watched at each step, a feature flag to turn it off, and a halt plan agreed before the first percent.
One monthly price per developer. Everything in it.
No deposit, no minimum term, no placement fee. You pay one invoice a month for each developer on your team.
Per developer, all-in. Your quote arrives by email with your exact number after you send the brief.
- Developer pay, local payroll and taxes
- Vetting: coding test, soft skills, English
- Free replacement within 90 days
- A direct line to our CEO
What changes the price
- Seniority and role. Senior engineer, tech lead or architect.
- Stack. Some stacks and niche tools cost more to staff.
- Team size. Larger teams get a better monthly rate per seat.
- White-label. Agencies reselling under their brand get partner pricing.
Terms in plain words
- First 2 weeks risk-free: if it isn't working, you don't pay for them
- Month to month, 30 days' notice to end
- No deposit and no minimum number of seats
- Want to hire the developer full-time? Buyout of 3 months' fee in year one, 2 months' after
Questions tech leads ask us
How senior are your Android developers?
6+ years of professional Android work, with recent production experience.
Can I see the coding test results?
Yes. Every profile card includes the score and the reviewer's notes.
What does it cost?
$6,900 per developer per month, all-in, and flat: the same rate whatever the stack. Your exact quote arrives by email after you send the brief.
Skip the sales rep. Talk to the CEO.
Tell us what you're building, your stack and when you need people. Three matched profiles within 48 hours, and a straight answer on whether we're the right fit.