Open source

The résumé is the sum of its parts.

Store each piece on its own, and keep a variation tailored to the role.

  • Experience
  • Education
  • Summary
  • Project
  • Skills
  • Talk

Compose the variation that fits the job.

Two close roles can share the same work and still ask for a different wording. The account service stays in both résumés. The summary and the release checks change: Playwright for the AI engineer, Jest and manual QA for the CRM developer.

Every wording stays in the library. The role you select marks the records in that résumé.

Amina Okonkwo

Product engineer who ships model features and checks them with Playwright.

Experience

  • Account serviceBoth roles

    Built the account service both the assistant and the CRM call.

  • Shared formsBoth roles

    Kept the form components both products use.

  • Release checksAI engineer

    Covered the assistant flow with Playwright, from the prompt to the saved result.

Summaries

  • AI engineerIn this résumé

    Product engineer who ships model features and checks them with Playwright.

  • CRM developer

    Product engineer who ships the customer workspace and checks it with Jest and manual QA.

Experiences

  • Account serviceIn this résumé

    Built the account service both the assistant and the CRM call.

  • Shared formsIn this résumé

    Kept the form components both products use.

  • Release checksIn this résumé

    Covered the assistant flow with Playwright, from the prompt to the saved result.

  • Release checks

    Covered the account screens with Jest, and walked the rest with manual QA.

resume.json

Amina Okonkwo

Product engineer who ships model features and checks them with Playwright.

Work

  • Product engineer, Account service

    • Built the account service both the assistant and the CRM call.
  • Product engineer, Release checks

    • Covered the assistant flow with Playwright, from the prompt to the saved result.

Projects

  • Shared forms

    Kept the form components both products use.

Skills

Playwright

A model can see which configuration fits.

Paste a JSON Resume document and the editor already knows the shape. Work, projects, skills, and the other blocks become records in the library. Download the library as a JSON backup when you want a file, and print a PDF from those same records.

An agent with API access can list résumés, search the blocks, add a bullet, or clone a version. Because it can follow which project belongs to which job, a draft and an email can both start from the configuration you would have picked by hand.

Local first. The server is a choice.

Editing happens in this browser. Lists open without a round trip, and a change is stored before anything is sent. The workbench stays quick when you are offline, and the library on this machine is the one you are actually changing.

Sign in and turn managed sync on when you want those changes copied to the server. A public résumé is published separately, so you can share one snapshot and keep the working library to yourself.

Local edits

149 this window

Click a day to record another edit.

SMTWTFS
LessMore

On this machine

Edits stay in the browser. Nothing is waiting to leave.

Managed sync