Android Developer
Glint Tech Solutions LLC
—
Jun 30, 2026
—
Jul 20, 2026
What this job asks for AI summary
An onsite Android Developer role focused on building and shipping Kotlin-based mobile applications for enterprise and consumer audiences. Day-to-day work spans the full development lifecycle — from architecture and API integration to performance tuning, CI/CD pipeline support, and Google Play releases. Suits a Jetpack-proficient Android developer experienced with MVVM/MVI patterns and comfortable collaborating across product, design, and backend teams.
Mid level · National · Contract
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The role is onsite across four possible states — CA, WA, NY, and NJ — with no single metro specified. No CBSA or state has been set; the hiring manager should confirm the specific office location(s).
The posting is from a staffing firm (Glint Tech Solutions) placing candidates with an unnamed enterprise client, and uses the word 'engagement', strongly suggesting a contract arrangement. Employment type has been set to Contract accordingly.
No overall years-of-experience requirement is stated. The scope (shipping production apps, CI/CD, code reviews, architectural patterns) is consistent with a mid-level individual contributor.
MVVM and MVI are listed as alternatives since the JD presents them as interchangeable architectural pattern options ('such as MVVM or MVI').
GraphQL and WebSocket are listed as alternatives on a single skill entry because the JD groups them together under Nice-to-Have as a single optional capability ('GraphQL or WebSocket implementations').
Flutter and React Native appear under Nice-to-Have as cross-platform exposure; they are listed as alternatives since the JD treats them interchangeably as examples of cross-platform frameworks.
A published Google Play portfolio and regulated-industry background (healthcare, fintech) are listed under Nice-to-Have but name no distinct technology tool, so they are omitted from the skills list per extraction rules.
Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.