Part-Time Remote iOS Developer
This one's part-time, fully remote, and pays $65,000 a year in USD. Location doesn't matter here; it's open worldwide. If you want a serious iOS role that doesn't eat a full workweek, this is worth a look.
This isn't a side project or a maintenance-only gig. The app has real users right now, and whatever ships lands in front of them fast. Part-time just means the hours are lighter, not the responsibility.
The work
You'll own native iOS features start to finish, not just patch things other people built. That means writing the code, wiring it into backend APIs, and sticking around to fix what breaks once real users get their hands on it. A single feature often runs from a rough design handoff through several rounds of testing before it's stable enough to ship, and this role covers all of that ground rather than handing pieces off to someone else.
- Build and ship native iOS features from initial design through release
- Connect app functionality to backend services through REST APIs
- Chase down bugs flagged by QA or reported by users, and fix them
- Address performance issues, including slow screens and memory problems on older devices
- Push builds through TestFlight and, eventually, App Store review
- Write brief technical notes on trickier fixes so the next person doesn't have to rediscover the same problem
A recent example: an app that lagged noticeably when scrolling a long list turned out to be re-rendering every row from scratch on each frame. Fixing it meant rethinking how the list cached its cells, not adding more hardware to the problem. That's the kind of thing this role runs into regularly.
Backend contracts sometimes shift mid-build, same as anywhere else. When that happens here, the expectation is to flag it early and adjust rather than push ahead on a spec that's already out of date. Nobody's looking for heroics on a broken assumption.
Pay and benefits
$65,000 a year, paid in USD, for part-time hours. On top of that:
- Health insurance
- Paid time off
- 401(k) matching
- Remote-work flexibility
- Bonuses each quarter based on how you and the team perform
Part-time doesn't mean an afterthought here. The benefits package is real, and the bonus structure rewards actual output rather than hours logged. Coverage and matching work the same way as on a full-time listing, prorated to the part-time schedule.
What you need
A bachelor's degree is the baseline, and two years of hands-on Swift work is the target on top of it. Beyond that, what matters most is what you've actually shipped. A candidate with an app live in the App Store right now, even a small one, has already dealt with crash reports, review rejections, and the gap between a working build and a good one. That's harder to fake than a resume line.
Native experience is what we're after, so time spent deep in the iOS SDK counts for more than general mobile exposure. Someone who's spent two years mostly working with cross-platform tools would need to demonstrate real Swift fluency to be competitive here. Experience with Apple's own frameworks, rather than a wrapper library sitting on top of them, tends to be the clearest signal of that.
Interview conversations tend to focus on decisions made in a shipped app rather than on textbook questions. Bring the project where something went wrong, and you had to fix it after release, since that conversation gets past the parts of a resume that are easy to inflate. A candidate who can walk through a real crash they diagnosed from start to finish is easy to spot compared to one reciting definitions.
Skills
- Swift
- iOS SDK
- Xcode
- REST APIs
- UIKit or SwiftUI
- App Store deployment
- Git
Nice-to-haves that'll get a second look: Combine or async/await for handling asynchronous data, unit testing with XCTest, some Fastlane or CI experience for automating builds, and comfort with Core Data or SwiftData for anything involving local storage. None of these are required, but they significantly reduce ramp-up time. Someone coming in already comfortable with SwiftUI specifically will likely move faster than someone still leaning on UIKit out of habit, since most new feature work happens there now.
How this actually runs
Async is the default here. Most communication happens through written updates and pull request comments rather than back-to-back calls, which is part of why the part-time structure works at all. Naukri Mitra hears from candidates fairly often who want serious engineering work without the full 40-hour commitment, and this is exactly that kind of listing.
Code review still moves at a normal pace despite the reduced hours. A pull request opened on a Monday shouldn't sit untouched until the following week just because everyone's juggling other commitments; the team treats review turnaround as part of the job, not an extra.
Expect a short check-in call once a week, mainly to unblock anything that's stuck. Outside of that, the schedule is yours to manage as long as the work gets done and reviews happen on time. Deadlines are set around app store review windows more than a strict daily clock, since a submission can sit in review for a few days no matter how ready it is.
Nobody's tracking hours minute by minute. What gets tracked is whether committed work lands when it's supposed to, and whether code review turnaround stays fast enough that the rest of the team isn't stuck waiting on a merge.
Apply
Send a resume and a link to at least one app you've shipped to the App Store, plus a note on what you specifically built if it was a team effort. We move fast on this one. Expect a response within a few days and a short technical conversation focused on something real you've built, not a whiteboard puzzle.
If part-time engineering work sounds like a stretch on paper, it usually isn't in practice. The per-week scope is smaller, but the standard for what ships isn't lowered to match it. Plenty of strong candidates for a role like this are already juggling something else: a degree, a freelance line of work, another part-time gig, and that's fine as long as the commitment here gets the focus it needs.
