Platform and Developer Experience Engineer

Workweek

5d•Remote

About The Position

Most platform roles hand you a backlog of tickets. This one hands you a mandate. We're moving to a model where small, autonomous teams — including non-engineers using Claude Code and Cursor — ship experiments fast. That only works if the infrastructure underneath is safe: if anyone on the team can build and ship without accidentally corrupting data, breaking the design system, or losing the ability to roll things back. This role exists to build that infrastructure. You are not building features. You are building the system that makes it safe for everyone else to build features fast. This is a high-leverage, low-visibility role. The best outcome is that the team never notices you exist — because nothing breaks. You'll work closely with our engineering lead and report to our Director of Engineering.

Requirements

4 or more years of experience in platform, DevEx, or infrastructure engineering, with strong CI/CD depth — GitHub Actions, automated testing pipelines, enforcement gates
Enough frontend range to write meaningful automated PR review rules, enforce component standards, and understand what a missing feature flag actually means in practice
AWS and observability fluency — Cloudwatch, alerting, and a working model of what platform changes can break and how to detect it fast
Experience working in a lean, fast-moving codebase — you know how to add guardrails without adding drag, and you default to automation over process
Claude Code or Cursor experience — you've used AI-assisted coding in a real codebase and understand how context quality affects output quality. Writing CLAUDE.md is not a novelty to you.
High agency. You identify the risk surface and close it without waiting to be asked.

Nice To Haves

You've written skill files or system prompts that encode domain-specific rules, worked on a Rails codebase through an AWS migration, or built tools that let non-engineers ship safely without needing to ask an engineer every time.

Responsibilities

Own the AI context layer — write and maintain CLAUDE.md and skill files with the same rigor you'd apply to a CI/CD pipeline. These are the primary guardrail for non-engineers using Claude Code. If Claude writes something wrong and no one can catch it, it ships.
Own the CI/CD layer — feature flag enforcement, automated PR review, Playwright smoke tests, Cloudwatch alerts. The safety net that catches what Claude's context missed.
Enforce frontend standards automatically — not through checklists, but through gates that reject non-compliant code before it merges.
Keep observability tight — automated alerting on platform changes and key experiment metrics, so regressions surface before anyone notices.
Contribute to dead code removal on both frontend and backend, reducing the risk surface and giving Claude a cleaner codebase to reason about.
Automate documentation so it stays in sync with the codebase — Claude should never be working off stale context.
Help close out the ongoing Rails to AWS migration, a dependency for the broader platform guardrails work.
Contribute to the shared infrastructure that makes the whole team faster, not just your own work.

Benefits

Competitive pay (we don't pay based on location, we assign value to the role)
Equity in Workweek
Remote operations with the ability to work in the time zone of your choice (or work IRL in our Austin, TX office)
Unlimited PTO with a minimum of 3 days/quarter used
100% health insurance coverage, 75% coverage for dependents, and $150/month towards an HSA (or $150/month health stipend if insurance not used)
120 days of parental leave to use within one year of childbirth (available 12 months after your start date and only available every 365 days)
401(k) plan with 3.5% company match
$500 one-time stipend for any home office needs used after the first 90 days
5-week sabbatical after 4 years on staff
2 volunteering days per year
1x/year in-person team retreat
$100/month book stipend