Senior Rust engineer, Sofia, Bulgaria · remote since 2019.

I write the part that has to stay up. Rust, mostly: indexers, languages, P2P protocols, and the tooling around them. Most of it is still running.

cargopete.com · resume · pavlovskipetko@gmail.com · linkedin

7 years 8 months shipping in production, Rust for the last five of them. 96 public repositories in The Night's Watch. 218 stars on Matchstick. 39 of 91 public repos in Rust, forks aside.

• nuthatch - be your own indexer. One Rust binary, one command, a live indexed API in under two minutes. Follows the chain, seals segments to Parquet, serves SQL and MCP, and has no mandatory third-party data dependency. A public good rather than a business.
• redstart - a language for authoring subgraphs. Schema, manifest and mappings collapse into one typed source that transpiles to AssemblyScript the canonical toolchain builds unmodified. The whole family of AssemblyScript footguns becomes unrepresentable. If it compiles, it works.
• yatr - a single-binary task runner whose cache is content-addressed and signed, so a shared cache entry can be trusted rather than hoped about. Speaks REAPI.

• matchstick (LimeChain for The Graph, on a Foundation grant, 2021) - unit testing for subgraphs, in Rust and WebAssembly. The ecosystem standardised on it. 218 stars, 17 forks, still maintained by others.
• graphcast and subgraph-radio (GraphOps, a Graph core dev team, 2022-2025) - a P2P messaging protocol for The Graph's indexer network, built on Waku and libp2p. Gossip, fault-tolerant delivery, and a radio pattern that lets anyone add a message type without touching the core.
• The Night's Watch - the unglamorous half of The Graph: indexers, gateways, data services, judges and doctors. Lodestar, Dispatch, Foghorn, horizon-doctor, Graphite, and learn-thegraph.com.
• Fathom - Rust services behind an AI data platform since April 2025: a multi-workspace monorepo, storage and control plane, and the dataops workflows that keep a model fed with something true.

Accountant before that, which is where the habit of checking the number twice comes from.

Open to senior Rust work, remote, contract or full-time. The lists below are here so that if you write, we both know within a paragraph whether it is going anywhere.

In: Rust backends, services and CLIs · distributed systems and P2P protocol work · blockchain indexing and data infrastructure · developer tooling, languages and testing frameworks · taking something that half works and making it hold · remote, EET, overlapping most of a European day.

Out: frontend as the main job (I ship React and Flutter when a project needs it, but it isn't what you want me for) · smart contract auditing (written contracts, not audited them for a living) · ML research (I build the pipelines, not the models) · relocation (overlapping some US hours is fine) · work where the architecture is settled and not open to a question.

This is also the source for cargopete.com - a static site, no framework at runtime. Built with Astro, deployed on Vercel, apex www.cargopete.com.

/ is the showcase. /blog/ is the writing. /resume/ carries the work history and the scope panel. The PDF at /resume/petko-pavlovski-resume.pdf is generated by yatr resume-pdf from src/data/resume.ts, the same file the page renders from, and yatr ci fails if the committed PDF and the data ever disagree. There is no hand-maintained CV: the last one still pointed at a GitHub handle that had moved on.

Posts are Markdown under src/content/blog/, one file per post, schema in src/content.config.ts. Frontmatter is title, date, description, optional tags, optional draft.

---
title: "A title"
date: "2026-09-02"
description: "One sentence. It is the listing subtitle and the feed description."
tags: ["rust", "astro"]
---

draft: true removes a post everywhere at once - the listing, the feed, the sitemap and getStaticPaths - so it has no URL at all rather than an unlisted one. Verified by building with a probe draft and grepping dist/ for it.

Code blocks go through Shiki with two themes and defaultColor: false, so every token carries --shiki-light and --shiki-dark and the theme picks one. With a single theme the toggle leaves one set of token colours on the wrong ground.

/rss.xml and /sitemap.xml are generated endpoints (src/pages/*.xml.ts), not files in public/. Both are hand-rolled rather than pulling in @astrojs/rss and @astrojs/sitemap: the site has two dependencies and this is forty lines of XML. The old public/sitemap.xml was hand-written, listed the homepage and nothing else, and would have gone stale the first time a post was added.

Built to the cargopete-style house skill. That means the palette is mandated rather than chosen: src/styles/global.css carries the skill's reference/tokens.css verbatim between two MANDATED markers. Edit those tokens in the skill and re-copy them here - never in this repo - so every site in the house style stays identical.

Texture is flat: no gradients, no shadows, hairline borders and whitespace doing the structural work. Light by default, with the dark theme a faithful inversion of it. Light is set as data-theme="light" on <html> server-side, so the inline script only has to undo it for a reader who chose dark, and a reader with JavaScript off gets the intended page rather than the other one.

The index rows on the homepage (.shelf) are borrowed from learn-thegraph.com, which runs the same house style. A catalogue reads better as a list of rows with a count on the left than as another grid of boxes.

Two light-theme contrast fixes are carried over from that site's design notes: the terminal title bar uses var(--bg-inset) rather than a color-mix the contrast validator cannot see, and the window title runs at --text-muted rather than --text-faint, which measures 2.49 on that bar in light and fails.

The terminal transcript in the hero is real output, run on 25 September 2026. Both commands can be pasted into a shell and reproduced. If the numbers drift, rerun them and update the page rather than rounding.

npm install
npm run dev          # http://localhost:4321
npm run build        # -> dist/
npm run check        # Astro types and content, and the resume PDF against its data

Or with yatr: yatr dev, yatr build, yatr ci.

After changing src/data/resume.ts, run yatr resume-pdf and commit the PDF with it. It prints the page with Playwright's Chromium, which is a one-off npx playwright install chromium; Vercel never runs it, it serves the committed file.

Fonts are self-hosted, subset with fonttools to the glyphs the page uses. Together they are 35KB, which is most of the page weight. Do not add a font CDN.

The favicon set is drawn, not imported. public/favicon.svg is the source of truth; scripts/make-favicon.py reproduces the same geometry as PNG and ICO with no dependencies beyond the standard library. Change both together, then run yatr favicon.