Updated November 2026
A mobility startup's first hires after the founding engineers are usually a city launch lead, a field operations lead and someone who owns permits and public affairs, with hardware or firmware engineers early if you build your own vehicles or chargers. In mobility the density of a working network in each city matters more than feature count, so the people who make vehicles or chargers available, maintained and allowed on the street often come before the second software engineer.
Density beats features
A rider who finds no scooter within a short walk, or a driver who reaches a broken charger, does not care how good your app is. Every mobility business sells availability in a specific place, and availability is built by people on the ground.
Once the core product works, the next salary usually does more in operations than in engineering, which upsets the order most software founders expect.
Turns a signed city into live, used vehicles or chargers.
Owns uptime, rebalancing and the contractor network.
Keeps the right to operate, city by city.
More features rarely fix a thin network.
Paid demand in a city with patchy coverage burns money.
Wait until there is enough trip or session data to model.
Engineering still grows, but the second and third engineers build operational tooling such as dispatch, maintenance tickets and fleet health views, rather than consumer features.
Four kinds of mobility company, four different bottlenecks
Mobility covers businesses with very different limits on growth. Find yours first, then hire for it.
| Segment | What limits growth | Suggested first non-engineering hires |
|---|---|---|
| Micromobility (scooters, bikes) | Permits and fleet caps set by the city | Public affairs lead, then field ops for charging and rebalancing |
| EV charging | Site access, grid connections and charger uptime | Site acquisition lead, then a field maintenance lead |
| Fleet software and services | Depot operations and vehicle downtime | Operations-minded solutions engineer, then customer success |
| Ride services | Driver supply and local licensing | Supply operations lead, then a licensing and safety owner |
Fleet software companies sell to operators rather than run vehicles, but they still win by hiring people who have run a depot. Their buyers can tell.
Who owns the city relationship
Cities, transport authorities and regulators decide whether you can operate, how many vehicles you can deploy and where you can install. Micromobility operators bid for permits, charging companies need planning consent and utility connections, and ride services need local operator and driver licensing.
Good candidates come from local government, transport policy or another operator's public affairs team. Ask which permit they lost and why. Rules differ by city and change often, so check with your lawyer or the relevant authority before planning a launch.
Hardware, field and data hires
Hardware and firmware
If you build vehicles, locks or chargers, hire a firmware engineer who has shipped devices that update over the air in the field. In EV charging, comfort with OCPP and multiple charger vendors matters more than a perfect stack.
Field operations and maintenance
Look for someone who has run shifts, contractors and spare parts across sites and measures success in uptime. People from logistics and other fleet businesses often fit; our head of operations job description is a good starting point.
Data and routing
Rebalancing, routing and site selection reward good data, once you have enough trips or sessions. Hire a data engineer first and a data scientist later, as covered in hiring a data engineer. If your fleet is electric, the climate tech playbook covers the energy side.
Worked example: an EV charging startup going from one city to three
Illustrative. A Series A charging operator with four engineers and two operations staff, live in one city, with sites signed in two more and both due live within the year.
The grid and permits manager starts before the integration engineer, because connection queues and consents, not code, set the launch dates. The data engineer waits until three cities produce enough sessions to compare sites.
Where Funded.club fits
We are a fixed-fee recruiting partner for funded startups and fast-growing teams across North America, Europe and APAC, and have helped 500+ startups from Seed to Series D since 2019. One dedicated recruiter runs each search end to end, with first screened candidates within 7 days and 33 days on average from kick-off to hire.
The fee is a low fixed amount per hire, agreed upfront and averaging 6 to 9% of salary, against the 20 to 25% typical of contingency recruiters. For an illustrative city launch lead on $95,000, the fee is $7,500, part as an advance and the balance on offer acceptance. If we don't deliver a shortlist of at least 3 qualified candidates within 30 days, you can claim the advance back in full. See our pricing page, or see all our sector hiring playbooks.
Frequently asked questions
Who should a mobility startup hire first?
After the founding engineers, a city launch lead, a field operations lead and a permits or public affairs owner. Add a firmware engineer early if you build your own vehicles or chargers.
When should a mobility startup hire a public affairs person?
Before you apply for permits in a new city or bid for public contracts, since cities decide whether and where you operate.
What does a city launch lead do?
They take a newly signed city to a working network, covering local hiring, sites or depots, contractors and launch timing, then hand over to a city manager.
Should a mobility startup hire a data scientist early?
Usually not. Hire a data engineer to collect trip, session and fault data first, and a data scientist once there is enough volume to model.
Worth a brief chat about your next hire? Book a free call.
Hiring after a funding round?
First candidates in 7 days. Fixed-fee, no commission.