Product engineering
Full-stack work on a multi-tenant platform where correctness matters — a wrong arrival time is a child at the wrong curb. Web app, APIs, and the data model underneath both.
Careers
Small team. Real problem. Early days.
We are building fleet software for operators the big platforms price out — school bus contractors, regional carriers, paratransit providers. It is unglamorous, specific work, and the people it helps are easy to picture.
Where we are
We are not running formal openings yet.
Rather than post roles we cannot fill today, here is the honest position: Nice Technologies is early, building alongside its first operators. Hiring will start with the people who make the product real — engineering and customer-facing roles — and we would rather already know you when it does.
If the work below sounds like yours, write to us now. We keep a genuine list, we read every message, and we reply.
How to reach us
Skip the cover letter
Email info@nicetechnologiesinc.com with "Careers" in the subject line and tell us three things:
- What you have built or run that you are proud of
- What kind of work you want more of
- Anything we should know about how you like to work
A link to something real beats a résumé. We reply within one business day, including when the answer is "not yet".
The work
What we will be hiring for.
Indicative, not open roles. If one of these is obviously you, say so.
Mobile
Two apps with opposite constraints: a driver tool built for gloves, glare and no signal, and a parent app that has to be reassuring and nearly invisible.
Implementation & support
Getting an operator from spreadsheets to live in weeks. Data migration, training dispatchers and drivers, and staying on the line through the first week of service.
Sales & partnerships
Talking to transportation directors and district contacts without a script. Knowing the operation well enough to say honestly when we are not the right fit.
Transportation operations
Someone who has actually dispatched, run a shop or managed a contract, to keep the rest of us honest about how the work really goes.
Something we have not thought of
If you can see a gap between what we are building and what operators need, tell us what it is and what you would do about it.
How we work
What you would be signing up for.
The same commitments we make to customers, pointed inward. We would rather set expectations plainly than sell you a version of the job that does not exist.
- Close to the customer. Everyone talks to operators. Nobody builds from a spec they have never seen used.
- Small scope, shipped. Narrow things that work beat broad things that nearly do.
- Early-stage reality. Fewer resources, more ownership, and genuine uncertainty. That suits some people and not others.
- Privacy is not a feature team. We handle children's location data. Everyone here is responsible for treating it properly.
- We say when we cannot. To customers, and to each other.
Get on our radar.
No opening required. Tell us what you would want to work on and we will tell you honestly where we are.