Careers
There are no open roles right now.
That is the honest headline and it will change on the day it stops being true. Rather than leave this page empty, or fill it with listings that do not exist, here is what this studio actually is, how the work is done, and what to do if you would like to be the first call.
Where things stand
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 on this page with a real description of the work — and a real person reading the replies.
How this studio works
- One platform, many apps. Identity, entitlements, the AI gateway, analytics and the privacy boundary live in a Swift SDK, a Kotlin SDK and a Python backend; apps consume them as versioned packages. The platform in detail →
- A written spec before the build. Concepts pass a stage gate first. The spec is the argument; the code is the consequence.
- Native, not wrapped. SwiftUI on iOS, Jetpack Compose on Android.
- 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. Every page here is statically rendered and guarded by tests that fail the build when a rule is broken, including the rule that stops this site quoting a number it cannot support.
What this studio would look for
This is a disposition rather than a job description — no role is open — but it is what would matter, so you can tell quickly whether it would suit you.
- 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.
Write anyway
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 a role opens, say so in the same email. There is no list and no automation behind this address — the message sits in an inbox until there is something to say.