Omar Hassan built his Staff packet in one Saturday afternoon.

September

Ben said he would sponsor Staff. Omar had nothing to attach.

Omar Hassan builds observability pipelines at Datadog in New York — Senior Engineer, six years in industry, two at Datadog. His manager Ben pulled him aside in September: “I want to put you up for Staff this cycle.” Then Ben asked for the promotion packet.

Omar opened Google Docs. Title: “stuff I did.” Body: empty. The work was real — ingestion latency cut, incident tooling adopted by three sister teams, a revenue-impacting launch in Q2 — but it was trapped in memory and scattered PR descriptions.

He had two weeks. He was not lazy; he had been heads-down shipping.

Saturday

Five wins he forgot he had shipped

He had logged in Grower inconsistently — mostly after big releases. Twelve entries total when he scrolled Saturday morning. Five he did not remember until he read his own words from April.

Polish pass tightened each: squad count, latency numbers, customer impact lines pulled from notes he wrote when he was tired but honest. Four hours start to PDF.

Sunday night he sent Ben the file. Monday Ben replied: “This is exactly what I needed for the packet.”

October calibration

Ben cited numbers Omar wrote in April — not improvised in the room

Omar was not in calibration. Ben was. The doc carried adoption metrics on the incident tool and ingestion SLA improvements with scope across teams — not “Omar is a great teammate.”

Staff track approved. Omar said the vault did not replace Ben’s sponsorship. It made sponsorship possible. Showing up with “stuff I did” empty would have burned the window.