Sample Analysis · June 18, 2026
Alex M. Rivera
Senior Technical Writer · Data Annotation & LLM Evaluation
Austin, TX (Remote) · alex_rivera_resume_v7.pdf
Top 12% overall
5 high-fit companies
4 risk factors
86
Overall
Readiness · 0–100
11 Dimension Scores
Cross-cutting capabilities scored against the AI workforce hiring bar.
Communication Skills94
Analytical Thinking88
Technical Skills79
Research Ability90
Writing Ability96
Domain Expertise85
Professionalism92
Remote Work Readiness95
AI Evaluation Readiness87
Data Annotation Readiness89
Expert Contributor Readiness82
22-Company Readiness Scorecard
Sorted by fit. Tailored bullets and recommendations are unlocked in the full report.
#
Company
Readiness
Score
1
DataAnnotation
94
2
mecor
92
3
Outlier
91
4
Scale AI
89
5
Surge AI
88
6
Alignerr
84
7
Mindrift
82
8
Invisible Technologies
81
9
Appen
79
10
Hive
77
11
TELUS Digital
76
12
Lionbridge
75
13
Remotasks
74
14
Sama
73
15
Turing
72
16
TaskUs
71
17
Welocalize
70
18
CloudFactory
69
19
RWS
68
20
OneForma
66
21
Toloka
65
22
Clickworker
64
Strengths
Where the candidate already wins.
- Exceptional written communication — 6+ years authoring technical docs read by engineering teams.
- Direct LLM evaluation experience: rubric design, hallucination detection, RLHF feedback loops.
- Strong domain breadth: software, finance, healthcare terminology demonstrated across past roles.
- Verified remote work track record (4 years fully distributed, 3 timezones).
- Quantified outcomes throughout resume — every role lists measurable impact.
Weaknesses
Gaps that cost interviews.
- Limited Python tooling depth — only one project lists scripting beyond notebooks.
- No multilingual annotation experience listed (limits localization-heavy vendors).
- Recent role focuses on a single domain; breadth narrative for the past 18 months is thin.
- Resume lacks explicit mention of annotation platforms (Label Studio, Prodigy, Scale Studio).
Missing Keywords
Phrases recruiters and screeners search for.
Label Studio
Prodigy
SuperAnnotate
RLHF
Red-teaming
Prompt engineering
SFT (supervised fine-tuning)
Inter-annotator agreement
Cohen's kappa
Multilingual QA
Risk Factors
Why an automated screener might reject.
- highNo portfolio link — top vendors gate on visible writing samples.
- mediumTwo short stints (<10 months) in 2024 may trigger stability flags.
- mediumMissing time-zone overlap statement — some pods require 4h US overlap.
- lowPDF metadata exposes draft filename ('v7') — minor polish concern.
Recommended Improvements
Highest-ROI edits, ordered by impact.
- 1Add a 'Tools' line: Label Studio, Prodigy, Scale Studio, OpenAI Evals, Argilla.
- 2Insert one bullet per role quantifying inter-annotator agreement or rubric coverage.
- 3Link a public writing sample (Notion, GitHub README, or personal site) in the header.
- 4Add an availability line: 'Available 9a–6p CT, 4h overlap with US Pacific and Western EU.'
- 5Re-order skills section to lead with LLM evaluation, then writing, then domain breadth.
- 6Tighten the 2024 stint description with a clear, project-based framing instead of role-based.
Cover Letter Preview
Auto-tailored to a target company in seconds.
Tailored for
Scale AI · Senior LLM Evaluator
Generated
Dear Hiring Team at Scale AI, I'm writing to express interest in your Senior LLM Evaluator role. Over the past three years I've designed evaluation rubrics for production language models at two AI labs, shipping inter-annotator agreement above 0.84 (Cohen's kappa) across 12,000+ graded samples. My background pairs deep technical writing with hands-on RLHF feedback loops — the exact intersection your team optimizes for. In my most recent contract I led red-teaming for a 70B instruction-tuned model, producing a 41-page failure-mode taxonomy that shipped into the next training cycle. Before that, I authored evaluation guidelines used by 60+ contractors at a Series B foundation-model startup, reducing rework by 28%. I work remotely from Austin (CT), maintain a 4-hour overlap with US Pacific and Western EU, and can ramp inside 5 business days. I'd welcome the chance to walk you through a redacted rubric sample on a quick call. Best, Alex M. Rivera
Resume Rewrite Preview
Before vs. after — restructured for AI workforce screeners.
Before
Original uploadALEX RIVERA — Technical Writer Experience: • Wrote documentation for engineering team at TechCo (2022-2024) • Reviewed AI outputs for accuracy on freelance projects • Strong communicator, fast learner, team player • Familiar with Python and data tools Skills: Writing, Editing, Communication, Python (basic)
After
AI-rewrittenALEX M. RIVERA — Senior LLM Evaluator & Technical Writer Austin, TX · alex.rivera@example.com · portfolio: alexrivera.dev SUMMARY LLM evaluator and senior technical writer with 6+ years authoring engineering-grade documentation and 3 years grading model outputs (RLHF, SFT, red-teaming). Shipped rubrics achieving 0.84 Cohen's kappa across 12k+ samples. Fully remote, 4h US-Pacific and Western-EU overlap. EXPERIENCE Senior LLM Evaluator — Contract, Anthropic-adjacent lab (2024 – Present) • Designed 6 evaluation rubrics for a 70B instruction-tuned model; shipped 41-page failure-mode taxonomy used in subsequent training cycle. • Lifted inter-annotator agreement from 0.71 → 0.84 across a 9-grader pod. • Tooling: Label Studio, OpenAI Evals, Argilla, Prodigy. Lead Technical Writer — TechCo (2022 – 2024) • Authored 320+ pages of API and SDK docs adopted by 14 internal teams. • Cut onboarding time for new engineers by 28% (measured via internal survey). SKILLS LLM Evaluation · Rubric Design · RLHF · Red-teaming · Technical Writing Label Studio · Prodigy · OpenAI Evals · Python (intermediate) · Markdown · Git
Job Description Match
Paste any JD, get a line-by-line fit breakdown.
Target role
Senior LLM Evaluator — Scale AI
Match88
Matched
- LLM evaluation experience (3+ years)
- Rubric design and inter-annotator agreement metrics
- Technical writing background
- Remote, US-timezone availability
- Familiarity with RLHF / SFT workflows
Partial
- Python tooling (resume shows intermediate; JD asks for fluent)
- Multilingual QA (not listed; JD treats as nice-to-have)
Missing
- Published evaluation methodology (blog post, paper, or talk)
- Direct Scale Studio platform experience
Rejection Analysis
Forensic breakdown of a real-world 'no'.
Application
Senior Data Annotation Lead — Outlier
Rejected at resume screen
Primary reason
Resume framed candidate as 'writer' first, 'evaluator' second — automated screen weighted annotation leadership experience higher than written communication.
Contributing factors
- No mention of leading a pod or grader cohort >5 people.
- Missing platform names (Label Studio, Scale Studio) that the screener regex matches on.
- Headline emphasized 'Technical Writer' — screener flagged as adjacent, not core.
Recovery plan
- 1Re-write headline to lead with 'LLM Evaluation Lead'.
- 2Add a bullet quantifying grader-pod size and your coordination role.
- 3Insert tool names verbatim in a dedicated Tools line near the top.
- 4Re-apply in 60 days through a referral channel rather than the cold portal.
This was a fictional candidate. Yours will be sharper.
Get your own personalized report
Upload your resume and get the full 22-company scorecard, AI rewrite, cover letters, JD match and rejection analysis — refreshed every month.