Use senior positioning consistently across public identity surfaces #94

New issue

Open

opened 2026-08-04 22:46:59 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-04 22:46:59 +00:00

Collaborator

Decision

Use senior as Kai's canonical level descriptor across public identity and recruiting surfaces.

Employment history remains factual and keeps employer-issued titles verbatim. In particular:

Nava remains Principal Infrastructure Engineer.
Textio remains Staff Infrastructure Engineer for 2022-2023 and Senior Infrastructure Engineer for 2018-2020.
Those titles describe specific historical jobs. They do not set the general public positioning.

Current mismatch

The live resume opens with "Staff platform engineer."
The live hiring page opens with "I am a senior platform engineer."
The GitHub profile currently says "staff-level platform engineer."

The hiring-page wording is canonical.

Required outcome

All generic present-day descriptions use senior, including resume headlines, introductions, website hero copy, repository-profile copy, and other public identity surfaces when they name a level.

Work-history entries continue to use the exact title held at each employer. Do not rewrite historical Principal, Staff, Manager, or Senior titles to manufacture consistency.

Acceptance criteria

The live resume uses senior rather than staff as its general level framing.
The hiring page continues to use senior.
The website hero and GitHub profile use senior wherever they state a current general level.
Any other public bio or profile touched by the canonical resume introduction uses senior.
Nava and both Textio entries retain their verbatim historical titles.
All other employment-history titles remain verbatim as well.
The platform, developer-infrastructure, and governed-agent-system throughline remains intact.
The wording does not imply two years of production agentic-LLM experience or otherwise overstate duration.
Apply the documented resume-surface synchronization and leave a LinkedIn sync reminder if relevant.
Verify the rendered live resume, live hiring page, and resume PDF after the change.

Non-goals

Tailoring the public pages to one company or requisition.
Expanding the intentionally narrow platform-engineering resume.
Changing compensation, location, employment, or interview filters.

## Decision Use **senior** as Kai's canonical level descriptor across public identity and recruiting surfaces. Employment history remains factual and keeps employer-issued titles verbatim. In particular: * Nava remains **Principal Infrastructure Engineer**. * Textio remains **Staff Infrastructure Engineer** for 2022-2023 and **Senior Infrastructure Engineer** for 2018-2020. * Those titles describe specific historical jobs. They do not set the general public positioning. ## Current mismatch * The live resume opens with "Staff platform engineer." * The live hiring page opens with "I am a senior platform engineer." * The GitHub profile currently says "staff-level platform engineer." The hiring-page wording is canonical. ## Required outcome All generic present-day descriptions use **senior**, including resume headlines, introductions, website hero copy, repository-profile copy, and other public identity surfaces when they name a level. Work-history entries continue to use the exact title held at each employer. Do not rewrite historical Principal, Staff, Manager, or Senior titles to manufacture consistency. ## Acceptance criteria * The live resume uses senior rather than staff as its general level framing. * The hiring page continues to use senior. * The website hero and GitHub profile use senior wherever they state a current general level. * Any other public bio or profile touched by the canonical resume introduction uses senior. * Nava and both Textio entries retain their verbatim historical titles. * All other employment-history titles remain verbatim as well. * The platform, developer-infrastructure, and governed-agent-system throughline remains intact. * The wording does not imply two years of production agentic-LLM experience or otherwise overstate duration. * Apply the documented resume-surface synchronization and leave a LinkedIn sync reminder if relevant. * Verify the rendered live resume, live hiring page, and resume PDF after the change. ## Non-goals * Tailoring the public pages to one company or requisition. * Expanding the intentionally narrow platform-engineering resume. * Changing compensation, location, employment, or interview filters.

coilyco-ops added the

autonomy

async-consult

priority

labels

2026-08-04 22:47:12 +00:00

coilyco-ops changed title from ~~Align staff-level and senior positioning across resume and hiring page~~ to Use senior positioning consistently across public identity surfaces

2026-08-04 22:50:12 +00:00

coilyco-ops added

and removed

labels

2026-08-04 22:50:13 +00:00

coilyco-ops added

priority

and removed