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.
To be successful in this role you have
Experience leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This includes current, hands-on fluency with AI-assisted and agentic development.
8+ years of software engineering with strong fundamentals in system design, API design, relational data modeling, and testing.
Hands-on depth building and operating third-party integrations that real tenants depended on — webhooks, rate limits, pagination, incremental sync, delete detection.
Experience designing API or SDK surfaces that another system consumes correctly without a human reading the documentation — and interest in doing that for a model.
Ownership of a versioned contract where a rename breaks a customer: stable identifiers, deprecation, and migration.
Sound judgment about least-privilege access — scope minimization per action, admin consent, secrets handling, tenant isolation — and about which actions an AI may take on its own.
Comfort with ambiguity and the drive to build from 0–1 without a playbook.
A record of technical leadership: architecture ownership, code-quality bar-raising, and mentoring engineers.
Nice to have
Experience evaluating tool or function selection — measuring whether a model picks the right action.
Experience with RAG or the Model Context Protocol (MCP).
Familiarity with SCIM or directory sync.
Background in IT service management or employee support products.
Why join us
Intelligence is commoditizing. Connection and execution are not. A model that reasons brilliantly and cannot act on the systems a company actually runs is a demo.
Flow already reaches a broad and growing share of the systems enterprises run day to day, and this team decides how fast that surface grows and how far each connection can be trusted. We aren’t writing connectors one at a time. We’re building the generator, the contract every provider follows, and the proof that what Flow says it did, it actually did. Real problems: a vendor specification that lies, an access model that must be mirrored exactly or not at all, a sync that resumes cleanly a million items later, and a tool surface a model has to get right without reading the documentation.
Work Personas
We approach our distributed world of work with flexibility and trust. Work personas (flexible, remote, or required in office) are categories that are assigned to ServiceNow employees depending on the nature of their work and their assigned work location. Learn more here. To determine eligibility for a work persona, ServiceNow may confirm the distance between your primary residence and the closest ServiceNow office using a third-party service.
Equal Opportunity Employer
ServiceNow is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, national origin, age, disability, gender identity, veteran status, or any other category protected by law. In addition, all qualified applicants with arrest or conviction records will be considered for employment in accordance with legal requirements.
Accommodations
We strive to create an accessible and inclusive experience for all candidates. If you require a reasonable accommodation to complete any part of the application process, or are unable to use this online application and need an alternative method to apply, please contact globaltalentss@servicenow.com for assistance.
Export Control Regulations
For positions requiring access to controlled technology subject to export control regulations, including the U.S. Export Administration Regulations (EAR), ServiceNow may be required to obtain export control approval from government authorities for certain individuals. All employment is contingent upon ServiceNow obtaining any export license or other approval that may be required by relevant export control authorities.
From Fortune. ©2026 Fortune Media IP Limited. All rights reserved. Used under license.
