Six Figure Work

Platform Engineer

Dedalus Labs

Company websitededaluslabs.ai (Dedalus Labs, opens in new tab)

Base salary $120K – $250K

Employer-published annual base salary, USD. Advertised base range in San Francisco, CA

Apply (opens in new tab)

You apply on the employer's own site. Six Figure Work does not handle applications.

  • LocationSan Francisco, CA
  • WorkplaceOn-site
  • Status at last checkSource accepting applications when checked
  • Last checked (2 h ago) · observed since

About this job

About the role

Dedalus Labs builds persistent computers for AI agents. Our flagship product, Dedalus Machines, gives agents an isolated environment where they can run software, keep files and state, and work over time.

You'll own the internal platform engineers use to build, test, release, and operate our software. Your focus is CI/CD, GitHub Actions, build systems, release pipelines, and observability. A source change should move through a reliable pipeline, and a production failure should lead us to the relevant request, resource, release, and evidence.

You'll work across a large, fast-moving codebase to remove slow feedback, manual release steps, and gaps in visibility. Success means engineers ship safely with less coordination and can turn platform telemetry into concrete fixes.

What you'll work on

Build and CI infrastructure. Own GitHub Actions workflows, runners, test execution, build caching, and artifact storage. Reduce queue time, repeated work, flaky failures, and local/CI differences. Measure build latency and reliability as the codebase grows.

Our open-source tooling includes Bessemer (BSMR), our build system, and Hollywood, which generates GitHub Actions from typed TypeScript definitions and runs actions locally. Improve the tools themselves when their behavior limits the development workflow.

Release engineering. Build repeatable pipelines for artifact publishing, staging validation, promotion, production rollout, and rollback. Connect every running version to its source, build inputs, and tested artifact. Make failed releases diagnosable and recovery procedures testable.

Platform observability. Build consistent instrumentation across services and infrastructure. Correlate logs, metrics, traces, errors, and release events so engineers can follow an operation end to end. Turn that data into useful queries, dashboards, alerts, and investigations that identify regressions, bottlenecks, and affected users.

Efficient telemetry ingestion. Design and operate collectors and ingestion pipelines. Handle batching, buffering, retries, and backpressure, and detect delayed or dropped data. Manage sampling, retention, and metric cardinality so useful coverage scales without uncontrolled cost or lost diagnostic evidence.

Developer environments. Automate local setup and test environments, maintain shared tooling, and make common operations repeatable. Use containers, Kubernetes, and infrastructure as code where they support reliable development and delivery.

You'd be a good fit if

  • You treat other engineers as users. You investigate where their workflow breaks down, implement a fix, and follow through until they can use and troubleshoot it.

  • You can follow a failed build, release, or request across tools and services. You collect evidence, distinguish symptoms from causes, and make the next investigation easier.

  • You choose tests that establish the right guarantees, verify performance changes against a baseline, and explain the limits of the result. You can make a scoped improvement and ship it.

  • You communicate decisions clearly, act on feedback, and own the reliability of what you build. You can use AI tools and take responsibility for the resulting code.

Experience that helps

You have built or operated CI/CD, release infrastructure, developer tooling, or observability systems that other engineers rely on. You can write and debug software in TypeScript, Python, Go, Rust, or a similar language, and investigate failures on Linux.

GitHub Actions and release-pipeline experience are especially relevant. Build systems such as Buck2, Bazel, or Blaze, remote execution, and cache design are useful. For observability, experience with Grafana, Datadog, Sentry, OpenTelemetry, or similar tools should include instrumentation, ingestion, and using the data to make engineering decisions.

Experience at a big tech company or on another large, fast-moving codebase is a plus, not a requirement. We value what it taught you about code review, shared tooling, release discipline, and making changes other engineers can trust.

Show depth in one or more of these areas and the ability to learn the others. Explain the workload, scale, failure modes, and changes you personally owned. A degree, particular employer, or experience with every tool above is not required.

This role may be a poor fit if

  • You are satisfied with a green pipeline or a dashboard without checking whether it helps engineers release safely or diagnose failures.

  • You routinely accept flaky builds, manual release steps, or noisy alerts without investigating their cause.

  • You keep polishing after the agreed deadline or claim an improvement without measuring it.

Location and compensation

This is a full-time, in-person role in San Francisco. The annual base salary range is $120,000-$250,000 USD, depending on relevant experience and role scope. Relocation assistance and visa sponsorship are available.

Show us your work

Use your application to show us one thing you built and one difficult problem you investigated. They can come from the same project. Choose work you already have. We are not asking you to build a new project for this application.

  • Work: Show the code, demo, design, or result. Explain what you personally owned, what you reused, and one decision that made the result better or simpler.

  • Investigation: Describe the symptom, your first explanation, the evidence that changed your thinking, and how you established the result. Include the workload or users involved and any important limitations.

  • Writing: Share one piece of writing you care about as a separate, required sample. Any medium or length is welcome. Tell us why you wrote it, who it was for, and what you wanted to communicate. Looking back, what works well and what would you change? We care about the quality of your thinking and writing, and your reflection on the work. Link it or paste a redacted excerpt. Explain your contribution and any coauthors or AI assistance.

Work from employment, open source, research, coursework, or independent projects is welcome. Public source code is optional. A redacted excerpt or a concrete account of private work is fine. Keep confidential information out of your application.

Tell us which problem in this role you want to own and why. If your strongest evidence is easy to miss on a resume, point us to it. An existing demo or short screen recording is welcome, and video is optional.

Useful examples include a faster build, a release pipeline you made reliable, or telemetry that exposed a previously hard-to-diagnose failure. Explain the before and after, your contribution, and how other engineers used the result.

Source: Dedalus Labs on Ashby · View original posting (opens in new tab)

How this pay compares

Base floor $120,000, above 5% of the 4,902 Software Engineering roles in California on this site; the other 95% list the same floor or a higher one. The employer's range is $130,000 wide, 108% of the floor. Observed open for 26 days so far (since Oct 25, 2026).

Pay in context

Among 4,902 Software Engineering roles in California listed on this site, the median base floor is $176,361 and the middle half runs from $149,100 to $202,000. This role's floor ($120,000) is above 5% of them; 58 others list the same floor.

Base floors of 4,902 Software Engineering roles in California

Base floors of 4,902 Software Engineering roles in California$100K to $125K: 7.9% (386); $125K to $150K: 17.5% (859); $150K to $175K: 22.7% (1,111); $175K to $200K: 22.7% (1,111); $200K to $225K: 12.8% (626); $225K to $250K: 6.6% (324); $250K to $275K: 4.6% (227); $275K and up: 5.3% (258)0%8%16%24%8%10018%12523%15023%17513%2007%2255%2505%275This job $120K
Each bar counts postings on this site by published base floor, in $K. The marker is this job's floor.
Table
Base floors of 4,902 Software Engineering roles in California
Floor bandSharePostings
$100K to $125K7.9%386
$125K to $150K17.5%859
$150K to $175K22.7%1,111
$175K to $200K22.7%1,111
$200K to $225K12.8%626
$225K to $250K6.6%324
$250K to $275K4.6%227
$275K and up5.3%258
How this is calculated
Statistic
Base floor distribution of the cohort
Formula
count of cohort postings in each $25K band of published base floor / postings in the cohort
Denominator
4,902 open postings with this job family in California
Sample size
4902
Hidden when
the cohort has fewer than 30 postings
Calculation version
jobpage-analysis-v1
Data as of
2026-11-20
Employer set
Open jobs on this site that publish a base salary of $100,000 or more

Only jobs on this site count, and each one publishes a base salary of $100,000 or more, so this compares six-figure jobs with each other, not with the whole market. Computed Nov 20, 2026.

State against nationwide

Median base floor in California vs nationwide

Median published base floor of the same job family, in this state and across all states, next to this job's floor.
Table
Median base floor in California vs nationwide
Valuepostings
Software Engineering, California$176,3614,902
Software Engineering, all states$160K13,249
This job's base floor (marked)$120K
How this is calculated
Statistic
Median floor, state vs nationwide
Formula
median published base floor of each cohort
Denominator
open postings of this job family
Sample size
4902 in California; 13249 nationwide
Hidden when
either cohort has fewer than 30 postings
Calculation version
jobpage-analysis-v1
Data as of
2026-11-20
Employer set
Open jobs on this site that publish a base salary of $100,000 or more

Similar pay elsewhere

Other employers' Software Engineering roles in California with the nearest published base floor to $120,000, one per employer.

This range next to 1 other live Dedalus Labs role with the nearest advertised base floor
Chart as a table
This range next to 1 other live Dedalus Labs role with the nearest advertised base floor
RolePublished base
Platform Engineer (this listing)$120K - $250K
Systems Engineer$120K - $250K

Same $100K to $400K scale as every card. All Dedalus Labs roles · How to read the bar

Observed changes

  1. First observed on the employer's board, already publishing a qualifying base salary
  2. Listing details edited by the employer
Observed since
Employer-stated posting date
2026-09-29
Where this pay comes from

Location as the employer wrote it: San Francisco

USD 120,000 – 250,000 · 1 YEAR · Salary

Method
Structured pay field published by the employer
Checked
Rule set
us-base-v2

The employer's job board publishes this pay as a dedicated data field. We read the field directly; no interpretation was needed.

What we verified

  • The pay figures come from the employer's own listing, quoted exactly above.
  • The pay is an annual base salary in US dollars with a minimum of at least $100,000.
  • The role was publicly listed on the employer's job board when last checked.

We do not verify what the employer will actually offer, whether the employer is still recruiting for the role, or anything beyond what the employer published. Full methodology.

Get Six Figure Work by email

Pick what you want. Nothing is selected for you unless it matches the page you are on, and nothing is sent until you confirm from a link we email you.

What would you like to receive?

A short weekly note on what employer-published pay data shows: who pays what, where, and what is changing. Once a week.

Practical notes for job seekers: interviewing, applying for six-figure roles, and making an upward move. About twice a month.

New jobs that match a search you choose. Every job listed has an employer-published base salary of $100,000 or more. At most one email a day (or weekly, your choice). Nothing is sent on days with no new matches. Alerts cover every new job, because this page has no filters.

We email you only after you confirm from a link we send to this address. We do not sell or share your address. Every email has a one-click unsubscribe link. How we handle your email.