Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
EPAM Systems Inc is seeking a mobile developer to lead the first offline-first iOS/Android app project. You will own the app from initial setup to public release on App Store and Google Play, working with a small team in a two-week sprint cycle and AI-assisted coding tools.
You will review diffs, add tests, and decide on sync/storage/release strategies, reporting to leadership. Prioritize reliability, performance on low-end devices, and clean client communication throughout development.
Our client is a remote product studio that builds MVPs and custom software for startups and companies past the idea stage. Clients pay for each build, and a small team works in two-week sprints with AI coding tools used every day. Clients are startup founders and their teams, so developers explain tradeoffs to them directly.
They've been at it since 2020 and were profitable in 2025, with a 30% net margin. After building their own AI systems, they tripled monthly revenue with the same team size. Clients rate them 4.9 out of 5 in verified reviews, and the startups they build for have raised more than $25M in venture funding.
You'll be the only mobile developer on a new offline-first iOS and Android app, starting from the first project setup. The developer accounts, build pipeline and release tracks don't exist yet, so that's where you begin, and you stay on the same app through its public launch on the App Store and Google Play.
Sprints run two weeks with four to five features each, and coding agents write most of the first draft. You review every diff, add the tests the agents missed, and make the calls on sync, storage and releases. If you'd rather have a QA team or a release manager handle testing and store submissions, this probably isn't the right seat.
You report to the studio's leadership and work day to day with the lead developer and a backend developer, who's your counterpart on the sync and upload APIs. You'll also write risk notes and tradeoffs directly to the client team, with your recommendation attached. Success means sprints that close with their acceptance criteria verified, a write queue that neither loses nor doubles a submission on real devices, and an app live on both stores where sync failures show up in monitoring before anyone reports them.