coilysiren/website

Watch

Refocus the resume around governed AI platform engineering #84

New issue

Closed

opened 2026-08-03 00:51:10 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-03 00:51:10 +00:00

Collaborator

Parent

Private Inbox epic

Actor

Design role.

Outcome

Refresh the canonical resume surface so the first screen makes Kai's Staff-level AI platform fit legible without turning the resume into a company-specific artifact.

Context

This is the first half of a time-boxed resume and hiring-page polish pass. The target role shape values shared agent-development infrastructure, developer experience, orchestration, MCP and A2A, evaluation, context systems, model routing, observability, governance, Kubernetes, Terraform, Python, and TypeScript.

Kai already has direct evidence across agentic-os, agent-compose, Ward, cli-guard, MCP services, Kubernetes infrastructure, and observability work. The design problem is information hierarchy and evidence selection, not inventing a new career story.

What to build

Put the Staff platform-engineering thesis, current location eligibility, and strongest agent-platform evidence in the top third.
Make governed agent execution, developer enablement, production operations, and cross-repository architecture easier to scan.
Name Python, TypeScript, Kubernetes, Terraform, MCP, observability, and model-routing work where the existing record supports them.
Prefer outcomes and architectural judgments over repository inventory.
Honor the repository's canonical resume generator and every documented resume or bio synchronization surface.
Preserve an ATS-readable, printable, mobile-readable result.

Acceptance criteria

The first screen positions Kai clearly for Staff AI platform and developer-infrastructure work.
The strongest relevant evidence appears before lower-signal history.
Every claim is supported by the existing resume, public repositories, or reviewed source material.
The public page, generated resume artifact, and documented synchronized intro surfaces agree.
Links work in an incognito session and the page is readable on a phone.
Repository validation passes and the change lands through the repository's normal workflow.

Blocked by

None. Start immediately.

Non-goals

Do not name a prospective employer.
Do not invent metrics, scale, customers, chronology, or hands-on depth.
Do not rewrite the entire career history.
Do not delay the outbound response for marginal polish.

## Parent [Private Inbox epic](https://forgejo.coilysiren.me/coilysiren/inbox/issues/319) ## Actor Design role. ## Outcome Refresh the canonical resume surface so the first screen makes Kai's Staff-level AI platform fit legible without turning the resume into a company-specific artifact. ## Context This is the first half of a time-boxed resume and hiring-page polish pass. The target role shape values shared agent-development infrastructure, developer experience, orchestration, MCP and A2A, evaluation, context systems, model routing, observability, governance, Kubernetes, Terraform, Python, and TypeScript. Kai already has direct evidence across agentic-os, agent-compose, Ward, cli-guard, MCP services, Kubernetes infrastructure, and observability work. The design problem is information hierarchy and evidence selection, not inventing a new career story. ## What to build * Put the Staff platform-engineering thesis, current location eligibility, and strongest agent-platform evidence in the top third. * Make governed agent execution, developer enablement, production operations, and cross-repository architecture easier to scan. * Name Python, TypeScript, Kubernetes, Terraform, MCP, observability, and model-routing work where the existing record supports them. * Prefer outcomes and architectural judgments over repository inventory. * Honor the repository's canonical resume generator and every documented resume or bio synchronization surface. * Preserve an ATS-readable, printable, mobile-readable result. ## Acceptance criteria * [ ] The first screen positions Kai clearly for Staff AI platform and developer-infrastructure work. * [ ] The strongest relevant evidence appears before lower-signal history. * [ ] Every claim is supported by the existing resume, public repositories, or reviewed source material. * [ ] The public page, generated resume artifact, and documented synchronized intro surfaces agree. * [ ] Links work in an incognito session and the page is readable on a phone. * [ ] Repository validation passes and the change lands through the repository's normal workflow. ## Blocked by None. Start immediately. ## Non-goals * Do not name a prospective employer. * Do not invent metrics, scale, customers, chronology, or hands-on depth. * Do not rewrite the entire career history. * Do not delay the outbound response for marginal polish.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-03 00:53:15 +00:00

coilyco-ops commented

2026-08-03 02:05:16 +00:00

Author

Collaborator

Landed in ffc01ca433, with the synchronized public profile intro in github.com/coilysiren/coilysiren@de6b196e04. The semantic resume now leads with Staff-level governed agent-platform evidence and supported skills, remains ATS-readable on the web, and generates a visually verified two-page PDF from the same canonical source.

Landed in https://forgejo.coilysiren.me/coilysiren/website/commit/ffc01ca433ca54f4af1f574465a0ccd652b2d0fd, with the synchronized public profile intro in https://github.com/coilysiren/coilysiren/commit/de6b196e04bf3455ebb763f3290adb95c75a7c2a. The semantic resume now leads with Staff-level governed agent-platform evidence and supported skills, remains ATS-readable on the web, and generates a visually verified two-page PDF from the same canonical source.

coilyco-ops closed this issue

2026-08-03 02:05:17 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilysiren/website#84

No description provided.

Rows
Columns