Feedback Guide

Tell us what worked and what didn't.

This MVP is the first cut. Real-world feedback is the only thing that gets us to a useful tool. Skim this page before you open an issue so your feedback lands in the right place.

Where to send feedback

Open a new GitHub issue with the feedback label.
Use the feedback channel in the Tech Immigrants community.
If something is broken, use a bug report instead.

What to include

What you were testing (web UI, CLI, eval harness).
What you expected vs. what happened.
The role or archetype you were aiming for.
Your browser / OS / Node version (for web UI / CLI bugs).

⚠ Privacy: don't paste your real CV

GitHub issues are public. Before sharing an example, anonymize it:

Replace your name with "Candidate A".
Replace company names with "Company X".
Remove phone, address, and email.
Keep the bullet structure and metrics — that's what we need to see.

If you accidentally paste a real CV, edit or delete the comment immediately. We can't un-share what you post on GitHub.

Sample anonymized feedback

Browser: Chrome 124 on macOS 14
What I tried: A 1-page SWE CV against a Python backend JD
Result: Score 2.1/5
Surprise: Keyword Match scored 5/5 but Tooling Visibility scored 1/5,
even though I named every tool in the CV. The two should agree.
Anonymized snippet:
  - "Built Candidate A service in Company X serving 50M requests/day"
  - "Migrated Postgres to a sharded cluster, scaling writes 5x"
Suggestion: weight Tooling Visibility by exact JD keywords, not just
archetype keywords.

Five questions that help

Was the feedback useful?
Was the score understandable?
What was missing from the result?
Would you trust this for your own CV today?
What role or archetype should we support next?

← Back to evaluator Open a feedback issue ↗