Start with the engineering connection
Name the role and lead with the closest relevant technical or product context. A developer who has worked on reliable backend services, customer-facing features or data-intensive systems can establish a useful bridge in one sentence.
Choose a project that demonstrates judgement
Explain a problem, your contribution, the technical approach and what changed. The best example may involve delivery, performance, reliability, developer experience, security or a difficult trade-off rather than a long technology list.
Show how you work with others
Software delivery involves product, design, quality, operations and other engineers. A letter can show how you clarify requirements, review work, learn from feedback or help a team ship safely.
Use the technology stack in context
Mention tools only when they help the reader understand the work. For example, a cloud platform may matter because you improved deployment reliability, not because its name appears in the role description.
Match the level of detail to the reader
A technical hiring manager may appreciate more depth, while an initial recruiter may need a plain explanation of why the work is relevant. Write clearly enough for both.
Keep claims interview-ready
Every technical contribution should be something you can describe in detail. Avoid using project language that suggests sole ownership when the work was a team effort.
Frequently asked questions
Questions people ask before they write.
Should I include GitHub in a developer cover letter?
Include it when the work is public, relevant and ready to represent you. A portfolio link is useful only when it strengthens the application.
Do I need to mention every technology from the job description?
No. Prioritise the technologies and engineering evidence you actually have, then explain how you can learn adjacent tools where that is true.