Ashby Integrations Lead, Partnerships at Ashby responsible for owning integration partnerships and acting as technical liaison between Product Managers and Engineering. Focus on operational improvements and automation.
Responsibilities
Own the inbound integration lifecycle
Own inbound integration requests from qualification through launch and ongoing maintenance, using judgment about customer value, product fit, technical feasibility, partner commitment, and Ashby’s priorities.
Guide partners through the process—from NDA and sandbox access to API documentation, onboarding, testing, and launch—while choosing the right balance of async and live collaboration.
Set clear expectations, keep work moving, and close the loop thoughtfully when an integration is not the right fit or a current priority.
Connect partners, Product, and Engineering
Serve as the technical and commercial liaison across integration partners and Ashby’s Product, Engineering, Product Operations, Support, Customer Success, Sales, and Marketing teams.
Translate partner and customer needs into clear requirements, tradeoffs, and next steps, and help determine the right path: native build, partner-built integration, connector, unified API, or future roadmap opportunity.
Help partners navigate API concepts such as authentication, endpoints, webhooks, data mapping, and workflow design, while bringing sound judgment to design-partner and enterprise requests.
Own how integration knowledge reaches Sales, CS,and Support, so teams feel well versed on current and upcoming integrations.
Own quality, launches, and strategic partnerships
Coordinate integration reviews and launch readiness with partners and Product, including workflow validation, feedback, security considerations, configuration, documentation, assets, and Marketplace publication.
Maintain the external integration directory and partner-facing resources, and partner with Marketing and Product Marketing on launch communications, enablement, and ongoing updates.
Qualification
You communicate clearly and write wellYou like building the systemThis role probably isn’t right ifYou dislike writing
Required
We think the ideal person for this role will have experience and skills that look something like this:
You’ve worked at the intersection of partnerships, product, technology, and customers—in integration or platform partnerships, technical program management, product operations, solutions architecture, implementation, or a similar role.
You’re technically fluent enough to understand APIs, authentication, data flows, webhooks, sandboxes, and integration tradeoffs. You don’t need to be an engineer, but you should be comfortable asking precise questions and learning how systems work.
You communicate clearly and write well. You can build trust with partners, set expectations, give direct guidance, and turn messy conversations into crisp requirements, decisions, and documentation.
You’re operationally disciplined and improvement-minded. You can own a high-volume workstream, create structure in ambiguity, automate repetitive work, and follow through across teams.
You care deeply about the customer experience and can work effectively across Product, Engineering, Support, Customer Success, Sales, Marketing, and external partners.
You like building the system, not just running it. You're drawn to finding a problem, scoping it, and proposing a solution, and you don't assume the current way is the right way just because it's what exists.
This role probably isn’t right if...
You want a role focused only on strategy or relationship development; this role includes hands-on technical, operational, and documentation work.
You’re uncomfortable with technical detail, difficult prioritization decisions, or direct conversations about fit and expectations.
You prefer an established playbook or a single-function role rather than building structure across teams.
You dislike writing, async communication, proactive follow-up, or representing Ashby externally.