Core Developer - Node

Addressed to

Parity

The letter

Dear Hiring Manager,

Core Developer - Node at Parity is building the infrastructure that powers blockchain networks like Polkadot and Kusama, systems where reliability, precision, and distributed collaboration define success. I follow the work because it addresses real coordination problems at scale, syncing nodes, producing blocks, managing network communication, not through abstraction but through code that runs in production. The fact that this is open-source means every decision is visible, reviewable, and accountable, which aligns with how I approach system design: as something that must hold up under scrutiny and function autonomously across time zones and teams.

In my recent work, I architected an AI-powered quality assurance pipeline that replaced manual inspection with a multi-agent system, each agent specialising in a different interface zone and a final LLM judge consolidating findings into structured defect reports. This wasn’t just about automation but about designing for consistency, removing human variability while ensuring the output was immediately usable by engineering teams. Similarly, in a data engineering project, I built ETL pipelines that ran without intervention, where validation cascaded automatically, and data integrity was guaranteed at each stage. These experiences taught me how to design systems that work not when watched, but when left alone, critical in distributed environments where failure surfaces slowly and silently.

I am a Tunisian software engineer who has learned to work asynchronously by necessity and preference, structuring communication around written updates and reproducible results rather than synchronous presence. I apply for this role to focus on blockchain infrastructure where automation and precision matter most, using AI not as a replacement for logic but as an accelerator within orchestrated systems. I ask to join Parity’s remote team in 2026, contributing to node development with the same rigor I’ve applied to pipelines that run unattended, because the systems I trust most are those that work when no one is looking.

Sincerely,
Chedy Chaaben

Delete this letter