Distributed Systems Engineer

Blockchain Lab analysis

Peer protocols aimed at model execution plus consensus, node metrics, and state sync across machines that do not do the same work.

It does not own the smart-contract API or the marketing site. A distributed-systems hire who cannot talk about failure detectors will be expensive noise.

Blockchain Lab analysis

Public reporting and the employer’s own releases. Not a relationship with Blockchain Lab. Not a credit opinion.

Founded

2023

Base

Distributed. No single headquarters is stated on the roles we store.

Status

Private. No token price, circulating supply, or revenue is treated as a fact in this brief.

People

A January 2025 secondary profile put the team near 30. That number is not current headcount.

1. 8 Nov 2023

   Seed, announced by the lead

   $25 million

   Archetype posted that it was leading Ritual's $25 million round. Blockworks called it a seed. Named participants in that coverage include Accomplice and Robot Ventures. Preqin also lists dao5, Anagram, Hack VC, and Dialectic. Some later blogs mislabel this round a Series A.

2. March 2025

   Series A, database-reported

   $25 million, unconfirmed here

   Preqin records a further $25 million with Accel, Avra, Hypersphere, and Polychain as new names, plus returning funds. This dossier did not find a Ritual press release for that round. Treat it as a database entry until the company confirms it.

• Runway and round status are not something you can read in a filing. Private company, one confirmed round.
• Mainnet, token, and fee switch are not facts this dossier will assert. The job text sometimes says mainnet. That is the employer's word. Ask what is actually in production.
• Stale reqs. The smart-contract posting was last updated on the board on 24 July 2024.
• The category is crowded and narrative-heavy. A coprocessor that cannot show a paid workload is a research project with a payroll.

Ask them

• Which round is the company actually operating on, and is the March 2025 Series A closed?
• What is live: Infernet, a testnet, a mainnet, a token? Who pays for inference today?
• Why has this specific req not been updated, and who would you report to?
• What is the public status of the Polychain / Eclipse matter?
• Is the role worldwide remote, or remote inside a list of countries the posting never names?

• Archetype announcement, 8 Nov 2023
• Blockworks seed coverage, Nov 2023
• Preqin asset profile, including the reported 2025 round

If a figure is not in those sources, it is not in this brief on purpose.

Illustrative preparation

Not the employer’s onboarding plan.

1. Days 1–30: sit with the existing simulation, if they have one. Measure it before you replace it.
2. Days 31–60: one networking change with a before-and-after under packet loss.
3. Days 61–90: a dashboard a validator operator can read without you in the room.

A week you can rehearse

• Draw the peer set. Say what a node is allowed to assume about a neighbour.
• Name the metric that would fire if inference nodes stalled and consensus nodes did not.
• Write the runbook line for a partition.

Illustrative preparation

• Tell a partial-failure story from a system you operated, with the graph you watched.
• Why is AI inference traffic a different peer-scoring problem from block gossip?
• What do you log, and what do you refuse to log, on a machine that sees other people's prompts?

Proof you can build before you apply

• The same state-machine lab, plus a note on what you would measure. A candidate who skips the measurement has missed the posting.

Open State-machine simulator. A small state machine with an honest path and one adversarial case.

• Protocol atlas
• Canon

• They describe the network as 'coming' and cannot show a testnet peer.
• On-call is undefined and the team is three people who all say someone else holds the pager.
• The privacy story for user prompts is 'we'll figure it out'.

Employer stated. This is a networking and reliability role: specialised nodes, consensus, and distributed execution, plus the monitoring that keeps that fleet honest.

• Design and implement distributed systems components for Ritual's heterogeneous compute network
• Develop and optimize peer-to-peer networking protocols optimized for AI model execution and blockchain consensus
• Build and maintain infrastructure for node monitoring, metrics collection, and system observability
• Architect solutions for efficient state management and synchronization across specialized nodes
• Collaborate with the research team to implement novel distributed systems algorithms

Source: the employer’s public Greenhouse record, job 4609616007. Open the original. First seen by this desk 2026-10-06. Nothing above the fold is a substitute for that page.

Blockchain Lab analysis. These lines are a reading of the advertisement. They are not extra hiring requirements.

• Separate the state transition from the networking story. They fail differently.
• Name the assumption the client makes about the peer set.
• Show a test where the honest path and the adversarial path diverge.

• Compensation, unless a figure appears in the header. None of these eighteen postings stated one.
• Closing date, and the day the role was first published. The board timestamp is an update.
• Which countries may apply. “Remote” alone is not worldwide eligibility. If the employer wrote “worldwide”, that sentence is theirs — still ask which entity can hire you.
• Visa sponsorship, on-call, and the employing subsidiary.