Is Odile Brantwick a real person

No. She is invented for this page, and so are Marrowfield Systems, Halvard Pay and Tessellate Werke. The numbers were written to give the engine something real to select from. Nobody applied with this letter and nobody was hired with it.

Did the product really write this letter

Yes. The evidence list on this page was loaded through this page's own door, the company city was typed into the field Details & drafting asks for, and Write the letter was pressed. The reply is printed above unchanged, blocks and all. The engine reports its own provenance: eight requirements read in the posting, eighteen evidence lines offered, eight sentences traced to a numbered line of them, ten written from named connective patterns, two gaps, no model.

A requirement the posting asks for that the evidence cannot support. Here they are Rust and SOC 2. The letter names both in one factual sentence and claims neither. They are shown to you as well, because the honest place to answer them is a conversation.

What does “Use this example” do

It opens the cover letter builder in Details & drafting with the role, the company, the posting and the four evidence groups already loaded, exactly as an imported résumé would load them. No application record and no letter exists until you press Create new draft.

Does the letter change if I choose another voice

The three voices change the subject line, the opening, the fit sentence and the closing. The evidence sentences are Odile's own lines and they do not change, because a voice is a style and evidence is a fact. Changing the voice keeps the draft you already have as a version first.

Which design is this example in

Modern, a quiet asymmetric grid. The door opens the builder on it. Any of the 12 designs carries the same words, and the gallery shows each one as a whole letter rather than a thumbnail.

Example · Engineering

A free software engineer cover letter our own engine wrote, and what it refused to say

One backend engineer cover letter, printed exactly as the builder wrote it: sender block, date, recipient, subject, four paragraphs and a sign-off. The person and the posting are invented. The letter, the tracing and the gaps came out of the product.

ConxfolioPublished 2026-09-13 · updated 2026-09-14

— three of these paragraphs are hers. the rest are joins.

The finished cover letter in the letter builder in the Classic design: sender block, date, recipient block, subject line, salutation, four paragraphs and a sign-off — The letter this page quotes, on the letter builder in the Classic design. The picture was taken by pressing this page's own door, typing the company city Details & drafting asks for, and pressing Create new draft.

Most engineering cover letter examples are a finished page with no working shown. This one prints the input beside the output. Odile Brantwick is invented, Marrowfield Systems is invented, and every employer written under her name is invented too. What is real is the letter itself: the evidence below was loaded into the cover letter builder through this page's own door, and the whole business letter that came back is printed here without a word changed.

Odile Brantwick and Marrowfield Systems are invented, and so are the employers in the evidence; the letter below is the builder's own output from that evidence, unchanged.

The job, and the evidence the letter may use

An invented person. Not a real document, and not yours.

The role
Backend Engineer · Marrowfield Systems

The posting
Marrowfield Systems is hiring a backend engineer for the payments team. You will work in Go and Python against PostgreSQL, run services on Kubernetes and own the reliability of the settlement path. We ask for Terraform, Kafka and real on-call experience. Rust and SOC 2 audit work are useful.

What the letter may claim

Cut end-of-day reconciliation from 40 minutes to 6 by rebuilding the settlement pipeline in Go.
Reduced PostgreSQL cost by 31% by moving cold ledger rows to partitioned storage.
Migrated 14 services from a shared monolith to independent deployments on Kubernetes.
Ran the on-call rota for the payments team and saw incidents fall from 9 to 2 a quarter.
Automated the Terraform review that used to take two engineers a morning.

Where it happened

Senior Backend Engineer · Halvard Pay · 2021 — present
Backend Engineer · Tessellate Werke · 2018 — 2021

Skills it may name

Go
Python
PostgreSQL
Kubernetes
Terraform
Kafka
gRPC
incident response

The letter the builder wrote, in full

221 words in the direct voice. 8 of its 13 sentences quote a numbered line of Odile's evidence; the rest are the builder's own connecting sentences.

Odile Brantwick
Backend Engineer
[email protected]
Rotterdam, Netherlands

26 September 2026

Hiring Team
Marrowfield Systems
Rotterdam

Re: Backend Engineer

Dear Marrowfield Systems Hiring Team,

I'm applying for the Backend Engineer role at Marrowfield Systems. Backend engineer with six years on payment systems, working on reliability, cost and the parts of the stack nobody volunteers for. You ask for PostgreSQL, and that is work I have already done: Reduced PostgreSQL cost by 31% by moving cold ledger rows to partitioned storage.

I have worked as Senior Backend Engineer at Halvard Pay, 2021 — present. I have also worked as Backend Engineer at Tessellate Werke, 2018 — 2021. I cut end-of-day reconciliation from 40 minutes to 6 by rebuilding the settlement pipeline in Go. I also migrated 14 services from a shared monolith to independent deployments on Kubernetes.

On Terraform: Automated the Terraform review that used to take two engineers a morning. I also ran the on-call rota for the payments team and saw incidents fall from 9 to 2 a quarter. The posting asks for PostgreSQL, Golang, Kubernetes and Terraform — all of which I've worked with directly. The posting also asks for Rust and SOC 2, which I have not used in these roles.

I would welcome the opportunity to discuss the role. Thank you for considering my application.

Sincerely,
Odile Brantwick

Two small things are worth naming.

How every letter on these pages is built from its evidence is set out in how our examples are made.

The Conxfolio cover letter builder on Details & drafting, opened by this page's own door, with the role Backend Engineer, the company Marrowfield Systems, the posting and the four evidence groups loaded — Details & drafting holding Odile Brantwick's evidence for this software engineer post.

The same Details & drafting section on a 390 pixel phone screen, showing the role, the company and the posting loaded from the example — The software engineer letter's details on a phone, before the letter was written.

Opening lines for a software engineer cover letter

Three ways to start it:
“I'd like to apply for the Backend Engineer role; for three years I have run payment services that handle a few thousand requests a second.”
“Your posting asks for Go and Kafka, which is the stack I have used every day since 2021.”
“The latency work in your job description is the problem I spent last year on, and I cut our p99 by a third.”

Swap in your own figure; the free cover letter builder drafts an opening from your evidence as well.

Mistakes that sink a software engineer cover letter

The first is a list of every language you have touched, which tells a hiring engineer nothing about what you can own. The second is repeating the résumé line by line instead of choosing the two or three results that answer the posting. The third is claiming ownership of a system you contributed to; engineers check, and a phone screen will find it.

Keep it under a page, name one incident you handled well and one thing you built that others use. The guide to tailoring a letter shows how to pick the evidence.

What it refused to claim

The posting asks for Rust and for SOC 2 audit work. Nothing in the evidence list supports either, so the letter claims neither and says so in one sentence, and both came back as gaps printed beside the draft. Eight requirements were read in this posting in total, and the count is printed with the gaps so an empty list can never be mistaken for a clean sweep. That is the rule this engine is built on: a requirement the document cannot evidence is shown to the writer, never asserted on their behalf. The gaps list is worth reading as an interview brief, because those two items are exactly what a hiring manager will open with.

There is no language model behind any of this.

What a backend engineer's letter has to prove

Engineering postings list tools, and the letter has to show the tools being used on something that had a consequence. The three selected paragraphs each name a system and a number in the same sentence, which is why they beat the profile line about reliability and cost. If you write bullets like "responsible for the payments platform", there is nothing for a selector to rank and nothing for a reader to check. Putting a figure in the line is the single change that moves an engineering document the furthest.

The second thing this title needs is scope. Fourteen services, one rota, two engineers a morning: those are the numbers that say what size of system she has been trusted with, which is the question behind most senior interviews.

Open it on Details & drafting

Loads Odile's role, company, posting and evidence into the cover letter builder in the Classic design. Nothing is written until you press Create new draft. Free, no account.

Use this example See the letter designs

Questions

Is Odile Brantwick a real person: No. She is invented for this page, and so are Marrowfield Systems, Halvard Pay and Tessellate Werke. The numbers were written to give the engine something real to select from. Nobody applied with this letter and nobody was hired with it.
Did the product really write this letter: Yes. The evidence list on this page was loaded through this page's own door, the company city was typed into the field Details & drafting asks for, and Write the letter was pressed. The reply is printed above unchanged, blocks and all. The engine reports its own provenance: eight requirements read in the posting, eighteen evidence lines offered, eight sentences traced to a numbered line of them, ten written from named connective patterns, two gaps, no model.
What is a gap: A requirement the posting asks for that the evidence cannot support. Here they are Rust and SOC 2. The letter names both in one factual sentence and claims neither. They are shown to you as well, because the honest place to answer them is a conversation.
What does “Use this example” do: It opens the cover letter builder in Details & drafting with the role, the company, the posting and the four evidence groups already loaded, exactly as an imported résumé would load them. No application record and no letter exists until you press Create new draft.
Does the letter change if I choose another voice: The three voices change the subject line, the opening, the fit sentence and the closing. The evidence sentences are Odile's own lines and they do not change, because a voice is a style and evidence is a fact. Changing the voice keeps the draft you already have as a version first.
Which design is this example in: Modern, a quiet asymmetric grid. The door opens the builder on it. Any of the 12 designs carries the same words, and the gallery shows each one as a whole letter rather than a thumbnail.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 22 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.