Staff Systems Engineer, Rust / Data Infrastructure
Staff Systems Engineer, Rust / Data Infrastructure
Posted today
SENIORITY
Lead
About the role
- Help customers diagnose issues, debug workloads, and understand system behavior.
- Collaborate closely with product and design while retaining strong ownership of technical decisions.
- Share work with engineering and research communities through talks, papers, blog posts, and open-source releases.
- First 30 days
- Get comfortable with the architecture, codebase, tooling, and deployment process.
- Understand the main production workflows end-to-end.
- Ship a small feature or meaningful improvement.
- By 60 days
- Take ownership of one area of the platform and contribute actively to technical decisions.
- Debug real production issues and improve reliability, performance, or developer experience.
- Start working with junior members of the team, establishing trust and shared engineering standards.
- By 90 days
- Make meaningful improvements to existing systems with increasing independence.
- Lead the design of a significant new capability.
- Become a trusted leader in both operational and technical discussions.
- What our client is looking for
- You are an experienced engineer who enjoys building simple abstractions over complex distributed systems. You should be excellent at:
- Their lingua franca is Python, and they use a lot of Rust, but they're open to anyone who can demonstrate outstanding equivalent experience in relevant systems.
- Designing, implementing, and operating distributed systems.
- Concurrency, asynchronous programming, fault tolerance, and failure recovery.
- Building cloud-based infrastructure.
- Modern software-engineering practices, including Git, containers, infrastructure as code, CI/CD, testing, security, and observability.
- Reading and writing technical design documents.
- Leading technical discussions and communicating trade-offs at different levels of abstraction, mentoring younger engineers through technical leadership.
- Taking ownership of ambiguous problems from initial requirements through production operation.
- You should have working knowledge of:
- SQL and relational data systems.
- Object storage and cloud-native storage architectures.
- Distributed computation, whether through Kubernetes, Spark, query engines, or custom infrastructure.
- API and developer-tooling design.
- Finally, while not necessary, experience in one or more of the following areas would be especially valuable:
- Database internals, query planning, execution engines, or optimization.
- Apache Arrow, DataFusion, DuckDB, or related systems.
- Transaction processing, Apache Iceberg, or data catalogs.
- Serverless runtimes, function scheduling, or sandboxed execution.
- Type systems, formal methods, or distributed-systems simulation.
- Infrastructure for coding agents, agent evaluation, or autonomous software development.
- We don't expect one person to have experience across all these areas. They care more about strong fundamentals, intellectual curiosity, technical judgment, and the ability to learn unfamiliar systems quickly.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
