We’re a high-growth HR tech company building software that helps in-house recruitment teams attract, hire, and onboard the right talent. Today, we have a strong foundation in place, with a mature product, rapid growth, strong product–market fit, and happy customers.

Integrations sit at the heart of Pinpoint’s product and commercial strategy. Our customers expect Pinpoint to fit seamlessly into their existing HR and hiring stack, and today our integrations marketplace includes ~70 built-in integrations alongside a public API that customers and partners actively build on.

As we work with larger, more complex organisations, the quality, reliability, and clarity of our integrations matter more than ever. To support that work, we’re hiring an Integrations Engineer to join our team of four to design, build, and maintain integrations between Pinpoint and third-party systems.

This person will own integrations end-to-end and work closely with Sales and Customer Success to unblock deals, support customers, and keep integrations running as external systems evolve.

The fine print (but a bit more exciting):

This is a remote-first role based in the UK or Poland, with occasional in-person team meetups. Our HQ is in Jersey (UK), and our ~90-person team is spread across the UK, US, and EU.
This is a backend- and integration-first role. It’s not about UI features or greenfield architecture but about making systems talk to each other reliably, clearly, and at scale.
Our product is deep, flexible, and genuinely complex. Integrations aren’t plug-and-play and often involve legacy systems as well as modern APIs.
This work will involve interacting with customers regularly: joining calls, clarifying requirements, troubleshooting integrations, and working directly with vendors and partners to get things live and keep them running.
Our values actually matter here. We hire people who reflect them in how they work, collaborate, and make decisions

About the Role:

Design, build, and maintain integrations with third-party systems using REST, GraphQL, and legacy APIs (SOAP, XML, older authentication patterns)
Build and ship integrations using our internal Ruby-based integration plugin framework
Own integrations end-to-end: requirements gathering, technical design, development, testing, validation, release, and ongoing maintenance
Act as a technical partner to Sales and Customer Success, supporting deal scoping, answering integration questions, and documenting expected behaviour
Pull data from external systems and push it back into Pinpoint, ensuring accuracy, reliability, and performance
Maintain existing integrations as APIs evolve, versions change, or edge cases emerge
Collaborate with Product and Engineering to identify repeatable patterns and reduce bespoke work over time
Write clear, practical documentation for internal teams, partners, and customers

What does success look like?

First 30 days: Shipping a first production integration and becoming comfortable with our plugin framework, API patterns, and integration workflows
First 60 days: Delivering multiple integrations, including at least one involving legacy or poorly documented third-party APIs, and actively supporting Sales and Customer Success with integration questions
First 90 days: Independently owning integrations end-to-end, contributing feedback to improve tooling or documentation, and maintaining a steady delivery cadence of ~2 integrations per month

About You:

2+ years’ experience building and maintaining integrations in a B2B SaaS environment
3+ years of production experience working in a Ruby on Rails codebase
A backend-first focus, with at least 1+ year of hands-on React experience to support integration-related UI, authentication flows, or debugging when needed (this is a requirement)
Strong hands-on experience with external APIs, including REST, GraphQL, and real exposure to SOAP or other legacy APIs (this is a real requirement)
Experience owning integrations through their full lifecycle: scoping, data mapping, authentication, testing, release, and maintenance
Comfort working with messy realities: inconsistent documentation, unexpected behaviour, edge cases, and unresponsive vendors
A testing and resilience mindset—you can explain how you test integrations, use sandboxes or mocks, and handle failures over time
Confidence working cross-functionally, particularly with Sales and Customer Success
Strong written communication skills and a documentation-first approach
Comfort working independently, managing priorities, and taking ownership without needing constant direction

FAQ’s

How do you decide what integrations to build?

We prioritize integrations from two main sources:

Existing and prospective customers: We're often asked to connect with their existing tools, usually HRIS, payroll, or background-checking systems. These requests are prioritized based on customer impact, technical feasibility, and the effort required.
Partnerships: Some integrations are driven by strategic partnerships or great products we want to offer to our customer base.

How is the current API built?
You can explore our API documentation here. It’s organized around REST and follows the JSON:API specification. Beyond the API, we also offer webhooks that clients can configure to trigger on key events. These webhooks are an area we’re actively improving to create an even better developer experience and more self-serve integrations.

What’s your tech stack?