About the role
What you'll own1. Integration design and scoping
- Run technical discovery with the partner: what their API exposes, what ours needs, where the gaps are
- Define the data contract in both directions — what fields, what format, what frequency, what happens on failure
- Produce the integration spec that both engineering teams build against
- Realistic effort estimates and sequencing, so commercial teams don't promise timelines we can't hit
- Design and build out MCP server implementations for partner and product integrations
- Own REST API and webhook design decisions on our side of the connection
- Authentication and authorisation flows — OAuth, API keys, token lifecycle, scoping
- Rate limits, retries, idempotency, error handling and failure modes
- Determine exactly what data is required from each end and why
- Field-level mapping, schema translation, and handling mismatches between the two models
- Flag privacy, consent and compliance implications early — especially for payment and student data
- Define what gets synced, what stays local, and who is the source of truth
- Sandbox setup, test plans, UAT coordination with the partner's technical team
- Debug failing integrations — read logs, trace requests, isolate whether it's us or them
- Own the go-live checklist and post-launch monitoring
- Version and deprecation management as partner APIs change
- Get us listed on partner marketplaces and app directories, meeting their technical review requirements
- Write and maintain integration documentation, setup guides and API reference material
- Build demo environments and reference implementations
- Technical enablement for the partner's support and solutions teams
- 5–8 years in solutions engineering, partner/integration engineering, technical account management or integration consulting at a SaaS or API company
- Hands-on: can read API documentation, hit endpoints with Postman or curl, read a log and find the problem
- Strong grasp of REST APIs, webhooks, JSON, OAuth and common auth patterns
- Has personally delivered at least two third-party integrations end to end — can walk through the architecture and what broke
- Can write clearly for a technical audience — specs, docs, integration guides
- Comfortable holding their ground in a technical conversation with a partner's senior engineers
- MCP (Model Context Protocol) experience, or a demonstrable grasp of the concept and appetite to go deep
- Scripting ability — Python or JavaScript — enough to prototype and test
- Payment gateway or WhatsApp Business API integration experience
- Prior work on a marketplace listing or partner app submission
- Exposure to AI/LLM tooling and agent architectures
Qualification
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field.
- Relevant experience in API integrations, solutions engineering, partner engineering, or technical consulting is required.