Product Manager (Partnerships)
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Job Description
Why Lovable?
Lovable lets anyone and everyone build software with any language. From solopreneurs to Fortune 100 teams, millions of people use Lovable to transform raw ideas into real products — fast. We are at the forefront of a foundational shift in software creation, which means you have an unprecedented opportunity to change the way the digital world works. Lovable-built applications and websites are visited hundreds of millions of times a month, and a growing share of our value comes from how well we connect to the tools our users already rely on. And we're just getting started.
We're a small, talent-dense team building a generation-defining company from Stockholm. We value extreme ownership, high velocity, and low-ego collaboration. We seek out people who care deeply, ship fast, and are eager to make a dent in the world.
Requirements
- You are absolutely passionate about AI and constantly experiment to find new ways to work more efficiently with it.
- 5+ years in product management, with meaningful time on platform, integrations, API, or partner-facing products.
- A proven track record of owning a roadmap and leading an engineering team to ship.
- Technical fluency — you program or have programmed in the past, and can hold credible conversations about APIs, auth, and integration architecture.
- Strong product and operational judgment.
- Strong root-cause and systems thinking.
- Comfort working across teams you don't manage — you can align a dotted-line partner org on shared priorities without formal authority.
What we're looking for
- Someone who can hear 30 different partner requests and synthesize them into the 2 things that actually matter.
- World-class product taste applied to the unglamorous-but-critical stuff — integrations, auth, reliability — that partners have to trust.
- Sharp prioritization: the ability to weigh the inbound partner queue against longer-term bets and make clear calls.
- Extreme clarity in communication — with partners, with engineers, with leadership.
- A self-directed operator who builds the roadmap rather than just managing the inbox.
What you'll do
In one sentence: Do all it takes to make Lovable the platform partners want to build on.
What this includes:
- Own the partnerships roadmap. Define what we build, make the trade-off calls, and drive execution with your engineering team and design.
- Work hand-in-hand with the partnerships org. Take their partner relationships, requests, and context, and translate them into clear product requirements — not secondhand summaries.
- Bring the context. Synthesize what you're hearing across partners into clear themes and opportunities, and present them with conviction and rigor.
- Scope ruthlessly. Partner needs sprawl — your job is to find the smallest thing we can ship that unlocks the most value.
- Balance the queue against the bets. Ship against reactive partner requests while reserving room for proactive integrations worth building before anyone asks.
- Check with users and metrics to learn what works, what should be iterated on, and what should be killed.
If you want significant ownership of a critical growth area while staying close to partners and details day to day, this might be the perfect fit.
About your application
Please submit your application in English. It's our company language, so you'll be speaking lots of it if you join.
We treat all candidates equally — if you're interested, please apply through our careers portal.
Audit details(provenance, verification trail, raw fields)
Core fields
lovable:f1c3bdd3-683b-409f-b0a1-5a39f9c7dd72Provenance
lovableVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
LLM enrichment
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
