Loading…
Loading…
Best practices for resumes. Many of these tips are drawn from the excellent r/EngineeringResumes wiki, which I'd recommend reading in full. While the source is engineering-focused, these principles apply to any profession.
"When the checkout service experienced 500ms latency spikes (S), I was tasked with reducing p95 latency below 200ms (T). I implemented Redis caching for session data and optimized database queries (A), reducing p95 latency to 120ms and improving conversion rate by 8% (R)."
"Reduced API response time by 40%, as measured by New Relic p95 metrics, by implementing Redis caching and query optimization."
"Facing a 3x increase in user traffic (C), redesigned the data pipeline using Apache Kafka (A), enabling real-time processing of 2M daily events with zero downtime (R)."
Applicant Tracking Systems parse resumes as text. Image-based PDFs, fancy tables, and multi-column layouts often get mangled or ignored.
Resume Builder outputs clean, single-column, text-based PDFs where every character is selectable and parseable. No images, no tables, no surprises.
The resume builder is fully private. Everything you type is saved to your browser's local storage and never sent to any server. The PDF is generated entirely on your device. No account needed, no uploads, no tracking.
You can optionally create a free account to save multiple resume versions for different job applications. Saved resumes are stored securely in the database so you can access them from any device.
If you use the Interview Prep feature, you'll also need an account. Your prep materials will be stored alongside your resumes. Payment info is handled by Stripe and never stored on this site.
Without an account, your resume lives only in your browser's local storage. If you clear your browser data or switch devices, your progress will be lost. Download your PDF regularly to keep a copy.