When our sales team closes a deal with a marketplace or platform business that needs to move their payments infrastructure to Whop, someone has to take that deal off the sales rep's plate and drive the technical integration to completion. That's you. You're the first engineer these businesses work with after signing. You assess their existing tech stack, jump on calls with their engineering team, build a concrete migration plan, and drive it to completion. You're not handing off a doc — you're in their codebase, on the calls, and accountable for the business going live on Whop. You know Whop inside and out. You know how connected accounts work, how to set up direct charges vs. transfers, how to embed the payout portal, how webhooks fire on payment.succeeded, and how to enroll sub-merchants via the API. Sometimes closing a deal means building what doesn't exist yet. If a prospect needs an MCP server, a public SDK integration, an AI agent skill, or a reference app to see how Whop fits into their stack — you build it. You contribute directly to Whop's public developer surface (docs, SDKs, example apps, MCP tools) whenever that's what it takes to land or accelerate a deal. You also close the loop back to our core engineering team. When you see the same integration friction three times, you drive the product change that eliminates it. You're always on, always responsive, and pushing timelines. This role reports to the Head of Partnerships.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Entry Level
Education Level
No Education Listed