Job description

Location: Remote in the US Why this role exists OpenExchange delivers virtual and hybrid events for the world’s largest investment banks, alongside hundreds of corporate clients and organizations. More than half a million virtual meetings and over two thousand conferences have run on our platform. For many of our clients, our platform is not just a tool they log into. They license access to our API suite to connect us to their own event management system, CRM or research workflow — automating event creation, attendee registration, reporting, and the retrieval of recordings and transcripts for compliance archiving. A growing share of our most significant relationships now runs this way. This role owns those integrations end to end: scoping them before the deal closes, delivering them, and making sure our own teams can run them afterwards. Where the role sits • Works daily with: Sales and Account Management, Product Management, Engineering, Event Delivery/Production, Client Support • Client-facing: Yes — with client technical leads, platform owners, and their vendors • Location: Remote in the US or UK, with occasional travel What you’ll own 1. Pre-sales and scoping • Join Sales on opportunities where an API integration is part of the deal — translating a prospect’s requirement into what our APIs can actually do, and being honest about what they can’t. • Run technical discovery: what systems they are integrating from, who owns them, their authentication model, and how their event workflow runs today. • Produce scoping documents and solution designs that Sales can attach to a proposal and Engineering can stand behind. • Give commercial decisions a realistic view of what an integration will take, from us and from the client — including saying no to the ones that aren’t viable. 2. Implementation and technical delivery • Own the integration from signed contract to the client running live events — milestones, dependencies, client-side blockers, and keeping both sides honest about the critical path. • Guide client engineering teams through the OE API modules — event and meeting management, registration, reporting, and post-event artifacts — including account setup, credentials and environment access. • Agree the authentication and access model with the client: API credentials, SSO setup, and attendee joining methods. • Run integration testing and UAT: build the test plan, work through failure cases, validate data flows end to end, and sign off go-live readiness. • Support platform migrations, sequencing the change so the client’s events keep running throughout. • Design integrations around how events actually get run — by our Delivery teams and by the client’s planners and producers — not just around what the API allows. 3. Enablement of Delivery and Support • Treat every integration as unfinished until our Delivery and Support teams can run and troubleshoot it without you. • Build and maintain the operational documentation for each integrated client: how their events get created, which fields flow from where, the known quirks, and what “normal” looks like. • Deliver training — live sessions, runbooks, decision trees — pitched at the people supporting live events when you’re not online. 4. Complex client issues • Sit inside the Support escalation path as the senior technical resource for integrated clients. • Diagnose issues that cross a boundary — API payload and field-mapping problems, authentication and SSO failures, data discrepancies between systems, and access not behaving as expected. • Interrogate logs, API responses and monitoring to isolate whether a fault sits with us, the client, or the integration between us — and communicate that clearly to a client under pressure, including holding the line on realistic timelines. • Convert recurring escalations into permanent fixes, and feed a structured, evidence-backed stream of requirements into Product Management — ranked by how often they come up and how painful they are. Experience and skills Essential • Proven experience in technical implementation, solutions engineering, integration consulting or a similar client-facing technical role. • Strong practical understanding of REST APIs: able to read documentation, build and debug requests in Postman or similar, interpret responses and error codes, and explain payload and field mapping to a non-specialist. • Able to hold the commercial and technical thread in the same conversation — credible with a client’s architect and with their commercial sponsor. • A track record of training and enabling internal teams, not just delivering to clients, with written work — implementation plans, runbooks, incident updates — that people can act on. • Comfortable running multiple concurrent implementations under time pressure, with competing client-side dependencies and the client watching. Desirable • Financial services, capital markets or another regulated environment, and familiarity with the security and compliance scrutiny that brings. • Webcasting, virtual events, streaming or a comparable live-delivery domain. • Hands-on familiarity with Jira, Confluence and Salesforce. #LI-OE

Requirements

Must-haves

Location: Remote in the US
Why this role exists
This role owns those integrations end to end: scoping them before the deal closes, delivering them, and making sure our own teams can run them afterwards.
Where the role sits
Works daily with: Sales and Account Management, Product Management, Engineering, Event Delivery/Production, Client Support
Client-facing: Yes — with client technical leads, platform owners, and their vendors
Location: Remote in the US or UK, with occasional travel
What you’ll own
Pre-sales and scoping
Join Sales on opportunities where an API integration is part of the deal — translating a prospect’s requirement into what our APIs can actually do, and being honest about what they can’t.
Run technical discovery: what systems they are integrating from, who owns them, their authentication model, and how their event workflow runs today.
Produce scoping documents and solution designs that Sales can attach to a proposal and Engineering can stand behind.
Give commercial decisions a realistic view of what an integration will take, from us and from the client — including saying no to the ones that aren’t viable.
Implementation and technical delivery
Own the integration from signed contract to the client running live events — milestones, dependencies, client-side blockers, and keeping both sides honest about the critical path.
Guide client engineering teams through the OE API modules — event and meeting management, registration, reporting, and post-event artifacts — including account setup, credentials and environment access.
Agree the authentication and access model with the client: API credentials, SSO setup, and attendee joining methods.
Run integration testing and UAT: build the test plan, work through failure cases, validate data flows end to end, and sign off go-live readiness.
Support platform migrations, sequencing the change so the client’s events keep running throughout.
Design integrations around how events actually get run — by our Delivery teams and by the client’s planners and producers — not just around what the API allows.
Enablement of Delivery and Support
Treat every integration as unfinished until our Delivery and Support teams can run and troubleshoot it without you.
Build and maintain the operational documentation for each integrated client: how their events get created, which fields flow from where, the known quirks, and what “normal” looks like.
Deliver training — live sessions, runbooks, decision trees — pitched at the people supporting live events when you’re not online.

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

apigorestjira

Platform: adp-workforce-now
Effort: medium