Staff Software Engineer, Integrations Platform

Staff Software Engineer — Integrations Platform Fixify's Integrations Platform is both the framework and the ecosystem: the patterns, SDK, and abstractions our team builds, plus the integrations themselves that run on top of it across customer ticketing, identity, knowledge, and endpoint systems. We are heading toward hundreds of integrations authored by our team today, by FDEs and contractors against the SDK tomorrow, and by AI agents soon after. We have reached the point where the shape of the platform underneath all of that matters more than any single integration. Someone needs to own that shape across quarters, not weeks. When you have built enough integrations to see the platform-shaped gaps, do you also have the patience to design the framework other engineers will use to fill them? At Fixify, every integration starts as a small failure somebody is feeling. A password reset that did not go through before a meeting. A Jira ticket that landed in the wrong queue. An access request that has been pending since Tuesday. The integrations we build are invisible when they work and impossible to ignore when they do not. At the scale we are heading toward, with FDEs, contractors, and AI agents all authoring on top of the platform, the only way to keep them invisible is to design the platform underneath with real care. That design work spans quarters. It is the work this role exists for. As a Staff Software Engineer on the Integrations Platform team, you would own the multi-quarter shape of the platform. You would set the integration strategy as a continuous workstream (taxonomy, prioritization, risk tiering, vendor partner relations). You would drive the architectural direction for non-API integration patterns where standard API-and-poll falls short: browser-driven flows, webhook-first designs, and iPaaS bridges like Okta Workflows and Tines. You would design the authoring framework that lets FDEs, contractors, and AI agents extend the platform safely (skill SDK, risk tier enforcement, sandbox environments, doc generator, CI gates). You would design the integration testing infrastructure that takes the team past tribal, per-integration fixtures. And you would do all of this as a multiplier for the team, not as a portfolio of solo wins. This is a coaching role as much as a building role. You would pair on hard design decisions before they ship. You would run design reviews as a teaching forum. You would share the strategic and surge escalation surface with the engineering manager so the team executes predictably, and you would take your regular turn in the maintenance rotation like everyone else. The point of this hire is to make the next architecture decision easier for the rest of the team, not to become the person every decision routes through. What we can do for you Hand you the architectural canvas for a platform that is mid-build, with the destination already meaningful (hundreds of integrations, agent authoring on top) and the room to shape how we get there. Pair you with a Chief Architect who is genuinely engaged on the integrations problem, and a small senior team who will push back on you the way you should push back on them. Connect you directly to the customers and analysts on the other end of your platform decisions, so the architecture is grounded in real user reality rather than abstract elegance. Trust your judgment on multi-quarter calls. We expect you to make them, document them, and revisit them when context changes. Give you the space to coach. This is part of the week, not a side activity. Share the strategic and surge escalation load so it is not a single funnel. What you can do for us Own the integrations strategy as a workstream rather than a series of decisions made under pressure. Drive architectural decisions across multiple quarters and multiple integrations, including the trade-offs between extracting shared abstractions now versus carrying duplication for a defined period. Design the authoring framewor