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 posted to the same endpoint the Write the letter button posts to, in the same voice the door opens with, and the reply is printed above unchanged. The engine reports its own provenance: three paragraphs selected, two gaps found, no model used.

A requirement the posting asks for that the evidence cannot support. Here they are Rust and SOC 2. The letter says nothing about either. They are shown to you instead, because the honest place to answer them is a conversation, not a claim in writing.

What does “Use this example” do

It opens the cover letter builder on 02 · Details 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 Write the letter.

Does the letter change if I choose another voice

The three voices change the opening sentence, the fit sentence and the closing. The evidence paragraphs are your own sentences and they do not change, because a voice is a style and your evidence is a fact. Changing the voice keeps the previous draft 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 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. The person and the posting are invented. The letter, the tracing and the gaps came out of the product.

ConxfolioPublished 2026-09-13

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

The Conxfolio cover letter builder on step 02 Details, opened by this page's own door, with the role Backend Engineer, the company Marrowfield Systems, the posting and the four evidence groups loaded — The Details step exactly as the door left it: Backend Engineer at Marrowfield Systems, the posting, and 18 evidence lines across profile, experience, achievements and skills, each one removable. No letter and no application record exists at this point.

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 handed to the cover letter builder, and what came back is printed here without a word changed.

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

This is the direct voice, which is the one the door opens with. Eight paragraphs. Three of them are Odile's own sentences, lifted whole out of the list above.

Dear Marrowfield Systems Hiring Team,

I'm applying for the Backend Engineer role at Marrowfield Systems.

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.

Automated the Terraform review that used to take two engineers a morning.

The posting asks for PostgreSQL, Kubernetes and Terraform — all of which I've worked with directly.

I'd welcome the chance to talk through any of this.

Odile Brantwick

The salutation, the opening, the sixth paragraph and the closing are connectors the engine owns. The three in the middle are hers. The signature is her name, taken from the top of the evidence and used only to sign, never as a claim.

Where each paragraph came from

The engine reported three selected lines and the position each came from in the evidence list: line 6, line 7 and line 9 of the eighteen it was given. Those are the PostgreSQL line, the Kubernetes line and the Terraform line. It also reported what each one answers in the posting, which is how the ranking is explainable rather than magical. A line scores for matching a requirement the posting names, for carrying a figure, and for the number of recognisable skills in it.

Two things were left out on purpose. The reconciliation line is the strongest sentence Odile has, and it did not make the letter, because the posting never asks about settlement speed. The on-call line went the same way. A cover letter is not a second résumé, and the engine picks for this posting rather than for her career. The article on evidence tracing shows the same provenance in the product's own interface.

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 says nothing about either, and both came back as gaps printed beside the draft. 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. The selection is deterministic code over your own lines, the fit sentence is a template filled with the skills that actually matched, and the response says so in its own payload.

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.

The same evidence in the other two voices

Three voices ship with the builder, and changing one rewrites the connectors rather than the evidence. The ranking never sees the voice, so the same lines are selected in the same order in all three. Run on this page's own evidence, the warm voice opens "I'd like to be considered for the Backend Engineer role at Marrowfield Systems." and closes "I'd be glad to walk through any of this with you." The formal voice opens "I am writing to apply for the position of Backend Engineer at Marrowfield Systems." and closes "I would welcome the opportunity to discuss my application further." The middle connector changes with it: warm writes "You mention PostgreSQL, Kubernetes and Terraform; those have been the centre of my recent work." and formal writes "The role calls for PostgreSQL, Kubernetes and Terraform, each of which I have applied in practice." In the product, switching voice keeps the draft you already have as a version before it writes the new one, so nothing is lost by trying the other two.

The design, and what the door does

The same Details step on a 390 pixel phone screen, showing the role, the company and the posting loaded from the example — The same door on a phone. The role, the company and the posting arrive filled in, and the evidence groups sit below them.

The example opens in Modern, a quiet asymmetric grid. The design changes the paper and nothing else, so the words above are the words in all 12 of them. The design gallery shows each as a whole letter.

Pressing the door below opens 02 · Details with the role, the company, the posting and the four evidence groups loaded, each line removable. Nothing is composed until you press Write the letter, so you can drop a line you do not want claimed before any draft exists. Replace her evidence with yours, paste the real posting, and the same engine will do to your lines what it did to hers. The matching résumé example carries the document those lines would come from.

Open it on the Details step

Loads Odile's role, company, posting and evidence into the cover letter builder in the Modern design. Nothing is written until you press Write the letter. 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 posted to the same endpoint the Write the letter button posts to, in the same voice the door opens with, and the reply is printed above unchanged. The engine reports its own provenance: three paragraphs selected, two gaps found, no model used.
What is a gap: A requirement the posting asks for that the evidence cannot support. Here they are Rust and SOC 2. The letter says nothing about either. They are shown to you instead, because the honest place to answer them is a conversation, not a claim in writing.
What does “Use this example” do: It opens the cover letter builder on 02 · Details 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 Write the letter.
Does the letter change if I choose another voice: The three voices change the opening sentence, the fit sentence and the closing. The evidence paragraphs are your own sentences and they do not change, because a voice is a style and your evidence is a fact. Changing the voice keeps the previous draft 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 20 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.