Mobile Software Engineer, Android
Showpad (company site, opens in a new tab)PuneOn-siteDirect career pageEst. 10–18 LPA
Posted 2d ago
Reach people at Showpad
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Showpad you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Build and maintain a native Android app used by field sellers, including offline content access, background sync, API integrations and buyer-engagement features.
- Evolve a mature, multi-module codebase through incremental architecture migrations while continuing to ship features and improve testability.
- Contribute to release pipelines, automated testing and production issue diagnosis, while applying secure data and networking practices.
Minimum Requirements
- Work Experience Required: Significant experience building production Android apps in a SaaS or enterprise environment; duration is not explicitly mentioned in the JD.
- Strong Kotlin proficiency and working Java knowledge; hands-on experience with Coroutines/Flow, Hilt or Dagger, Retrofit, MVVM or similar patterns, and gradual legacy-code migration.
- Experience with multi-module Gradle projects, offline-first features, local storage and background sync; unit-testing experience with JUnit, Mockito and Robolectric.
- Location qualification: Pune. Specific onsite or remote arrangement is not explicitly mentioned in the JD.
Ideal Candidate Profile
- Has worked in enterprise or SaaS Android products where reliable offline use and sync are important to users in the field.
- Can make incremental improvements in a mixed legacy and modern codebase without disrupting ongoing feature delivery.
- Has relevant exposure to mobile release operations, observability, security, or integrations such as CRM, SSO, WebView and document rendering.