Lead Product Engineer, Integrations

Servicepath

2d•Remote

About The Position

servicePath TM builds quote-to-cash software for IT service providers. Our customers sell multi-year contracts, configured solutions and network circuits, priced to the penny, and that data has to arrive correctly in their CRM and their finance systems. Everything that carries it there is what we mean by integrations, and we are looking for someone to own it. We are strong proponents of leveraging Artificial Intelligence to drive innovation, aligning with our core value of continuous improvement. By integrating AI into our workflows, we enhance productivity, streamline processes, and elevate our solutions to new heights. To learn more about our corporate values and how AI shapes our approach, visit our website. Job Description: You would own our public API and the developer experience around it, decide what the rest of our integration suite should become, and then build a large part of it. There is usually no specification waiting for you, and writing one is part of the work rather than a prerequisite for starting. The role exists for the decisions AI cannot make on your behalf. Working out what a customer actually needs when they have described it badly. Choosing between two designs that are both correct, knowing which one survives the next twelve customers. Recognising that a field mapping is technically valid and will still put the wrong number in someone's forecast. You would set direction with our product manager, and you would be the person the company relies on whenever something crosses a system boundary. At servicePath™, we seek candidates who are eager to enhance performance by leveraging tools and technologies like AI. Our goal is to streamline tasks, increase efficiency, and maximize productivity, making work more manageable while driving organizational success.

Requirements

Ability to build at this level without someone breaking the work down first.
C# and ASP.NET Core Web API on modern .NET
OpenAPI 3.0 in a code-first workflow, and REST design where versioning and deprecation are real constraints
OAuth 2.0 and OIDC, token handling and secret storage
At least one major CRM or ERP API integrated in production: Salesforce, Dynamics, HubSpot or NetSuite
Document databases (RavenDB)
React and TypeScript, enough to build the configuration screens for the areas you own
AI tooling as a working habit
Take something vague and shape it into something real
Simplify a mess instead of adding another layer to it
Think in systems, because one integration decision reaches every downstream consumer
Document as you build, and treat that as part of the job
Can disagree with a product decision, say why once, and then commit either way
Coach the people around you

Nice To Haves

Quote-to-cash, CPQ or billing, where the edge cases are commercial
Telecoms or carrier connectivity
Designing agent or tool interfaces, not only consuming them
Running a public API as a product

Responsibilities

Own our public API and the developer experience around it.
Decide what the rest of our integration suite should become, and then build a large part of it.
Set direction with our product manager.
Be the person the company relies on whenever something crosses a system boundary.
Own the technical roadmap for the public API working alongside our Product Team.
Manage versioning and deprecation of the public API.
Ensure the design standard for the public API is genuinely followed.
Improve the experience for a developer using the public API.
Manage connections to customers' CRM and business systems (Salesforce, Dynamics, HubSpot, NetSuite), including authentication, credentials, field mappings, forecasting rules, reference data synchronization, and connection health.
Replace bespoke setup work with a configuration surface an administrator can drive.
Manage carrier connectivity, including calling eleven carriers live for availability and pricing and normalizing the data.
Manage supplier data ingestion, moving it onto declarative definitions that AI helps author and the engine then executes predictably.
Address commercial problems such as mid-contract upgrades, co-termination, uplifts and escalators, renewals where the deal has changed shape since it was signed, and differing customer data across CRM organizations.
Ensure work is drivable by an agent as well as a person, meaning discrete typed operations, server-side validation for drafts, simulation capabilities, and a single write path.
Document new endpoints where they are written.
Ensure behavior that varies by customer belongs in configuration instead of a bespoke build.