<svgtabindex="0"aria-labelledby="title desc"role="img"xmlns="http://www.w3.org/2000/svg"viewBox="0 0 19.9 19.7"><titleid="title">Search Icon</title><descid="desc">Icon to open search</desc><gclass="search-path"fill="none"><pathstroke-linecap="square"d="M18.5 18.3l-5.4-5.4"/><circlecx="8"cy="8"r="7"/></g></svg>
<p>Status is building the tools and infrastructure for the advancement of a secure, private, and open web3.</p>
<p>With the high level goals of preserving the right to privacy, mitigating the risk of censorship, and promoting economic trade in a transparent, open manner, Status is building a community where anyone is welcome to join and contribute.</p>
<p>As an organization, Status seeks to push the web3 ecosystem forward through research, creation of developer tools, and support of the open source community.</p>
<p>As a product, Status is an open source, Ethereum-based app that gives users the power to chat, transact, and access a revolutionary world of DApps on the decentralized web. But Status is also building foundational infrastructure for the whole Ethereum ecosystem, including the Nimbus ETH 1.0 and 2.0 clients, the Keycard hardware wallet, and the Waku messaging protocol (a continuation of Whisper).</p>
<p>As a team, Status has been completely distributed since inception. Our team is currently 100+ core contributors strong, and welcomes a growing number of community members from all walks of life, scattered all around the globe.</p>
<p>We care deeply about open source, and our organizational structure has minimal hierarchy and no fixed work hours. We believe in working with a high degree of autonomy while supporting the organization’s priorities.</p>
<p>This role will be part of a new team that will make a provable and private WASM engine that runs everywhere. As a research engineer, you will be responsible for researching, designing, analyzing and implementing circuits that allow for proving private computation of execution in WASM. This includes having a deep understanding of relevant ZK proof systems and tooling (zk-SNARK, Circom, Plonk/Halo 2, zk-STARK, etc), as well as different architectures (zk-EVM Community Effort, Polygon Hermez and similar) and their trade-offs. You will collaborate with the Vac Research team, and work with requirements from our new Logos program. As one of the first hires of a greenfield project, you are expected to take on significant responsibility,while collaboratingwith other research engineers, including compiler engineers and senior Rust engineers.</p>
<p><strong>Key responsibilities</strong></p>
<ul>
<li>Research, analyze and design proof systems and architectures for private computation</li>
<li>Be familiar and adapt to research needs zero-knowledge circuits written in Rust Design and implement zero-knowledge circuits in Rust</li>
<li>Write specifications and communicate research findings through write-ups</li>
<li>Break down complex problems, and know what can and what can’t be dealt with later</li>
<li>Perform security analysis, measure performance of and debug circuits</li>
</ul>
<p><strong>You ideally will have</strong></p>
<ul>
<li>Very strong academic or engineering background (PhD-level or equivalent in industry); relevant research experience</li>
<li>Experience with low level/strongly typed languages (C/C++/Go/Rust or Java/C#)</li>
<li>Experience with Open Source software</li>
<li>Deep understanding of Zero-Knowledge proof systems (zk-SNARK, circom, Plonk/Halo2, zk-STARK), elliptic curve cryptography, and circuit design</li>
<li>Keen communicator, eager to share your work in a wide variety of contexts, like internal and public presentations, blog posts and academic papers.</li>
<li>Experience in, and passion for, blockchain technology.</li>
<li>Experience in provable and/or private computation (zkEVM, other ZK VM)</li>
<li>Rust Zero Knowledge tooling</li>
<li>Experience with WebAssemblyWASM</li>
</ul>
<p>[Don’t worry if you don’t meet all of these criteria, we’d still love to hear from you anyway if you think you’d be a great fit for this role. Just explain to us why in your cover letter].</p>