Drimva

ServiceNow

Staff FinOps Analyst

$176K–$308K

Santa Clara, CALIFORNIA, United States · Hybrid · Staff · Full-time · Posted Oct 28, 2026

Experience
8 years of related experience with a Bachelor's degree; or 6 years and a Master's degree; or a PhD with 3 years experience; or equivalent experience.
Education
Bachelor’s degree in a quantitative field (Computer Science, Engineering, Finance, Mathematics, or related).

About the job

Leads AI FinOps governance, cost monitoring, and optimization across ServiceNow’s AI investments, coordinating engineering, finance, and cloud providers.

What you'll do

  • Define AI cost and usage KPIs, detect anomalies, and work with engineering to investigate and remediate them.
  • Identify and deliver cost optimizations, establish preventive controls and spend guardrails, and coordinate the governance program.
  • Report AI cost trends, optimization progress, and forecasts to VP-level stakeholders.

What they ask for

  • Strong working knowledge of LLM pricing, multi-cloud AI services, and AI cost optimization levers.
  • Proficiency in SQL and/or Python for analysis, KPI frameworks, anomaly detection, and data visualization.
  • Hands-on multi-cloud cost governance across AWS, Azure, and GCP; proven engineering collaboration and executive communication skills.
  • Bachelor’s degree in a quantitative field (Computer Science, Engineering, Finance, Mathematics, or related).

Nice to have

  • Experience with AI optimization techniques such as model routing, prompt engineering, context management, batch inference, and caching.
  • Familiarity with provider budget and commitment tools, agentic AI cost patterns, or GenAI gateways and LLM proxies.

Pay

$176,100 - $308,200 USD base salary

Tools

SQL, Python, AWS Bedrock, Azure OpenAI, GCP Vertex AI, Azure Cost Management, AWS Budgets, GCP Billing controls

AI focus

Manages AI spend through usage analysis, anomaly detection, cost optimization, and governance of AI services and investments.

Model-written summary · the original posting is authoritative

First seen Oct 29, 2026 · Last verified Nov 6, 2026 (UTC)