Senior Backend Engineer at Harborline
Tomas Reyes's resume, tailored
All examples Invented people The product's real format
Summary
4 of 6 requirements are supported by the resume as written, one needs an answer from the candidate, and one is not shown, so it stays out rather than being invented.
What the posting asks for
Go in production
Skills; Quill, bullet 1
Postgres at scale
Quill, bullet 2
Performance work with measured results
Quill, bullet 1
On-call ownership
Quill, bullet 3
Kubernetes
Question
Event-driven architecture with Kafka
Not mentioned
No score. “Supported” names the sentence that supports it. “Not shown” means the resume says nothing about it, and neither will the tailored version.
The tailored summary
Backend engineer, six years in Go and Postgres. Cut p95 latency on the orders API from 840 ms to 190 ms and ran the on-call rotation for a 12-person team.
Each figure in this summary appears in a bullet below. The summary is assembled from them, not written over them.
Changes that matter
Original: Improved the performance of several services.Rewritten: Cut p95 latency on the orders API from 840 ms to 190 ms by rewriting the hot path in Go and adding two covering indexes in Postgres.In your own application you choose: use this wording, edit it, or keep your original.
Original: Took part in on-call.Rewritten: Ran the on-call rotation for a 12-person team, including the runbooks and the weekly review of pages.From your resumeWhy this changed: On-call ownership is named in the posting; the resume describes running it, not only taking part.
Source: “Ran the on-call rotation for the 12-person platform team, wrote the runbooks and led the weekly page review.” Quill, bullet 3.In your own application you choose: use this wording, edit it, or keep your original.
Original: Maintained the internal wiki.Left out.Left outWhy this changed: Not relevant to a backend posting. Keep it in if you want it.
Source: “Maintained the internal wiki.” Quill, bullet 6.In your own application you can keep this line in.
The rewrite we rejected
Rejected suggestion: Architected the migration to Kubernetes.Deployed services to the platform team's Kubernetes cluster.Rejected, original keptWhy it was rejected: Deploying to a cluster is not architecting the migration; the resume supports the former only. Checked against Quill, bullet 4.
The first draft proposed the struck line. The check found the resume does not support that level of ownership, reverted to the original wording, and shows you both so you know what was declined.
The one question we asked
An answer goes in as a bullet labelled “added by you”. Leave it blank and the resume says nothing about it. There is no checkbox that approves a claim on your behalf.
Tailor your own software engineer resume
Upload your resume and paste the posting. The first application is free, once, downloads included, no card.
Applications are not open yet. This page shows what one looks like.
Other roles
Account executive, SDR, Product manager, Data analyst, Customer success manager, Marketing manager, Project manager, Registered nurse, Financial analyst, Operations manager.
Source: “Reduced p95 latency on the orders API from 840 ms to 190 ms (Go rewrite of the hot path, two covering indexes in Postgres).” Quill, bullet 1.