Principal Software Engineer
ServiceNow
Get hot jobs first on Telegram
New positions appear faster in our channel
- Location
- United States, Canada
- Job Type
- full-time
- Work Format
- 🌍 Remote
- Salary
- $221,200 - $387,100
- Posted
- November 21, 2026
Job Description
Principal Software Engineer
- Building A,B,C 2225 Lawson Lane, 95054 Santa Clara, CALIFORNIA, United States Employees can work remotely
- 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
As a Principal Software Engineer in the AI Experiences organization, you will define and own the technical direction for the ServiceNow design system and set the direction for the future of frontend development at ServiceNow. The Application AI Experiences team builds the frameworks, components, and tools that every ServiceNow application interface is built on. We are extending that foundation so people and AI agents can work together across the platform, through generative UI, agent-ready components, and new ways of interacting with applications.
The strategic decisions you make will influence hundreds of applications and thousands of developers building on the ServiceNow platform. You will define architectural standards, influence technical direction across teams, and help ensure the design system remains the fastest and most scalable way to build on the platform.
What you’ll do
-
Architect: Own the architecture of the component and widget model, including API design, tokens and theming, accessibility, and versioning. Define governance and contribution models that scale across teams while driving adoption, consistency, and long-term maintainability of the design system.
-
Build the agentic layer: Design and build how AI agents use the design system, both coding agents building UI and agents composing interfaces at runtime. Define machine-readable component metadata, schemas, and usage guidance written for agents. Design the consumption model and the evaluation model to hill climb to successful agentic usage over time.
-
Work hands-on: Write high-quality, high-performance code across the component library and tooling. Prototype quickly, review closely, and lead large initiatives from proposal through rollout.
-
Improve developer experience: Set standards for how UI code is written and shipped, including driving consistent toolchains across teams.
-
Own UI performance and quality: Drive rendering performance, accessibility, and real-user measurement across the experiences built on the design system.
-
Execute cross-functionally: Work with design to keep design assets and shipped code in sync. Work with product, application, and AI experience teams so the design system is the fastest way to build.
-
Raise the bar on culture: Mentor senior and staff engineers, champion engineering excellence, and set the standard for frontend work across the organization.
-
Drive technological change: Find gaps in the platform, propose solutions, align stakeholders, and lead migrations.
Qualifications
-
12+ years of software engineering experience, with principal-scope impact setting architecture across multiple teams.
-
Experience using AI in your own engineering work and evaluating it critically. This includes coding agents, AI-assisted review and testing, and a clear view of how AI changes the way UI is built at scale.
-
Experience designing component libraries, developer platforms, or frontend systems that can be effectively consumed by AI-assisted development workflows and emerging agentic systems. This can include structured component schemas, MCP or similar tool interfaces, agent-oriented documentation, and evaluation of agent-generated UI for correctness, consistency, and accessibility.
-
Built and maintained an enterprise design system or component library used by many teams and thousands of developers in production. API design, design tokens, theming, versioning, and deprecation should be second nature to you.
-
Deep expertise in TypeScript, JavaScript, and the web platform (DOM, CSS, browser rendering). Hands-on experience with Web Components (Lit or similar) and at least one major framework such as React.
-
Accessibility expertise: WCAG 2.2, ARIA patterns, testing with assistive technology, and building accessibility into shared components so teams get it by default.
-
Web performance experience, including profiling, bundle and rendering optimization, server rendering and hydration, and real-user monitoring.
-
Frontend infrastructure experience with build tools, monorepo tooling, CI/CD, and testing strategy across unit, visual regression, and end-to-end tests.
-
Self-driven with strong ownership and demonstrated success establishing technical standards, influencing architectural decisions, and driving adoption at scale.
-
Demonstrated success driving technical strategy and influencing architectural decisions across multiple teams and stakeholders without direct authority.
Additional Information
JV21
For positions in this location, we offer a base pay of $221,200 - $387,100, plus equity (when applicable), variable/incentive compensation and benefits. Sales positions generally offer a competitive On Target Earnings (OTE) incentive compensation structure. Please note that the base pay shown is a guideline, and individual total compensation will vary based on factors such as qualifications, skill level, competencies, and work location. We also offer health plans, including flexible spending accounts, a 401(k) Plan with company match, ESPP, matching donations, a flexible time away plan and family leave programs. Compensation is based on the geographic location in which the role is located and is subject to change based on work location.
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.
By clicking the link above or any third-party link within this posting, you are leaving this site and going to a third-party website where the third-party website's terms and privacy policy apply
🎯 Who is this job for?
Level: Senior/Principal—suited to an engineer with 12+ years of experience and a record of setting frontend architecture across multiple teams.
Required skills: Deep TypeScript, JavaScript, web platform, Web Components, React, accessibility, performance optimization, design systems, AI-assisted development, frontend infrastructure, testing, and CI/CD expertise.
Relevant tasks: Designing and governing enterprise component libraries, building agent-ready UI systems, writing high-performance code, improving developer tooling, leading migrations, ensuring accessibility and quality, and influencing technical strategy without direct authority.
💬 Potential Interview Questions
How would you architect an enterprise design system that supports thousands of developers across multiple application teams?
I would define stable component APIs, design tokens, accessibility contracts, contribution governance, and clear ownership boundaries. I would also establish compatibility policies, documentation standards, automated quality gates, and adoption metrics to keep the system consistent and maintainable at scale.
How would you design a versioning and deprecation strategy for a shared TypeScript component library?
I would use semantic versioning, explicit API stability levels, codemods, migration guides, and a defined deprecation window. Breaking changes should be rare, observable through usage telemetry, and supported by automated compatibility and upgrade tooling.
How would you make design-system components consumable by AI coding agents and runtime UI agents?
I would provide machine-readable component schemas containing props, states, events, accessibility requirements, composition rules, and examples. Agent-facing documentation and tool interfaces should constrain invalid combinations while enabling evaluation of correctness, visual consistency, accessibility, and task success.
What considerations are important when implementing Web Components with Lit alongside React applications?
I would define clear interoperability contracts for properties, attributes, custom events, slots, and form behavior, while handling React’s event and property semantics carefully. I would also standardize SSR, hydration, styling, and testing patterns so components behave consistently across frameworks.
How would you design an accessible component library aligned with WCAG 2.2?
Accessibility should be built into component APIs and interaction models through correct semantics, keyboard support, focus management, ARIA patterns, and contrast requirements. I would combine automated checks with screen-reader testing, keyboard testing, and accessibility acceptance criteria for every component.
How would you diagnose and improve frontend performance in a large design system?
I would profile bundle size, rendering, layout, hydration, and interaction latency using browser tooling and production telemetry. Improvements could include tree-shaking, code splitting, efficient DOM updates, virtualization, server rendering, hydration optimization, and removal of unnecessary dependencies.
Which real-user performance metrics would you track, and how would you use them?
I would track Core Web Vitals such as LCP, INP, and CLS, along with bundle size, error rates, component render cost, and task-specific interaction timings. Segmenting results by application, device, browser, and component version helps prioritize changes and detect regressions after releases.
How would you structure build, testing, and release infrastructure for a frontend monorepo?
I would use task orchestration with dependency-aware caching, reproducible builds, incremental CI, and clear package boundaries. The pipeline should include unit tests, type checking, accessibility tests, visual regression tests, end-to-end tests, and automated release validation.
How would you evaluate AI-generated UI before allowing it into production?
I would evaluate functional correctness, schema compliance, accessibility, responsive behavior, visual consistency, security, and performance using deterministic tests and representative user tasks. Human review remains important for ambiguous cases, while evaluation data should continuously improve prompts, metadata, and agent tooling.
How would you drive adoption of a new frontend architecture across teams without direct authority?
I would align stakeholders around measurable problems, provide a compelling reference implementation, and make the preferred path easier through tooling, documentation, migration support, and strong defaults. I would use pilot teams, transparent metrics, feedback loops, and incremental rollout rather than relying solely on mandates.
📋 Job Summary
ServiceNow is an AI platform company helping businesses connect data, workflows, and intelligent automation. As a Principal Software Engineer, you’ll shape the architecture of its enterprise design system, build agent-ready components and tooling, improve accessibility and performance, and influence frontend standards across hundreds of applications. The stack includes TypeScript, JavaScript, Web Components, Lit, React, DOM/CSS, monorepos, CI/CD, and automated testing. This is a full-time flexible or remote role in North America, offering a base salary of $221,200–$387,100 plus equity, incentives, and benefits—an opportunity to define the future of AI-powered UI at global scale.
Required Skills
Never miss a JavaScript opportunity
Subscribe to get similar jobs and weekly insights delivered to your inbox
Hiring JavaScript developers?
Post your job to 10,500+ registered developers. Starting free.
See PricingRelated jobs
Is this your listing? Claim or request removal