Jetpack Compose UI
Compose-first for new screens, Material 3 design system, Compose-Compiler stability metrics in CI, animation performance budgets.
Loading…
Senior engineering · Android / Kotlin
Senior Android / Kotlin engineering for production systems.
Native Android engineering — Kotlin, Jetpack Compose, Coroutines, Hilt, and the long-tail device discipline (Pixel 4a → Galaxy S25, Android 10+) most apps under-test for.
- In production
- 2018+
- Senior bench
- 15+ G6/G9 engineers
- Floor
- G6+ on client work
- Engagement
- Outcome-led, not hourly
Why senior, not contractor
Android / Kotlin in production is a different problem than Android / Kotlin on a laptop.
Most Android apps are tested on the engineer's flagship and shipped to a long-tail device fleet that breaks in unexpected ways. Prosigns ships Android with Compose-first UI, Coroutines + Flow for the async layer, performance budgets defended on real low-end devices (Pixel 4a, Galaxy A-series), and the Play Store review discipline that catches Data Safety mismatches before the listing rejection.
Senior floor
G6+ minimum
Bench depth
15+ G6/G9 engineers
In production
2018+
Engagement
Outcome-led SOW
Where Android / Kotlin ships
6 sub-areas, grounded in shipped engagements.
Specific applications of Android / Kotlin we’ve built and operate. Every example below maps to a real engagement, not a bullet on a stack-card.
01 02 Coroutines + Flow async layer
Structured concurrency, StateFlow / SharedFlow for UI state, Channel for events. No more LiveData except for migration.
03 Play Store + Data Safety
Data Safety section reviewed against runtime, common rejection categories audited pre-submission, staged rollout discipline.
04 Enterprise + MDM
Managed Google Play, Android Enterprise / Work Profile, MDM (Intune, Workspace ONE), Android Management API.
05 Compose Multiplatform
Compose for iOS / desktop / web where the cross-platform investment is genuinely warranted; not a default but a tool when it fits.
06 Wear OS + Auto + TV
Wear OS apps with proper complications, Android Auto for media / messaging, Android TV for media-led brands.
Stack depth
The Android / Kotlin ecosystem, owned.
Frameworks, libraries, and runtime tools the bench has shipped in production. Not a CV-skim — a working depth.
UI
- Jetpack Compose
- Material 3
- Coil
- Lottie
- Compose Multiplatform
Async + concurrency
- Coroutines
- Flow
- StateFlow
- WorkManager
- Channel
Architecture + DI
- Hilt
- Koin
- ViewModel
- Navigation Compose
- Decompose
Data + persistence
- Room
- DataStore
- Realm
- Ktor Client
- Retrofit
Quality + ops
- JUnit 5
- Roborazzi
- Maestro
- Firebase Crashlytics
- Sentry
Engagement models
Three ways to engage Android / Kotlin engineers.
We don’t bill hourly contractors. Engagements run against outcomes — choose the shape that matches the work.
See engagement models- 01
Fixed-scope
Defined deliverable, fixed price
When the deliverable is clear and the scope is bounded — an MVP, a migration, a discrete platform build. Senior engineering against a written outcome, not against a body count.
- 02
Embedded squad
Senior product team, ongoing
When the work is product-shaped and the cadence is continuous. A senior pod (engineering + design + PM as needed) embedded into your team, with the practice lead co-piloting from HELM.
- 03
Managed services
Steady-state operations
When the system is running and needs ongoing engineering ownership — operations, SLO defense, release management, security and compliance evidence. Monthly retainer against a published SLA.
Selected work
Android / Kotlin engineering that shipped.
Healthcare
Field-rounding companion app on Android for clinicians.
Pixel 4aperf budget defendedCompose-first with Coroutines + Flow. Offline-first sync via Room + WorkManager. Performance budgets enforced on real low-end devices in CI before merge.
Duration · 8 months
Brief us
Reply < 4 business hoursHave a Android / Kotlin workload? Send a brief.
Five fields. Goes straight to the practice lead — not an SDR. We’ll reply with a senior engineer’s read on fit, scope, and the engagement model that suits the work.
FAQ
Questions buyers ask.
Everything below also appears in the proposal and the SOW — no surprises after signing.
Compose or XML views?
Compose for new builds. XML interop only where necessary — large legacy fragments, third-party SDKs that haven't shipped Compose support. We don't ship XML-only new builds in 2026.
Java or Kotlin?
Kotlin. Java is fine for legacy maintenance but shouldn't be the choice for new modules. KSP for annotation processing where KAPT is too slow.
Is this staff-aug, or is it engineering-led delivery?
Engineering-led delivery. We don't bill hourly contractors against your JIRA board. Every engagement runs against a defined outcome with a senior engineer accountable from kickoff to operating cutover. If you genuinely need staff-aug — discrete bodies, your management, hourly rates — we'll be honest and route you to a partner that fits.
What seniority floor are we talking about?
G6 minimum (six-plus years in their craft) on every billable hour. Department leads are G9 or G10. We don't flex juniors onto the bench mid-sprint, we don't subcontract to delivery centers, and we don't dilute senior rates with mixed staffing. The bench in the proposal is the bench in production.
How does pricing work?
Three engagement models published at /engagement-models/. Fixed-scope for defined deliverables, embedded squads for ongoing product work, managed services for steady-state operations. Rates depend on seniority, engagement length, and region. Discovery + scoping conversation is free; SOWs are written against deliverables, not bodies.
Where are your engineers based?
Senior-only across Dallas, Doha, Lahore, and Islamabad. We staff against the engagement's needs (timezone, language, regulatory frame), not against arbitrary regional preferences. Most engagements run with a US/EU-aligned core and a follow-the-sun extended bench when the workload warrants it.
Will the engineers I see in the proposal be the engineers shipping the work?
Yes. We name the engineers in the SOW, attach their profiles, and they're on the kickoff. We don't bait-and-switch with senior reviewers and junior execution. If a named engineer needs to roll off the engagement (rare), we surface a replacement from the same seniority tier with explicit handoff.
Talk to a Android / Kotlin lead
Senior Android / Kotlin engineering, accountable from kickoff.
Bring the workload — we’ll bring a senior engineer plus the practice lead most relevant to the work. 30 minutes, no obligation, no junior reps.