Staff Software Engineer

We're building the dev, build, and test cloud: the infrastructure layer that everything downstream of a code change runs on.

Our premise is that legacy CI/CD was designed for a world where a human wrote every line and waited for feedback, but that world is quickly passing by. Agents now generate enormous amounts of code and need to validate it continuously, before anyone gets a chance to review a pull request. The old platforms haven't kept up. We built RWX using the state of the art techniques in build systems but with an eye toward making those techniques more accessible to both agents and humans.

What you'll do

We're hiring a Staff Software Engineer to deliver across all of our product categories. This is a generalist role: you might be making changes to our logs UI one day and tweaking Linux kernel settings the next. We're looking for someone with great taste for software architecture and with impeccable problem-solving skills rather than a particular skill set, but being familiar with CI/CD, cloud computing, and Linux internals will be helpful.

What we're looking for

• Significant experience with complex technical systems.
• A strong product perspective.
• Excellent writing and communication.
• A background in reliable integration testing.
• A balanced approach to AI agents, taking advantage of their velocity without offloading thinking and understanding to them.

Nice to haves

We don't expect a single person to possess all of these attributes, but any one of the following would stand out:

• Deep experience with CI/CD and devops or platform engineering.
• Strong familiarity with Linux kernel development or Linux components like overlayfs, cgroups, and eBPF.
• A strong infrastructure background with experience in multiple clouds or racking physical servers.
• A strong social presence and an appetite for conferences, selling, and demoing with customers.
• Experience with advanced testing techniques like fuzzing and formal proofs.

How we work

We have a small team and place a lot of trust in every engineer. We expect everyone to take full ownership of the planning, execution, and release of all of their work. We use RWX to build RWX, so when something is annoying, it's annoying to us first and we fix it. We still carefully review code and do everything we can to prioritize reliability.