Staff Engineer, Infrastructure
- Sets technical direction across more than one team
- Track record of migrations that did not require a freeze
- Writes the design document others build from
Before: Contributed to the design of the event pipeline.
After: Wrote and drove the design for the event pipeline now carrying all product telemetry across four teams.
Why: Staff postings score scope. "Contributed to" reads as a participant at a level that is asking for an owner.
Before: Proficient in Java, Python, Go, Rust, TypeScript, C++.
After: (removed) Proficient in Java, Python, Go, Rust, TypeScript, C++.
Why: A language list is neutral at senior and negative at staff. The space is worth more spent on the migration.
Before: Helped migrate off the legacy schema.
After: Ran the expand/contract migration off the legacy schema over two quarters with no deploy freeze.
Why: They name the freeze explicitly. This is the sentence the posting was written to find.
- The posting implies people leadership. Nothing on your resume shows mentoring.
- No public writing linked; a staff posting that asks for design documents will look for it.
Gaps are shown rather than papered over. The assistant rewrites how something is said; it does not invent something you did not do.
