Senior Product Engineer

About the role

Hi 👋 I'm Leo, Head of Roadmap Engineering at Pinpoint.
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.
We're hiring a Senior Product Engineer on our Marketplace squad: the team behind Pinpoint's usage-based features (reference checks, background checks, one-way video interviewing) and the billing that powers them. You'll sit inside our product engineering org of 30+ people across 8 verticalised squads; Marketplace is a tight team of a product manager, two engineers, and a designer, owning these features end-to-end.
Our remit is to help grow the revenue that scales with how much customers use Pinpoint, and much of that runs on third-party services we white-label. So the craft here is integration: wiring up those vendors seamlessly and owning the relationship yourself when something breaks on their side. It's one of the most commercially pointed and most independent parts of the product.
You'll be embedded in the problem from the start: understanding real customer workflows, debating trade-offs, shaping solutions, and standing behind them in production, with vendors and edge cases included. There's no separate discovery phase and no "throw it over the wall" model.
This isn't a role for someone to just ship what they are told. We want engineers who build in-depth context over time and use that understanding to make better product decisions every day. If you care about owning a problem space, not just shipping tickets, this role was built for you.

The fine print (but a bit more exciting):
This is a remote role (UK, Portugal, Spain, or Poland) with occasional in-person team meetups.
Our product is a configurable, platform-style ATS serving multiple personas: recruiters, hiring managers, and operations teams across a wide range of complex workflows
Our stack is pragmatic and maintainable: Ruby on Rails (6.x), React with TypeScript, PostgreSQL, Sidekiq, and CI/CD via CircleCI (moving to GitHub Actions).
Pinpoint is still very much in startup mode. Priorities shift, not everything is perfectly defined, and we expect people to operate well in that environment.
Curious about how we think and build? Our engineers write about it here .
Our values actually matter here. We hire people who reflect them in how they work, collaborate, and make decisions.

Build full-stack features using Ruby on Rails and React (TypeScript) within a small, focused squad.
Own your product area end-to-end: from real customer workflows and edge cases through to delivery, performance, and ongoing quality.
Integrate white-labelled third-party services seamlessly into the platform, and own the vendor relationship, including hands-on debugging when the issue is on their side.
Contribute to architectural discussions and technical trade-offs, not just implementation.
Help translate product needs and constraints into clean, maintainable solutions.
Review code, mentor others, and raise the technical bar within your squad.

5+ years of professional software engineering experience building production web applications.
3+ years of production experience with Ruby on Rails.
3+ years building React applications in a production environment.
Comfortable working with TypeScript (our frontend codebase uses it throughout).
Background in startup or scale-up B2B SaaS environments.
Fluent with AI-assisted development and able to show how it's changed the way you work.
Comfortable operating in ambiguity and taking end-to-end ownership.
Experience on multi-persona, workflow-heavy SaaS products.
Strong written communication: clear, direct, and able to explain technical decisions to non-engineers and external partners alike.
Bonus : deep experience integrating third-party APIs / white-labelled services, usage-based / billing features, and refactoring or migrating systems.
FAQs How are squads structured? Small, cross-functional teams: one PM, one designer, and two to five engineers, each owning a specific area of the platform end-to-end: backlog, quality, performance, and all.
What areas of the product do squads own? Verticals across Workflow, Candidate Experience, Onboarding, Marketplace, Platform & Reporting, and Integrations, plus an AI squad and a Delta squad for fast-moving, complex client work. Engineers join a squad and build deep context there over time.
How is AI deployed within the team? AI is central to how our engineers work. Most of the team uses Claude Code as their primary tool, and the hard part of the job has shifted from writing code to understanding context, owning outcomes, and knowing when the model is wrong. The engineers who thrive here are high-agency people who spot a problem and go fix it, and who care whether what they shipped actually helped the user. We think our value driver is growth and product strength, not margin, so when AI makes each person more productive, we use that to move faster, not to hire fewer people. Our R&D budget is more than 40% larger this year than last, and we still have more work than people to do it.
Do engineers do support rotations? No formal rotation. Dedicated support teams handle incoming tickets, though engineers may occasionally help with technically complex issues in their area.
What does 'senior' mean here? You're a strong individual contributor who takes real ownership, contributes to technical direction, and helps raise the standard of the people around you. This isn't a people-management role.
What's the sprint cadence? Two-week sprints, with retros and small postmortems.
How do you handle QA and technical debt? Quality is owned by the team. We have strong automated testing and encourage engineers to address technical debt as part of their day-to-day work, not in a separate cleanup sprint.
What does the first 90 days look like? By 30 days, you're comfortable with the codebase, the stack, and Marketplace's product area, and starting to help field questions about your features. By 60 days, you're shipping independently, contributing to squad planning, and influencing product decisions. By 90 days, you're a trusted owner of your area: making technical decisions, owning a vendor relationship, and building genuine product context.