Software Engineer - Distributed Systems

Figma · San Francisco, CA • New York, NY • United States · Engineering · listed June 2, 2025

The shape of it

Seniority
Senior
Experience asked
5+ years
Where
Not stated
Stated pay
$153,000 – $376,000 USD
Requirements listed
6
Length
933 words

In the posting’s own words

At Figma, infrastructure is at the heart of everything we build. As a Software Engineer on our Infrastructure team, you’ll help design, build, and operate the systems that power our real-time collaborative design tools used by millions of people worldwide. We’re scaling fast, and we’re looking for experienced distributed systems engineers across a variety of teams. Whether you’re passionate about storage, compute orchestration, developer tooling, networking, or real-time data systems, this role offers an opportunity to shape the technical foundation of one of the most beloved design platforms in the world.

What it asks for · 6

  • 5+ years of Software Engineering experience, specifically in backend or infrastructure engineering..
  • Deep understanding of distributed systems concepts such as sharding, replication, consistency, and eventual convergence.
  • Experience with cloud-native environments (AWS, GCP, or Azure), infrastructure-as-code, and container orchestration.
  • Proficiency in languages such as Go, TypeScript, Python, Rust, or Ruby.
  • Strong system design skills and a track record of architecting resilient production systems.
  • Excellent communication skills, with experience collaborating across teams and mentoring others.

Also a plus

  • Experience scaling storage platforms (e.g., Postgres, Redis, S3, DynamoDB) or operating streaming systems like Kafka.
  • Background in traffic management, DDoS mitigation, or service mesh technologies (e.g., Envoy, Istio).
  • A history of developing complex, realtime distributed systems at scale.
  • A passion for building developer productivity tools, including development environments, CI/CD pipelines, and build systems.
  • Experience with evolving large-scale, shared developer platforms to improve reliability and developer velocity.
  • Strong problem-solving skills and a bias for action—especially when tackling high-impact, gritty challenges.

What the job covers

  • Design, build, and maintain scalable and reliable infrastructure systems that support product innovation and user collaboration at scale.
  • Architect and evolve distributed systems including storage platforms, streaming infrastructure, and compute orchestration.
  • Improve developer experience by building internal platforms, CI/CD systems, build tools, and APIs.
  • Collaborate across product and infrastructure teams to design secure, maintainable, and performant systems.
  • Participate in shaping platform strategy, roadmaps, and engineering best practices across the organization.
  • Debug and resolve complex production issues that span services and layers of the stack.
  • Mentor engineers and foster a culture of collaboration, inclusivity, and technical excellence.

Tools and skills named

Cloud & infra
  • Distributed systems4×
  • CI/CD2×
  • AWS
  • Azure
  • GCP
  • Kafka
  • Redis
Languages
  • Go
  • Python
  • Ruby
  • Rust
  • TypeScript
Product & design
  • Figma5×
Data
  • DynamoDB
  • PostgreSQL
Ways of working
  • Mentorship

Words the posting leans on

  • systems13×
  • design9×
  • platforms7×
  • experience6×
  • infrastructure6×
  • build5×
  • developer5×
  • distributed systems4×
  • collaboration3×
  • engineering3×
  • engineers3×
  • product3×
  • skills3×
  • tools3×
  • building2×
  • ci/cd2×

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 August 24, 2026 and last changed by Figma on August 12, 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.