Page 1 of 2

Technical Writer, Security - Parapet Labs


๐—ฅ๐—ฒ๐—บ๐—ผ๐˜๐—ฒ | ๐—–๐—ผ๐—ป๐˜๐—ฟ๐—ฎ๐—ฐ๐˜

๐—ช๐—ต๐—ผ ๐˜„๐—ฒ ๐—ฎ๐—ฟ๐—ฒ:
Parapet Labs is a smart contract security firm. We protect DeFi and Web3 protocols that hold real money, by finding the flaws before an attacker does. Our work covers EVM and SVM code review, AI-assisted scanning, protocol design review and fix verification.

We are small on purpose and senior-only. The final report is what the client keeps, shows their investors and acts on. It has to be right.

๐—›๐—ผ๐˜„ ๐˜„๐—ฒ ๐˜„๐—ผ๐—ฟ๐—ธ:
Quality is the whole product, so quality is how we operate.

โ€ข ๐—ฆ๐—ฒ๐—ป๐—ถ๐—ผ๐—ฟ ๐—ฒ๐˜†๐—ฒ๐˜€ ๐—ผ๐—ป ๐—ฒ๐˜ƒ๐—ฒ๐—ฟ๐˜† ๐—ฒ๐—ป๐—ด๐—ฎ๐—ด๐—ฒ๐—บ๐—ฒ๐—ป๐˜. No juniors on client code.
โ€ข ๐—ฅ๐—ฎ๐—ป๐—ธ๐—ฒ๐—ฑ ๐—ฎ๐—ป๐—ฑ ๐—ฎ๐—ฐ๐˜๐—ถ๐—ผ๐—ป๐—ฎ๐—ฏ๐—น๐—ฒ. Every finding is severity-ranked and comes with a fix the team can ship.
โ€ข ๐—ช๐—ฟ๐—ถ๐˜๐˜๐—ฒ๐—ป ๐˜๐—ผ ๐—ฏ๐—ฒ ๐—ฎ๐—ฐ๐˜๐—ฒ๐—ฑ ๐—ผ๐—ป. Reports are for the engineers who fix the bugs and for the people who sign off on launch.
โ€ข ๐—™๐—ถ๐—ป๐—ฑ๐—ถ๐—ป๐—ด๐˜€ ๐—ฏ๐—ฒ๐—ณ๐—ผ๐—ฟ๐—ฒ ๐˜๐—ต๐—ฒ ๐—ณ๐—ถ๐—ป๐—ฎ๐—น ๐—ฟ๐—ฒ๐—ฝ๐—ผ๐—ฟ๐˜. Critical issues are communicated the same day.
โ€ข ๐—ฃ๐—ฟ๐—ผ๐—ผ๐—ณ ๐—ผ๐˜ƒ๐—ฒ๐—ฟ ๐—ฐ๐—ฟ๐—ฒ๐—ฑ๐—ฒ๐—ป๐˜๐—ถ๐—ฎ๐—น๐˜€. We care about what you have written, not where you have worked.

It is a high-standards environment. The bar is high, the feedback is direct, and every sentence is expected to earn its place.

๐—ง๐—ต๐—ฒ ๐—ฟ๐—ผ๐—น๐—ฒ:
You own report quality, and you are the public voice of our technical work. You take complex vulnerabilities found by our auditors and turn them into clear write-ups that founders and engineers can act on. You also write the post-mortems and technical articles that show the wider ecosystem how real exploits work and how to prevent them. You work closely with the auditors, so you will need to understand the exploit, not just edit the grammar.

๐—ช๐—ต๐—ฎ๐˜ ๐˜†๐—ผ๐˜‚ ๐˜„๐—ถ๐—น๐—น ๐—ฑ๐—ผ:
โ€ข Turn auditor notes and proofs of concept into clear, precise findings.
โ€ข Make sure every finding is correctly severity-ranked, reproducible and comes with a concrete fix.
โ€ข Edit ruthlessly: cut filler, remove ambiguity and make sure each finding stands on its own.
โ€ข ๐—ช๐—ฟ๐—ถ๐˜๐—ฒ ๐—ฝ๐—ผ๐˜€๐˜-๐—บ๐—ผ๐—ฟ๐˜๐—ฒ๐—บ๐˜€: analyze real exploits and incidents, reconstruct the attack step by step, explain the root cause and the lesson for builders.
โ€ข ๐—ช๐—ฟ๐—ถ๐˜๐—ฒ ๐˜๐—ฒ๐—ฐ๐—ต๐—ป๐—ถ๐—ฐ๐—ฎ๐—น ๐—ฎ๐—ฟ๐˜๐—ถ๐—ฐ๐—น๐—ฒ๐˜€: deep dives on vulnerability classes, audit techniques, fuzzing and invariant testing, and findings we are cleared to share, written for engineers and protocol teams.
โ€ข Work with auditors and researchers to turn their knowledge into publishable pieces, and get every technical claim checked before it goes out.
โ€ข Keep our report structure, templates and style guide consistent and up to date.
โ€ข Write summaries for a non-technical reader, such as a founder, investor or board member.
โ€ข Ask the auditor the question that exposes a gap in the explanation, before the client does.

๐—ช๐—ต๐—ฎ๐˜ ๐˜„๐—ฒ ๐—ฒ๐˜…๐—ฝ๐—ฒ๐—ฐ๐˜ ๐—ณ๐—ฟ๐—ผ๐—บ ๐˜†๐—ผ๐˜‚:
โ€ข ๐—” ๐—ฝ๐—ผ๐—ฟ๐˜๐—ณ๐—ผ๐—น๐—ถ๐—ผ ๐—ผ๐—ณ ๐˜๐—ฒ๐—ฐ๐—ต๐—ป๐—ถ๐—ฐ๐—ฎ๐—น ๐˜„๐—ฟ๐—ถ๐˜๐—ถ๐—ป๐—ด: audit reports, post-mortems, technical articles or documentation we can read.
โ€ข You can follow a smart contract exploit end to end, from on-chain transactions to root cause, and explain it precisely.
โ€ข You can write a long-form technical article that engineers finish reading and trust.
โ€ข Ruthless editing: severity-ranked, actionable, zero filler.
โ€ข A reader-first mindset, writing for the person who has to fix the issue tonight.
โ€ข You are comfortable asking technical questions until you fully understand the issue.
โ€ข You deliver on time and communicate clearly while working remotely.

๐—” ๐—ฝ๐—น๐˜‚๐˜€ ๐—ถ๐—ณ ๐˜†๐—ผ๐˜‚ ๐—ต๐—ฎ๐˜ƒ๐—ฒ:
โ€ข Basic Solidity reading skills, enough to follow the code a finding refers to.
โ€ข Previous experience writing or editing audit reports, security advisories, post-mortems or technical blog articles.
โ€ข Experience reading transactions and traces on a block explorer or with tools like Foundry or Tenderly to reconstruct an attack.
โ€ข Experience in DeFi or Web3 security.
โ€ข Experience building report templates, style guides or documentation systems.
โ€ข Public writing under your own name.

๐—ช๐—ต๐—ฎ๐˜ ๐˜†๐—ผ๐˜‚ ๐—ด๐—ฒ๐˜ ๐—ณ๐—ฟ๐—ผ๐—บ ๐˜‚๐˜€:
โ€ข Fully remote contract work, with your own schedule within delivery deadlines.
โ€ข Direct work with senior auditors, which means you learn how real exploits work from the people who find them.
โ€ข Real impact: your writing is what clients see, share and act on.
โ€ข A culture where quality is respected and writing is treated as part of the security work.
โ€ข Competitive compensation.

Tell us a bit more about yourself

Anything else we should know?

Upload your resume and cover letter

How did you hear about this job?

If a current employee at (company) referred you, please list his/her name

When can you start?