Product Manager, Connectors - Remote (UK or Europe) · Junior to Mid level

Compensation: £85k – £95k

About Gr4vy

Gr4vy is the cloud-native payments infrastructure platform that gives merchants the flexibility to build, manage, and scale their payments stack without the complexity. Our customers include some of the world's most recognisable brands across travel, non-profit, retail, and digital goods, and we work alongside leading PSPs, schemes, and fraud providers to power their payment flows globally.

About the role We're hiring a Product Manager to own our connector portfolio — the integrations that link merchants to payment service providers, alternative payment methods, bank rails, wallets, and risk services. It is the most requested part of our product and the largest single body of work on our roadmap.

The job starts when a request arrives as "can we support this provider?" and ends when the integration is live and documented. In between, you work out what kind of integration it actually is, whether it can be built at all, and what it would take; you write the specification; you keep the queue ordered and honest about what's committed versus aspirational; and you follow each build through to a release note. Some of these are card processors. Many are not — redirect-based payment methods, bank transfer rails, gift card platforms, fraud and risk services, each with its own shape.

We have tooling for the hard first step. Our connector assessment process is packaged as a Claude skill that takes a provider's documentation and produces a structured first read: what type of integration it is, where the gaps are, how complex it looks. You'll be handed it on day one, you'll use it several times a week, and you'll be expected to improve it. What the tool can't do is judge — decide when an answer is good enough to act on, when a documented gap is fatal rather than annoying, and when to go back to the provider with questions rather than guess.

This is a queue-shaped job, not a project-shaped one. There are always more requests than capacity, several builds in flight at once, and a steady stream of people who want to know where theirs sits. Success looks like a portfolio that stays ordered and legible, not an empty backlog.

What sits outside this role. Pricing and commercial negotiation are not yours. You provide the technical facts that a price depends on — what type of integration it is, how complex, what's missing, what the risks are — and someone else quotes the number and has that conversation with the customer. The same applies to partner contracts and funding arrangements. You are also not managing engineers, and you are not writing the integration code.

Reporting line: reports to the Chief Product Officer. You'll work daily with engineering, delivery, and our external build partners, and closely with Solution Engineering, Support, Partnerships, and Commercial.

**What you'll do

Assess and decide

• Take inbound requests from Commercial, Partnerships, Solution Engineering, and Support, and turn each one into a clear answer: buildable, buildable with caveats, or not buildable — with the reasons written down.
• Read the provider's API documentation properly. Work out what the integration type is, what capabilities exist, and what is missing or contradictory.
• Send the awkward questions to the provider, and chase them. A good portion of this job is getting a straight answer out of a third party who is slow to reply, and being honest internally about what is still unknown.
• Keep a decision trail. When we decline something or shelve it, the reason should be findable a year later.

Shape the work

• Write the specification for each integration: what's in scope, what's explicitly out and why, what the acceptance criteria are, and which open questions are still live.
• Keep the queue ordered — what's committed, what's shaped and ready, what's waiting on a third party, and what's parked. Make that legible to everyone who asks.
• Work with engineering and our external build partners so a build starts from a specification that doesn't need rewriting halfway through.
• Track each build to done, and write the release note when it ships.

Be the front door

• Be the person Commercial, Solution Engineering and Support come to for a status or a feasibility read, and answer in writing, in the channel where you were asked.
• Join provider and merchant calls when the question is technical rather than commercial.
• Feed what you learn back into how we assess and price integrations — including improving the assessment tooling itself.

What we're looking for ** Must-haves

• You have integrated systems for a living. Two or more years in a role where reading someone else's API documentation and making it work was the core of the job — integration or implementation engineer, solutions consultant, technical partner manager, technical support engineer, or a developer who did a lot of third-party integration work.
• You read API documentation cold and fast. REST and JSON, webhooks, the common authentication patterns, OpenAPI specs. Comfortable with XML and older SOAP-era interfaces too, because plenty of payment providers still ship them.
• You can tell a good API from a bad one, and say why. Undocumented error cases, no idempotency, no sandbox, reference docs that contradict each other, fields with no stated constraints. Spotting these early is most of the value you add.
• You write clearly and you write a lot. Precise, structured, and honest about what you don't yet know. This is the part of the job we will weight most heavily.
• You are comfortable saying "we can't build this" to someone who very much wants to hear yes — in writing, with reasons, without hedging it into meaninglessness.
• You can hold many things at once without losing the thread on any of them, and you keep your own records rather than relying on someone else's.
• You work AI-natively. Much of our product process runs through purpose-built Claude skills. You'll be handed them on day one and expected to extend them. If you don't already work this way, this will be a difficult adjustment.

Nice-to-haves

• Payments knowledge — cards, APMs, wallets, bank rails, 3DS, tokenisation. We will teach you what you're missing, but you'll ramp considerably faster if some of this is already there.
• Product management experience. This can be a first product role for the right integrations person; we care more about how you think about an integration than about your job title so far.
• Experience working with outsourced or partner-delivered engineering.
• Experience in a customer-facing technical role where commercial colleagues depended on your answers to move a deal along.

What we're not asking for

• People management. This is an individual contributor role.
• Deep payments experience. It helps, and it's in the list above as a nice-to-have, but a strong integrations background matters more to us here.
• Slide decks. There is almost no deck work in this job.**

How we'll know you're succeeding At three months: every new request gets a first-pass assessment within days rather than weeks, and the people who used to chase for one have stopped.

At six months: the portfolio is ordered and legible. Anyone can see what's committed, what's shaped, what's blocked and on whom. Builds start from a specification that survives contact with engineering.

At twelve months: you own the portfolio end to end. Nothing enters the build queue without your assessment, nothing ships without a release note, and the CPO no longer reads provider documentation.

Why you’ll love working at Gr4vy You’ll be joining at a truly momentous time in our company’s life cycle. We want your imprint on how the world experiences Gr4vy as the leader in the fast-growing cloud payments space. Come and bring your skills to a growing team. You’ll influence, challenge and help build our inclusive culture and passion for equity. A global identity is in Gr4vy’s DNA, with employees currently spanning across the globe.

Our Fine Print We choose laughter first. Sometimes our standups veer into debates about food, family (furballs included), and unlimited lifehack fails. We’re committed to learning, to advocating, and to doing better for our customers and ourselves, every day.

Diversity statement We value all the great benefits that diversity brings and encourage everyone to bring their whole self at work, regardless of gender, religion, ethnicity, sexual orientation, age or disability.

Compensation: Competitive salary in USD/EU/GBP + equity + benefits. Location: Anywhere in Europe - Remote working