Senior Infrastructure Engineer
Own the bare metal, networks and platforms behind OpenInfra, NoLimitNodes and HyperliquidRPC, where a millisecond is a feature and downtime is a refund.
- Location
- Toronto, Canada
- Type
- Full-time, hybrid
- Team
- Infrastructure
About CLR3
Our products promise things most providers will not put in writing: sub-millisecond round trips, four nines of uptime, streams that sustain over a hundred thousand messages a second. Somebody has to make those numbers true every day. That is this role.
You will run the fleet behind OpenInfra, NoLimitNodes and HyperliquidRPC: bare-metal servers, private networking, validators, RPC nodes and the observability that watches all of it. You will also advise clients on their own infrastructure when engagements call for it.
What you will do
- Run and grow our bare-metal fleet: provisioning, networking, storage and capacity planning
- Keep our latency and uptime promises honest with real measurement and alerting
- Operate Solana and Hyperliquid node infrastructure, including upgrades and incident response
- Automate everything that gets done twice, from provisioning to failover
- Design private networking and peering so data takes the shortest path
- Handle escalations and take part in a sane on-call rotation
- Advise clients on infrastructure during consulting engagements
What we are looking for
- Years of hands-on experience running production infrastructure, ideally bare metal as well as cloud
- Strong Linux fundamentals: networking, storage, performance tuning and debugging under pressure
- Experience with infrastructure as code and configuration management
- Comfort with monitoring and observability stacks, and opinions about what to alert on
- A track record of being calm and useful during incidents
- Able to work from our Toronto office part of the week
Nice to have
- Experience running blockchain nodes or validators at scale
- Familiarity with high-performance networking, kernel tuning or DPDK-style work
- Experience with Kubernetes and with deciding when not to use it
- Background in data centre selection, peering and transit negotiation
- Scripting or systems programming in Go, Rust or Python
Who you are
- You think uptime numbers should be measured, not marketed
- You would rather automate a task than document a manual process
- You stay calm when the pager goes off and honest in the postmortem
- You enjoy squeezing latency out of systems most people consider fast enough
- You like owning things end to end
How we hire
- 1Intro call with an engineer, about 30 minutes
- 2Deep-dive conversation about systems you have run and incidents you have handled
- 3Practical exercise built around a realistic infrastructure scenario
- 4Conversation with the founders
- 5Offer
Apply
Email careers@clr3.org with a short note about yourself, a link to your GitHub or past work, and a CV if you have one. We read every application and reply to all of them.
Apply for this role