Examples hub / Software engineering
Tech hiring teams want scope (services, traffic, data sizes) and ownership more than a bare list of languages.
Last updated: May 23, 2026 · Fictional sample names and employers for teaching only.
Use this as structure and proof style—not copy-paste text for your real application. Replace every fact with your license, metrics, and employers.
Alex Rivera Seattle, WA 206-555-0188 alex.rivera@email.com April 10, 2026 Engineering Hiring Manager Northwind Platform Seattle, WA Dear Hiring Manager, I am applying for the Software Engineer role on your platform team. Over the last three years at Contour Labs I owned the billing-events service (Go + Postgres, ~40k events/day) and cut p99 processing latency from 1.8s to 420ms by redesigning the consumer batching path and adding back-pressure metrics. I partner with product and support on incident reviews, write runbooks before launch, and treat code review as teaching—not gatekeeping. Your posting’s emphasis on observability and on-call hygiene matches how I already work: SLO dashboards first, clever abstractions second. I would welcome a chance to discuss how I can help Northwind ship durable APIs. My resume and GitHub are linked below. Sincerely, Alex Rivera
Lead with a production change users felt, then map your strongest system to their stack and team shape.
Open a full letter in the editor, then customize tone and details.
Many teams still ask for one or read it when provided. A short letter that explains ownership beats a blank submission when candidates look similar on paper.
No. Mirror the posting’s top three requirements with proof. Put the rest on your resume.
Use “I owned / we shipped / the metric moved” with scope. Credit teammates when the win was shared.