Staff Software Engineer, Integrations

About Team

Flow by ServiceNow is a standalone conversational AI service desk, with its own product and its own codebase. Employees ask for help wherever they already work — Slack, Microsoft Teams, email, or the browser. Flow answers from connected knowledge, handles the request, and runs automations the team publishes. AI is how the product works, and a person stays in control when the action is sensitive. 

Flow is a new company inside ServiceNow, reimagining every function from first principles. We hire builders with agency and curiosity who use AI as the default way to design, review, and operate. They challenge inherited ways of working and treat their work as craft. 

Flow is only as good as the systems it can read and the actions it can take. On the Integrations team, you’ll own how Flow connects to the systems companies run on, including identity, devices, ticketing, documents, and chat. You’ll turn them into three things: assets Flow can inventory, knowledge it can cite, and actions it can run. Every connection keeps each source’s permissions intact. 

In your first 12 months, you’ll make sure priority systems support assets, automations, and knowledge that Flow can actually use. Connection health and failed actions will be operable without a specialist in the room, and every new system will follow one contract for permissions, audit, and proof. 

Types of problems you’ll get to work on 

• Integration generation at scale. We don’t hand-write connectors. Build the pipeline that generates them from whatever a vendor publishes, which is often not a clean OpenAPI spec — and own spec normalization, pinned provenance, and deterministic regeneration across a growing catalog. 

• Tool surfaces an AI can actually call. An action’s name, description, schema, and examples are the product surface a model sees. Design them so the assistant picks the right action first try, scope them so they are safe for an AI to call, and measure whether it does. 

• Permissions and credentials you can prove. If a file is private to HR, a marketer must not see its title, its URL, or that it exists. Own access-model mirroring and delete detection, and pick the smallest credential policy each provider needs across validation, reconnect, revocation, and tenant isolation. 

• AI-native development itself. Agentic coding is how this team ships, not a productivity add-on. Author the skills and guardrails that let agents do integration work correctly, keep the deterministic provider-fake harness that makes fast iteration possible, and review generated code critically before anything ships. 

• Engineering leadership. Raise the technical bar through architecture decisions, code review, and coaching. Partner with product and design to shape requirements and explain tradeoffs clearly. 

Our stack 

TypeScript on Bun, PostgreSQL, Temporal for durable execution, Nango as the OAuth broker. We expect you to be excellent in a comparable stack and fluent in ours within weeks. We are not screening for this list.

Department: Engineering, Infrastructure and Operations
Function: Engineering
Experience Level: Not Applicable