Field Notes · by Erin Kerr

Tailoring your resume is step one.

Field Notes reads live job posts to find the words each field actually uses, and what those posts ask you to prove. Connect it to your AI assistant and check a resume against 6,624 real posts.

MCP server URLhttps://fieldnotes.erinkerr.me/mcp

Check a resume in your browserSee the fields

Add it to your assistant

Claude

In Settings, open Connectors and add a custom connector. Name it Field Notes and paste the URL above.

Claude Code

claude mcp add --transport http field-notes https://fieldnotes.erinkerr.me/mcp

Cursor

Add this to your mcp.json:

{
  "mcpServers": {
    "field-notes": {
      "url": "https://fieldnotes.erinkerr.me/mcp"
    }
  }
}

Any MCP client

It speaks Streamable HTTP at the URL above. No account, no sign-in, no key.

Then ask something like

10 fields so far

6,624 posts from 2,227 company boards. These are the most widely used of each field’s own words.

Design

265 posts · 98 companies · 2026-10-01

  • visual
  • craft
  • portfolio
  • interaction
  • figma
  • prototype
  • design systems
  • prototyping
  • user
  • quality
  • designing
  • thinking

Proof map: ready · See the field →

Software engineering

1,507 posts · 395 companies · 2026-10-05

  • design
  • code
  • systems
  • production
  • architecture
  • infrastructure
  • platform
  • building
  • technical
  • stack
  • cloud
  • python

Proof map: coming soon · See the field →

Data

365 posts · 161 companies · 2026-10-05

  • sql
  • python
  • analytics
  • models
  • analysis
  • modeling
  • science
  • datasets
  • insights
  • data quality
  • analytical
  • source

Proof map: coming soon · See the field →

Product management

397 posts · 174 companies · 2026-10-05

  • roadmap
  • engineering
  • strategy
  • vision
  • user
  • features
  • product strategy
  • execution
  • capabilities
  • metrics
  • launch
  • cross functional

Proof map: coming soon · See the field →

Marketing

584 posts · 262 companies · 2026-10-05

  • campaigns
  • content
  • strategy
  • channel
  • brand
  • audiences
  • creative
  • execution
  • market
  • media
  • execute
  • messaging

Proof map: coming soon · See the field →

Sales

1,544 posts · 368 companies · 2026-10-05

  • account
  • relationships
  • business
  • opportunity
  • executive
  • customer
  • market
  • value
  • growth
  • pipeline
  • success
  • deals

Proof map: coming soon · See the field →

Customer success & support

382 posts · 182 companies · 2026-10-05

  • issues
  • success
  • resolution
  • troubleshooting
  • onboarding
  • resolve
  • communication skills
  • customer experience
  • account management
  • escalation
  • customer success manager
  • customer facing

Proof map: coming soon · See the field →

Operations

822 posts · 260 companies · 2026-10-05

  • processes
  • operational
  • leadership
  • project
  • manage
  • execution
  • risk
  • program
  • cross functional
  • stakeholders
  • reporting
  • improvement

Proof map: coming soon · See the field →

Finance & accounting

418 posts · 171 companies · 2026-10-05

  • accounting
  • reporting
  • audit
  • processes
  • excel
  • reconciliations
  • prepare
  • analysis
  • report
  • close
  • control
  • tax

Proof map: coming soon · See the field →

People & recruiting

340 posts · 156 companies · 2026-10-05

  • hiring
  • candidate
  • hiring managers
  • sourcing
  • interview
  • talent acquisition
  • candidate experience
  • organizational
  • ats
  • full cycle
  • business partner
  • workforce

Proof map: coming soon · See the field →

What your assistant gets

list_roles
The fields it covers, their specialties, and how many posts each is based on.
get_field_vocabulary
The words a field's posts use far more than other fields' posts, with real lines from those posts.
get_proof_asks
What posts ask you to prove: shipped work, impact, craft, and the rest, most-asked first.
check_resume
Which of the field's common words a resume already uses, and which it's missing.
compare_with_posting
One resume against one job post: the field words it uses and the phrases it keeps repeating.
contribute_resume
Only with your explicit yes: saves the resume, contact details removed, to help this research. You get a delete code.
delete_contribution
Deletes a saved resume with its delete code, right away.

Ground rules

Reformulate, never fabricate.

Field Notes shows how your field describes the work. It isn’t a list of claims to add. Use a word only where your real experience backs it up, and every answer says so.

Nothing is kept unless you say yes.

Resume and job-post text is processed in memory to answer your question, then dropped. Saving a resume to help the research is a separate, opt-in step. Privacy

Real posts, dated.

Every quote is a short, verbatim line from a public job post, linked to its source. Each field shows the date its posts were read, so the data stays usable after the posts close.

How it works

  1. Reads live posts from public job boards (Greenhouse, Lever, Ashby, and Amazon), at most 15 per company per specialty so no single employer sets the averages.
  2. Finds each field’s own words: the ones its posts use far more than the other fields’ posts do, counted once per post and only when at least 5 companies use them.
  3. Sorts the lines where posts describe the proof they want into clusters, like shipped work, measurable impact, and craft.

It started as research for my portfolio redesign: an affinity map of 265 designer job posts, sorted by hand. erinkerr.me