Business Systems Analyst

Figma · San Francisco, CA • New York, NY • United States · Customer Operations and Support · listed October 7, 2026

The shape of it

Seniority
Mid level
Experience asked
3+ years
Where
Not stated
Stated pay
$105,000 – $245,000 USD
Requirements listed
5
Length
1,016 words

In the posting’s own words

As a member of the Operations & Strategy team within Customer Operations & Support (COS), you'll own and evolve the systems that power our support organization. This role is ideal for a well-rounded systems admin with deep Zendesk expertise and experience with Decagon, who enjoys working across many tools and can jump in wherever the team needs support. You'll help keep our support systems stable, well-designed, and adaptable, while partnering across teams to implement changes that improve both customer and Specialist experience.

What it asks for · 5

  • 3+ years of experience as a Zendesk administrator or Business Systems Analyst supporting a customer or product support organization
  • Deep hands-on experience with Zendesk workflows, routing, automations, business rules, queue architecture, and channel configuration, plus hands-on experience configuring Decagon and integrating it with Zendesk
  • Experience administering or supporting multiple tools across a support ecosystem, and the ability to learn new systems quickly
  • Experience leading systems changes independently or in partnership with Engineering, IT, Security, or Analytics
  • Strong communication skills, ownership, and sound judgment, with the ability to work effectively with technical and non-technical stakeholders while maintaining a high bar for quality, documentation, and execution

Also a plus

  • Zendesk Administrator certification
  • Experience configuring skills-based routing, intelligent routing, or classification
  • Experience with Zendesk Copilot, agent assist, or other AI-powered support tooling
  • Admin experience with Sprinklr, Gainsight, MaestroQA, Assembled, or Salesforce
  • Experience with APIs, webhooks, custom Zendesk apps, or scripting, plus SQL or analytics tools to evaluate workflow and tooling performance

What the job covers

  • Own and optimize the COS Zendesk environment, including workflows, business rules, automations, routing, permissions, and overall system health
  • Lead improvements to ticket classification, queue design, backlog management, and skills-based routing to help Support scale
  • Administer Decagon and its integration with Zendesk, including handoffs, escalations, and routing of AI-escalated tickets
  • Serve as a hands-on admin across our broader support tooling, including Sprinklr, Gainsight, MaestroQA, Assembled, among others
  • Evaluate and expand agent-facing AI capabilities, including Zendesk Copilot and other agent assist opportunities
  • Own the lifecycle of systems changes, including requirements, design, testing, rollout, communication, and post-launch monitoring
  • Create and maintain documentation across systems, including playbooks, operating procedures, change logs, and architecture diagrams

Tools and skills named

Product & design
  • Figma4×
Ways of working
  • Technical writing2×
  • Testing
Go to market
  • Salesforce
Languages
  • SQL
Security & compliance
  • Security

Words the posting leans on

  • experience11×
  • zendesk10×
  • support9×
  • systems9×
  • routing6×
  • design5×
  • changes4×
  • workflows4×
  • admin3×
  • customer3×
  • decagon3×
  • plus3×
  • tools3×
  • agent assist2×
  • analytics2×
  • architecture2×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Figma

every open role at Figma →

How this page was made

An automated read of a public job posting, fetched October 7, 2026 and last changed by Figma on October 7, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.