Principal Software Engineer - Platform Engineering Workflow Automation
ServiceNow
- Location
- Santa Clara, California, United States
- Employment
- Full Time
- Work model
- On-Site
- Level
- Principal
- H-1B history
- 185 approvals (FY2023)
- Posted
- 1h ago
Skills
About this role
Principal Software Engineer - Platform Engineering Workflow Automation Full-time Employee Type: Regular Region: AMS - North America and Canada Work Persona: Flexible or Remote Company Description It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people.
Job Description
About the team We build the workflow and automation engines that power how work gets done across the ServiceNow Platform. Our engines process billions of workflow transactions every month across enterprise customers, and we're now extending that foundation to support AI-native, agentic workflows. This is a team that cares about getting the architecture right, not just shipping features. We spend real time on performance, reliability, and making sure the platform holds up as customers push more volume and more complexity through it.
What you'll do
As a Principal Software Engineer, you'll take on hard architecture problems across our workflow and automation stack, including how we evolve it toward agentic, AI-driven execution at scale. Lead architecture and technical direction for problem areas across the portfolio, working with product and engineering leads to figure out what's blocking progress and where the real opportunities are. Get hands-on. Build the prototypes and reference implementations that prove out an architectural idea before a whole team commits to it. Test ideas with real experiments and real data, not just design docs. Use what you learn to shape the direction. Help move existing workflow capabilities toward AI-native patterns: agentic execution, better use of context and data, more autonomous flows, and connect that to concrete engineering work. Dig into cases where an agentic feature exists but isn't delivering the value it should. Figure out if it's the architecture, the data, the UX, or the cost model, and drive the fix. Write down the patterns and tradeoffs that work so other teams don't have to rediscover them. Sit in on design reviews and tough calls across teams. Push back with data when something looks risky, and help teams weigh shipping speed against long-term durability. Work across engineering teams to share what's working and help good patterns spread faster.
What we're looking for
15+ years of engineering experience, or equivalent. Real experience building and running large-scale distributed systems: workflow engines, integration platforms, data-heavy products, or cloud infrastructure. Solid grasp of system design for scale, reliability, observability, and production readiness, including database architecture at high transaction volume. Strong depth in Java, Python, or a comparable language. A track record of setting technical direction and influencing architecture across teams, even without a formal reporting line. Comfortable leading through credibility and collaboration rather than title. Good judgment on when to invest in long-term architecture versus when to just ship. Experience mentoring senior engineers and building patterns that other teams actually reuse. Experience with AI-powered products, agentic systems, or workflow automation platforms is a strong plus. Comfortable reasoning about AI-assisted workflows: data quality, correctness, evaluation, safety, and where a human needs to stay in the loop. Bonus if you've worked on large-scale enterprise customers or led complex platform migrations. Why this role You'd be shaping how our