Fixify

StaffSoftwareEngineer,IntegrationsPlatform

United States Remote Friendly
Market Sentiment
HIGH DEMAND

Neural analysis suggests this role is
optimal for Lead candidates.

The Brief

“Staff Software Engineer, Integrations Platform at Fixify. Skills: Integrations Platform architecture, Authoring framework design, Non-API integration patterns, Multi-quarter architectural ownership, Coaching and team multiplication. Own the multi-quarter shape of the platform. Set the integration strategy”

What You'll Achieve.

Make the next architecture decision easier for the rest of the team; 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; Treat platform work as a multiplier rather than a personal portfolio

Industry & Context.

Problems you'll solve

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?; Read CS threads, POPs escalations, and customer-facing reality as input to the strategy

Eligibility Requirements

Take your regular turn in the maintenance rotation

What They're Looking For.

Must Have

At least 8 years of experience building scalable, observable SaaS systems, Deep fluency in TypeScript and Node.js, Experience with AWS primitives (Lambda, SQS, S3), Hands-on experience with non-API integration patterns: webhooks at scale, OAuth flows across many tenants, Hands-on experience with at least one of browser-driven automation, iPaaS bridges (Okta Workflows, Tines, Workato), or callback-based designs, A documented architectural decision you are proud of, Fluency with AI coding tools (Cursor, Claude Code, or equivalent)

Nice to Have

Experience with Okta Workflows, Experience with Tines, Experience with Workato, Another architectural decision you would do differently with a year of hindsight

What You'll Do.

Own the multi-quarter shape of the platform

Set the integration strategy

Drive the architectural direction for non-API integration patterns

Design the authoring framework

Design the integration testing infrastructure

Own the integrations strategy as a workstream

Drive architectural decisions across multiple quarters and multiple integrations

Design the authoring framework that lets FDEs

and AI agents extend the platform safely

Treat operability as part of platform design

How You'll Work.

Team & Collaboration

Pair on hard design decisions before they ship; Run design reviews as a teaching forum; Share the strategic and surge escalation surface with the engineering manager; Frame staff-shaped projects so other engineers on the team can take meaningful pieces

Communication Scope

Share the strategic and surge escalation surface

Process & Methodology

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

Full Job Description

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 t

Free ATS check

Applying for this Staff Software Engineer, Integrations Platform role?

Most applicants get filtered before a human reads their resume. See if yours makes the cut.

How to Apply on Greenhouse

  • Create a Greenhouse profile before applying — it saves time across multiple applications.
  • Upload your resume as a PDF; the parser handles it better than Word.
  • Answer all knockout questions carefully — wrong answers auto-reject before a human sees you.
  • Enable email notifications to track application status in real time.

ANONYMOUS · UNFILTERED

What do employees actually say about Fixify?

Real rants from real employees. Read before you apply.

Read Company Rants →