About the role
Some of our largest customers do not need a demo, they need a working integration inside their own environment, sometimes one with no internet access. You will embed directly with these customers, write the code that connects Plane to their existing tools and workflows, and stay on the account until it works in production, not just in a sandbox. You will work alongside the customer's own engineers as much as you work with ours, and you will carry a problem from a whiteboard conversation to shipped code yourself. This role exists because our biggest deployments live or die on custom integration work that a generic support ticket cannot solve.
What you'll do
- Own the end-to-end delivery of custom integrations for strategic customers, from the first technical conversation to code running in their production environment.
- Build against APIs and infrastructure you did not design and cannot fully see, because you are integrating into someone else's stack, not your own.
- Design the technical approach for a customer's specific use case, then write the code yourself rather than handing it to another team.
- Work daily embedded with a customer's engineers and stakeholders, in their tools and on their timeline, while staying connected back to Plane's own product and engineering teams.
- Decide when a customer's request is a one-off integration and when it is a real product gap worth escalating, and make the case either way.
- Debug an integration failing on a customer's infrastructure that you cannot access directly, working from logs, screen shares, and a customer engineer's patience, because you will not always get a repro environment.
What you'll bring
- You have shipped production code that talks to real customer systems, and you can walk us through one integration that broke and what you did about it.
- You are proficient in Python and comfortable with API design and integration work, including auth flows, webhooks, and the messy edges of someone else's documentation.
- You have worked embedded with a customer or a similarly demanding internal stakeholder, and you know the difference between a request and the actual problem behind it.
- You can hold a technical conversation with both a customer's engineers and their executives, in the same meeting, without losing either.
- You are comfortable owning a project with a real deadline and no clear handoff, because on this team, you are the handoff.
Nice to haves
- You have contributed to Plane, run it self-hosted, or maintained another open project people rely on.
- You have shipped software into regulated or isolated environments: banking, defense, healthcare, or air-gapped anything.
- You have built systems where AI agents act on real data, and you have opinions about state, permissions, and audit trails.
- You have worked in a forward-deployed, solutions engineering, or professional services engineering role before.
Tech
- Backend: Python/Django, Golang, Node.js, Postgres, Redis
- Messaging: RabbitMQ, Kafka
- Infrastructure: AWS, Kubernetes, Rancher, self-hosted deployment via Docker and Helm
- Integration: REST and webhook-based APIs, SSO and identity federation
- Everyday tools: GitHub, Plane (yes, we use our own product)