There are no open roles right now.
That will change on the day it stops being true. Until then this page is for anyone who wants to know how the work is actually done here, what the studio would look for, and what to send if you would like to be the first call.
Nothing is listed, and nothing is invented.
nexapps is one engineer, one shared platform, and one app that has not launched yet. There is no headcount plan to announce and no funding round to point at. When a role opens it will be posted here with a real description of the work — and a real person reading the replies.
How this studio works
One platform, many apps
Sign-in, subscriptions, AI, analytics and privacy are written once, in Swift, Kotlin and Python, and every app builds on them.
A written spec before the build
Every concept is written up and scored against fixed criteria before any code exists, and the ones that do not clear the bar are dropped. Nothing gets built without a spec, and the finished build is measured against the one it started from.
Native, not wrapped
SwiftUI on iOS, Jetpack Compose on Android. No web view pretending to be an app.
Privacy is a build constraint
No third-party analytics or advertising SDK ships inside a nexapps app — and this website makes zero third-party requests, which you can verify right now.
Small surfaces, verified
Changes land through a CI gate — lint, tests, and a build that fails when a rule is broken. That applies to the apps and to this website equally.
Timeboxed, and written down
Four to six weeks per app, a hard stop after eight, and a written note at the end whatever the outcome was. The thresholds are fixed in the spec before the build starts.
What this studio would look for
No role is open. This is what would matter if one were.
People who finish. Shipping into a store, with review, edge cases, refunds and the second release, is a different skill from building something that demos well.
Ownership of a whole slice. At this size, whoever writes a feature also writes its analytics, its entitlement states and its privacy story.
Comfort in the shared layer. The interesting work is in the platform at least as often as it is in the app.
Plain writing. Specs, commit messages and product copy are all part of the job here. Honest copy is a product decision, not a marketing one.
What to send
Email support@nexapps.co with Careers in the subject line. Send something you actually shipped — an app, a repository, a piece of writing — rather than a template CV.
One person reads this mailbox and answers it by hand — most replies go out within two business days, and nothing behind the address is automated, so a heavy week can take longer.
The answer may well be “not yet”, and if it is, it will say what would have to change. If you would rather simply be told when something opens, say so in the same email — there is no list and no automation behind this address, so the message sits in an inbox until there is something to say.
The day this page has a listing on it, it will be a real one.