Writing: essays and notes on product engineering

Long-form writing by Sangeet Banerjee on realtime systems, infrastructure UX, growth engineering, and software craft.

Back to Sangeet Banerjee homepage

The resume is the site

By Sangeet Banerjee. Published 2026-02-18. 2 min read.

Humans barely read PDFs anyway. Screening is agents + a URL. The site is for both.

Tags: portfolio, hiring, meta

All writing

The resume is the site: article facts

Title
The resume is the site
Author
Sangeet Banerjee
Published
February 18, 2026
Updated
February 18, 2026
Reading time
2 min read
Summary
Humans barely read PDFs anyway. Screening is agents + a URL. The site is for both.
URL
https://sangeet.xyz/blogs/the-resume-is-the-site
Tags
portfolio, hiring, meta
Excerpt
If you hit Resume on my site, you get a short note instead of a file. That is intentional. Resumes barely matter the way people pretend For a lot of hiring now, no human carefully reads a multi-page PDF. A stack of applications gets skimmed by software, an internal bot, or someone pasting text into a model. The “resume” is often a lossy export that trails the real work. So shipping another PDF felt pointless. The website already is the document, and it can be readable by people and by agents. Built for both Humans get projects, links, context, a booking URL. Agents get structured pages, llms.txt, and other text routes. Paste sangeet.xyz into a screening agent. That is closer to how this generation of tools actually works than attaching SangeetBanerjeeResumeFinalv7.pdf. What a PDF would duplicate badly - Timeline and stack that go stale - Links that die on someone’s laptop - A version I forget to update after I ship I update the site when I ship. My PDF updated when I remembered. After someone asked for a résumé that was months behind live work, the gate felt more honest than a download. What I tell recruiters Use the URL. Or email hello@sangeet.xyz if you want a short human brief.…
.xyz
All posts
2 min read

The resume is the site

humans barely read PDFs anyway. screening is agents + a URL. the site is for both.

portfoliohiringmeta

If you hit Resume on my site, you get a short note instead of a file. That is intentional.

Resumes barely matter the way people pretend

For a lot of hiring now, no human carefully reads a multi-page PDF. A stack of applications gets skimmed by software, an internal bot, or someone pasting text into a model. The “resume” is often a lossy export that trails the real work.

So shipping another PDF felt pointless. The website already is the document, and it can be readable by people and by agents.

Built for both

Humans get projects, links, context, a booking URL.

Agents get structured pages, llms.txt, and other text routes. Paste sangeet.xyz into a screening agent. That is closer to how this generation of tools actually works than attaching Sangeet_Banerjee_Resume_Final_v7.pdf.

What a PDF would duplicate badly

  • Timeline and stack that go stale
  • Links that die on someone’s laptop
  • A version I forget to update after I ship

I update the site when I ship. My PDF updated when I remembered. After someone asked for a résumé that was months behind live work, the gate felt more honest than a download.

What I tell recruiters

Use the URL. Or email hello@sangeet.xyz if you want a short human brief.

Some ATS pipelines still want a file. Fair. Feed them the URL or text exports, or ask. I am not maintaining two sources of truth so a footer date can look official.

One URL

The résumé is irrelevant as a separate artifact when the site is already the source and the machines reading applications prefer URLs and structured text anyway.