Engineering · Full-time
Android Developer
Own Android delivery end to end — architecture, build, store submission, and the release cadence afterwards.
- Experience
- 2–6 years
- Engagement
- Full-time
- Location
- Remote, India
About the role
You would be the person accountable for what ships to the Play Store. That means the architecture decisions, the offline behaviour, the store compliance work most teams discover too late, and the update cycle after launch. Our mobile work targets mid-range Android hardware first, because that is what most of our clients’ users actually carry.
What you would do
- Build and ship production Android applications, native or cross-platform depending on what the requirement genuinely needs
- Own the release pipeline — signing, staged rollout, crash monitoring, and the response when a release misbehaves
- Design offline and sync behaviour deliberately: what queues, what fails, and what the user is told
- Prepare store compliance during the build — privacy declarations and permission justifications, not a scramble before submission
- Review other engineers’ pull requests and have yours reviewed; nobody pushes to a protected branch here
- Write the architecture decisions down as you make them, so the reasoning survives you
What we need from you
- 2–6 years building Android applications that reached real users
- Kotlin, and comfort with either Jetpack Compose or React Native depending on the project
- At least one app you took through Play Store submission and review yourself
- A working understanding of offline persistence, background work, and the battery and permission constraints modern Android imposes
- Ability to explain a technical trade-off to someone non-technical without either dumbing it down or hiding behind jargon
Useful, not required
- iOS experience, or a genuine interest in picking it up
- CI/CD for mobile — Fastlane, GitHub Actions, or similar
- Experience with an app that had to work on poor connectivity
How hiring runs
Four steps, and a decision within a week.
Application
Send your CV and anything you have built. For engineering roles a repository or shipped product tells us more than a covering letter.
Intro conversation
Thirty minutes on what you want to work on and what we actually do. Ask us hard questions here — we would rather you did.
Technical conversation
A discussion of real problems, not a whiteboard puzzle. For engineering roles we will look at code you have written, or work through a small realistic problem together.
Decision
A clear yes or no with the reasoning, within a week. If it is a no, we will tell you why.
We have not published salary bands. Rather than print a range we would have to caveat, we will tell you the band for the role in the first conversation, before you invest time in a process. Compensation is set on the role and your experience, not on what you were paid previously.
Apply
Send us your work, not a covering letter.
Email career@laxorasoftware.com with “Android Developer” in the subject line. A repository, a shipped product, or anything you can walk us through tells us far more than a paragraph about your strengths.