By Ryan Wightman, Generalist and Marketing Stream Lead at Jumpstart. Updated September 2026.Every week a founder tells me some version of the same thing: "I need someone who can own the product side, but I can't justify a full product manager yet." What they hire instead is a generalist with a product lean. Founder's associate, chief of staff, sometimes "operations and product". The title moves around. The job doesn't.
This page is for the person who keeps ending up owning the product-shaped problems without the title. You're two to five years into consulting, a bank, a grad scheme or a scale-up. You're the one who writes the spec nobody asked for, sits in on the customer calls, and gets irritated when the roadmap is a Notion page nobody reads. That's the person these roles are built for, and it's the person I'm looking hardest for right now.
What a product-focused generalist actually does
You sit at product, but you're rarely the only person with an opinion on it. The founder has one, the engineers have one, the customers have several. Your job is to look at the same product through every one of those lenses, CX, engineering, marketing, comms, and turn what you see into the next iteration. You're the connector. Nothing about the product moves unless someone joins those conversations up, and at seed stage that someone is you. That's why the title says generalist: so much feeds into a product decision that a narrow specialist can't make it.
In practice, the first month looks something like this:
- You talk to users. Not a survey, real calls, ten or twenty of them. You write down what they said, what they meant, and what they'd pay for.
- You turn that into something engineers can build and marketing can explain. A one-page spec, a rough wireframe, a prioritised list, the sentence that goes on the landing page. You don't need to know Figma, you need to be clear.
- You own the number the founder cares about this quarter. Activation, retention, time to first value. You find out why it's not moving and fix the parts that don't need code.
- You run the operational side of shipping: release notes, onboarding flows, the help doc, the pricing page, the thing that broke on Tuesday.
Then it widens. At yetipay the founders' associate owns projects across ops, growth and product four days a week in Soho. At Simple Online Healthcare the role literally lists product, engineering, management and strategy in the title. At Ares Intelligence, a team of five, you run client projects from interview to intelligence report and build the playbooks that turn pilots into repeat revenue. That's product work with a commercial edge, whatever the business card says.
The non-technical product engineer
Something has shifted in the last year or so. Founders are hiring product people who can't write production code but can build. They open Cursor or Lovable or Replit, describe what they want, and have a working prototype in an afternoon that the engineers then make real. Call it vibe coding if you like. What matters is that the gap between "I have an idea" and "here's a clickable version" has collapsed, and founders want someone who lives in that gap.
So AI competency is now part of this job. Not a computer science degree. The habit of reaching for AI tools first, knowing what they're good at, and shipping a rough version rather than writing a document about it.
The other half is translation. You'll sit on a client call where the customer asks why the integration is late, and you'll need to explain a technical problem in plain English without making the engineers sound incompetent or the customer feel stupid. Then you'll go into the internal meeting and do it the other way round. People who can do that are rare, and founders pay for them, because every hour a technical founder spends translating is an hour not spent building.
Roles like this we've filled
These went to candidates from my Generalist stream. Salaries are from the original briefs.
What it pays
For a product-leaning generalist role at a London seed or Series A startup, expect £35k to £65k base. Equity or a bonus appears on roughly half of the roles I've filled. Two things move the number up: prior experience owning a product surface or a revenue number (even a small one), and the stage of the company, since Series A pays more than pre-seed. Two things move it down: no evidence of shipping anything, and needing a lot of direction in the first six months.
If you're coming from banking or consulting, read the banking-to-startup page too. The base is lower than what you're on. The scope is not.
Who gets hired
I've watched a lot of these hires happen. The people who get the offer tend to share a few traits, and none of them is "has a product title".
- They have shipped something. A side project, an internal tool, a process that saved a team hours. Doesn't matter how small. Founders want evidence you can finish.
- They can hold a conversation with an engineer and a customer on the same afternoon without either one rolling their eyes.
- They're comfortable being wrong in public. Product at seed stage is guessing, testing, and changing your mind quickly.
- They build with AI. A prototype in Lovable, a workflow in Zapier, a script they got Claude to write. Founders now ask about this directly.
- They can explain a technical delay to a customer and a customer complaint to an engineer, in the same afternoon, without losing either.
- They want to be early. Sust Global's brief said "cares about climate". Radical's said "driven by the mission". Founders read for that and they can tell when it's not there.
The sweet spot is two to five years' experience. Less than that and you haven't seen enough to have judgement; more and you'll want a team and a budget the company can't give you yet. What founders don't need: an MBA, a PM certification, or a product title on your CV. Plenty of the people who land these roles have never had one.
Want a shortlist of live product-generalist roles? Book a 15-minute call. We'll work out if you're a fit for the stream, get you on the platform within 24 hours, and founders start pitching to you.
Book a generalist call →How to position yourself
Your CV probably describes your job. Rewrite it to describe your decisions. "Owned the pricing page redesign, activation up 18%" beats "supported the product team". Pull every example where you chose what to build or what to stop doing, and lead with those.
Then build something. If you've never used an AI coding tool, spend a weekend with one and make a small working thing that solves a problem you actually have. Put the link on your CV. It answers the "can you build" question before anyone asks it, and it's the single fastest way to separate yourself from the consultants applying for the same role.
On Jumpstart you also record a 60-second video pitch within 24 hours of joining. For a product generalist this is the single best filter you'll get, because it's the job in miniature: understand your audience, say one clear thing, ship it before the deadline. Mine's on the home page if you want an example.
Then apply to roles where the founder is technical and needs a commercial and product counterpart, or where the founder is commercial and the product is getting away from them. Both are good. Avoid roles where there's already a Head of Product and you'd be their assistant. That's a different job and it caps you.
How the process works
Book a 15-minute call with me. If the stream fits, you're onto the platform with a profile and a video pitch within 24 hours. Founders pitch their roles to you on video, you Quick Apply to the ones you like, and 80% of candidates who hit the 24-hour window land a role in four to six weeks. It's free for candidates. Jumpstart can't support visa sponsorship or candidates in full-time study, so please don't book if either applies.