Senior Backend Engineer, Rust

About the role

You will advance the core infrastructure of a widely adopted Ethereum scaling solution through backend work in Rust. The role involves implementing and maintaining critical backend systems for a major blockchain ecosystem alongside a team of backend engineers. You will build foundational technology that shapes how decentralized applications interact at scale.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Implement backend services in Rust that power blockchain infrastructure and scaling solutions such as Arbitrum, Prysm, and ZeroDev, defining the APIs and data flows that applications depend on. These services uphold decentralization, security, and transparency for a global user base by enforcing protocol rules and consensus logic.

Build components that enable thousands of teams to deploy and operate their own blockchain chains using platforms like Arbitrum One, providing the execution environment and data availability they require. Maintain and extend the infrastructure that powers the Arbitrum stack and related ecosystem tools, ensuring reliability and performance under real-world load.

Requirements

Demonstrate strong proficiency in Rust and experience shipping backend services at scale, with a record of writing safe, concurrent, and performant systems. Have experience working with blockchain infrastructure or related distributed systems, understanding consensus, networking, and cryptographic verification.

Show ability to collaborate with multiple teams and integrate with tools such as Arbitrum, Prysm, and ZeroDev, contributing to shared protocols and interfaces.

Practical notes

US work authorization is required for this role. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Backend engineering roles rely on , low-level systems to keep digital infrastructure reliable and secure. Rust is widely used in performance critical and safety sensitive systems across the industry. Blockchain infrastructure teams often work with distributed systems concepts and cryptographic primitives. Tooling for scalable networks emphasizes correctness, concurrency, and maintainability. Engineers in this space typically collaborate with diverse product teams across a broad ecosystem.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.