Examples, end to end

Three complete pairs, three different careers.

A software engineer applying to a platform team, a marketing manager applying for a lifecycle role, and a registered nurse applying to the med-surg unit she has already worked on for seven years. Each pair shows the résumé and the cover letter the same person might send for one specific posting.

All names, employers, and metrics below are entirely fictional.

Example 1 · Software engineer
Fully fictional

Senior Software Engineer, Platform at Northwind Labs

Senior Platform role · Remote (US) · Distributed systems team · 5+ years of Go or Rust · Production Kubernetes at meaningful scale.

RésuméMaya Okafor
One page

Senior software engineer · Distributed systems

maya.okafor@example.dev · linkedin.example/mayaokafor · github.example/mokafor

Summary

Senior engineer with nine years building high-throughput backend systems in Go, with one production Rust service live for the past two. Most comfortable in the part of the stack between a queue and a database; happiest when the latency budget is tight and the failure modes are honest about themselves.

Experience

Senior software engineer

Harbor & Hatch — Remote · Apr 2021 – PresentOwned the redesign of the order-fulfillment pipeline from a per-tenant cron to a single shared worker pool. Throughput rose from 320 to 1,100 orders per minute at p99 under 800 ms, with no infra spend increase. Cut the on-call page rate in half by replacing three separate retry layers with one bounded retry, idempotency keys, and a documented replay path.

Software engineer

Cartograph Inc. — Brooklyn, NY · Aug 2017 – Mar 2021Shipped the geospatial indexing service in Go that the rest of the stack read from, replacing a Postgres + PostGIS path that timed out past 40k rows. Ran the migration as a five-week shadow read, then a one-week dual write, then a cutover that we never noticed on either side.

Software engineer

Larkspur Analytics — Boston, MA · Jul 2015 – Jul 2017Owned the MySQL → PostgreSQL migration of the reporting system. Wrote the per-tenant data audit that drove the cutover order, ran the dual-write window, and ended with a clean rollback path that we never had to use.

Selected projects

openpgp-batch

Maintainer of a small open-source library for batch-signing files with age-encrypted detached signatures. About 1.4k stars, used in two CI pipelines I do not own.

rfcgarden

A personal indexing tool that watches the IETF mail archive and surfaces the hundred most recently edited drafts; nothing public, mostly a way to keep my own reading habits honest.

Skills

Go (daily) · Rust (one production service, two side projects) · PostgreSQL · Redis · Kafka · Kubernetes · Terraform · Linux · gRPC · Prometheus / OpenTelemetry · Production on-call rotation habit

Cover letterFrom Maya Okafor
Warm, human

Dear Northwind hiring team,

Your platform posting calls out three things I have spent the last several years doing: the part of the stack that runs on a tight latency budget, the part where failure modes need to be named out loud, and the part where two teams need to share a queue without one of them quietly starving the other. I would like to do more of that work, on a team that has been writing about it long enough to be tired of the answer being "add another retry."

The bulk of my last four years has been in exactly that shape of system. The biggest was the fulfillment rewrite at Harbor & Hatch — a single worker pool replacing per-tenant crons — which took us from somewhere we could not reason about under load to a place where we ship with confidence on a Friday afternoon. I did most of that work alongside a small platform team; the design survived an engineer leaving, an SLO tightening that almost nobody noticed, and one genuine outage I will be happy to walk through.

Two specific things about the Northwind posting caught my eye. The first is the way you describe the on-call rotation — the part about "you will own the system you ship, including its 3 a.m." is the line I have written into my own job descriptions for the past three years. The second is that you are explicit about Kubernetes at scale rather than "cloud-native experience." I have spent the better part of a year debugging a control-plane-vs-data-plane race that landed in a Kubernetes upgrade, and I would welcome more of that shape of problem.

I have built my career on boring systems that are honest about themselves. Northwind is the same kind of shop. I would love to talk.

Sincerely, Maya Okafor

Example 2 · Marketing manager
Fully fictional

Marketing Manager, Lifecycle at Bramble Hill

Lifecycle marketing role · Hybrid (NYC, 2 days) · B2C subscription · Email, in-app, push · Owned retention metrics.

RésuméTheodore (Teddy) Brennan
One page

Lifecycle marketing manager · B2C subscription

teddy.brennan@example.email · linkedin.example/teddybrennan

Profile

Lifecycle marketer with seven years owning retention for direct-to-consumer subscription products. Strongest wherever the brief says "own this metric" and the metric is one of the three that actually move the business. Comfortable with the math; happier still with the writing.

Experience

Lifecycle marketing manager

Loomlight Tea Co. — Brooklyn, NY · Feb 2022 – PresentOwned the retention number end-to-end across email, in-app, and push. Took 90-day repeat-purchase rate from 28% to 41% over fourteen months, mostly by killing the four "blast to everyone" sends that were crowding out the actually-useful ones. Built the welcome series that 82% of new subscribers read end-to-end.

Senior email marketer

Northfield Outfitters — Remote · Jun 2019 – Jan 2022Owned the email program that grew from 180k to 410k active subscribers without any increase in churn. Created the quarterly pause-and-review ritual that catches a campaign going sideways a week before the metrics do.

Email marketing specialist

Cobbler & Crow — Manhattan, NY · Aug 2017 – May 2019Owned the holiday and gifting campaigns end-to-end. The Black Friday 2018 program is the one I am still proudest of, mostly because of how little of it was new — I almost entirely worked with what the team was already shipping.

Selected results

Welcome series refresh (Loomlight)

Three-email series replacing a single "thanks for signing up" send. Read-through went from 22% to 71%; first-purchase within 14 days rose from 19% to 34%; volume of confused support tickets dropped by half.

Subscription pause program (Loomlight)

A three-step pause flow that recovered an estimated $480k of at-risk ARR in its first two quarters. The flow worked because we wrote the copy with two former-pausers in the room.

Tools and skills

Customer.io · Iterable · Looker · dbt (read fluently) · SQL · A/B testing with holdouts · copywriting and editing · qualitative research with past customers · a quiet distaste for "synergy"

Cover letterFrom Theodore (Teddy) Brennan
Warm, human

Dear Bramble Hill team,

I read your lifecycle posting twice, because the second paragraph was the one that mattered: ownership of the retention number with the authority to do something about it. I have spent the last several years being the person who owns that number; I would like to keep doing that work on a team that has decided the answer is not "more emails."

At Loomlight, I owned retention end-to-end across email, in-app, and push. The biggest change was not a new campaign — it was killing four "blast to everyone" sends that were crowding out the ones people actually read. Ninety-day repeat-purchase moved from 28% to 41% over fourteen months, and the welcome series I wrote (with a former customer in the room for every revision) is the one I am most proud of.

Two specifics caught my eye about Bramble Hill. The first is the way your posting describes the role as "a marketing manager who can write." I am a marketing manager because I write — the campaigns that moved numbers at Loomlight moved them because the words in front of the buttons were the right words, and the ones that did not move anything were nearly always the ones whose words nobody had read carefully. The second is that you call out the subscription pause flow explicitly; I built exactly that flow at Loomlight and I would be glad to talk through what worked and what did not.

Thank you for reading. I would love to talk about retention in the shape it actually has at Bramble Hill.

Warmly, Teddy Brennan

Example 3 · Registered nurse
Fully fictional

Registered Nurse, Medical-Surgical at Greenbirch Regional

Med-surg RN · Full-time nights · 36 hours/week · Acute care hospital · Two years med-surg experience preferred · ACLS within first year.

RésuméDevon Alvarado, RN, BSN
One page

Registered nurse · Medical-surgical and step-down

devon.alvarado@example.email · compact RN license: NY #742113

Profile

Registered nurse with nine years on med-surg and step-down units in two acute-care hospitals. Steady on nights. The part of the work I am proudest of is the part that happens in the room — the part that no system measures well.

Licenses and certifications

New York State RN license #742113 (compact-eligible) · BLS, current · ACLS, current · Chemotherapy certification, 2022 · Charge-nurse readiness course, 2021

Experience

Registered nurse — medical-surgical

Greenbirch Regional — Hybrid (Saranac Lake, NY) · Jun 2018 – PresentCharge nurse on a 28-bed med-surg floor, 36-hour nights, average census 24. Precepted nine new graduates through their first year; six are still on the unit. Owned the falls-prevention huddle that brought unit falls from 2.1 to 0.7 per 1,000 patient days over a year.

Registered nurse — step-down

Wyandotte Medical Center — Wyandotte, NY · Aug 2015 – May 2018Step-down unit, 12 patients per shift on a 1:4 ratio. Comfortable with drips, vents, and post-op cardiac surgery; oncology-trained during the last year.

CNA

Lakeside Long-Term Care — Saranac Lake, NY · Sep 2013 – Jul 2015Where I learned that the work that matters most is the work that is not measured.

Education

Bachelor of Science in Nursing (BSN)

State University of New York, Plattsburgh · Class of 2015 · Cum laude

Affiliations

American Nurses Association · Sigma Theta Tau, Iota Omicron chapter · Hospital falls-prevention committee, 2021 – present

Cover letterFrom Devon Alvarado
Warm, human

Dear Greenbirch hiring committee,

I am applying for the med-surg night position at Greenbirch Regional because it is the same unit where I have worked for the past seven years, and because I would like to keep working on it. I have been a charge nurse on this floor long enough that I know where the danger spots are at 3 a.m. and where the room light leaks through the curtain. I would like to keep that knowledge in this building.

I have been a nurse for nine years, almost all of them nights, almost all of them on the same kind of unit. The work I am proudest of is the work that does not show up on a dashboard: the conversation with the daughter who is going to lose her father and does not know it yet, the sit-with-the-patient-five-minutes after the family leaves, the catch on the morning vitals that looked fine and were not. I have also done the work that does — the falls-prevention huddle I started on our floor brought falls from 2.1 to 0.7 per 1,000 patient days over a year, and I can show you the spread sheet.

Greenbirch is the hospital where I trained as a new graduate a decade ago and have stayed through two re-organizations and a pandemic. I know the night team, the day team, the environmental services team, and most of the night-shift hospitalists by first name. The posting asks for someone who can stabilize a unit on a hard shift and then make it slightly better by morning; that is what I have been doing on this floor for seven years, and I would like to keep doing it.

Thank you for reading. I would glad to talk about the floor, the night, and the work we still want to do on it.

Respectfully, Devon Alvarado, RN, BSN

From people who made the move

Loading buyer notes…

Paste your own résumé and a posting, and Hearthwright will tailor both — delivered to your inbox in about two minutes.

See the options