Internship · Engineering
Mobile Developer Intern
Offline-first Flutter on an app with a hard rule: a foreman finishes his day in under 90 seconds, with gloves on, with no signal.
- Location
- Remote, 4 hours of overlap with 11:00 to 19:00 Pakistan time
- Hours
- 20 or 40 hours a week
- Length
- 8 weeks, fixed cohort start
- Compensation
- Unpaid. If your work ships to a client or into our own products, we pay you for it
- Applications close
- 31 October 2026
- Stack
- FlutterDartRiverpoddrift / SQLitego_router
About the role
You join a cohort of nine interns building Stage 2 of SiteDay, our field production software for sitework contractors. You own the foreman's phone app, where every screen reads from a local database, nothing waits on the network, and CI measures whether the whole day still takes under 90 seconds. The eight weeks run in three phases: weeks 1 and 2 you learn the codebase and help write the specification, weeks 3 to 6 you build your slice in parallel with the other tracks, and weeks 7 and 8 are integration, release and a demo you run yourself. The app is Flutter and Dart; if you know React Native the concepts transfer and week 1 covers the language.
What you will learn
- Flutter and Dart with Riverpod, go_router and drift over SQLite
- Offline-first architecture: local storage as the source of truth, sync as a background detail
- An outbox and why it beats retrying a request
- Conflict handling tested against a written matrix rather than hoped about
- Designing for gloves and sunlight: tap targets, type sizes, custom keypads
- Performance as a requirement with a number attached, measured in CI
What we look for
- One typed language, and some mobile or React experience
- A physical Android or iOS phone to test on
- Git basics
What you would build
Machine hour meters and fault reporting from the field, including the state that takes a machine out of service and removes it from tomorrow's list. Your work is measured against the 90-second timing test: if the feature makes the day slower, the test wins and the feature waits.
How the 8 weeks run
- Weeks 1 to 2: learn the codebase, read the specification, and ship one small change. The design intern produces the wireframes everyone else builds from
- Weeks 3 to 6: build your slice in parallel with the other eight tracks, reviewed weekly, with a mid-point review in week 4
- Weeks 7 to 8: integration, regression, and a release you demo to the company yourself
- Every week: a written daily standup, a Monday cohort sync, a 30-minute 1:1 with your mentor, and a Friday demo