Recommendation letter guide · Sample letter and email · Updated Nov 2026

Letter of recommendation for a Forward Deployed Engineer

The short answer

The best FDE recommendation comes from someone who saw you deliver for a customer: your engagement lead or manager, or the customer-side sponsor who signed off your work. It should prove three things with specific stories: you ship working code in someone else’s environment, customers trust you in hard conversations, and you own the outcome, not just the tickets.

See the sample letter Full FDE interview guide

Who should write it

Pick the person who saw your work most closely, not the one with the biggest title.

Your manager or engagement lead

They saw the whole deployment: scope, setbacks, and how you handled the customer when things went wrong.

The customer-side sponsor or their tech lead

Unique to FDE work and very strong: the person you built for confirms the outcome. Ask your manager first and check your contract allows it.

A product or core engineering lead

Shows your field learnings changed the product, which is what separates a strong FDE from a consultant.

What a FDE letter must prove

Each quality needs a specific story. Here is the kind of line that proves it.

Ships in messy environments

“Ishaan got our platform running on the insurer’s own AWS account, under their security rules, in five weeks.”

Earns customer trust

“When the pilot slipped, he told their COO first, with a new plan. She added a second workflow the next quarter.”

Owns the outcome

“He measured success by handling time on the claims floor, not by features shipped.”

Makes the product better

“A connector he built for one customer is now part of our product and saves every new account a week of setup.”

Structure: one page, five short parts

1OpeningWho you are, your role, how long you worked with the candidate, on which engagements, and the role they are applying for.
2Headline claimOne sentence that sums up the candidate, e.g. “the engineer I send to our hardest customers”. Only if true.
3Two deployment storiesEach story: the customer situation, what the candidate built or decided, and the outcome the customer measured. Anonymise customers if needed.
4How they handle peopleOne short paragraph on executives, end users and difficult customer engineers, with an example.
5CloseA clear recommendation and an offer to talk, with your contact details.

Sample letter of recommendation

From an engagement lead, for a job application (fictional people and company)

I am Meera Iyer, Head of Deployments at Lumen Data Systems (fictional). Ishaan Kapoor reported to me for two years as a forward deployed engineer, and I worked alongside him on four customer engagements. I am glad to recommend him for a Forward Deployed Engineer role.

Ishaan is the engineer I send to our hardest customers. At a mid-size insurer, he got our platform running on their own AWS account, under their security rules, in five weeks. Before shipping the claims assistant, he sat with their senior handlers and built a 250-example evaluation set from real claims. Accuracy rose from 74% to 92% before go-live, and 140 handlers now use it every day.

He also tells customers hard news early. When a data-access delay put the pilot two weeks behind, he called their COO before she heard it from anyone else, with a smaller first release and a new date. We hit that date, and the customer added a second workflow the next quarter.

Our product team values him too. He noticed the same document-ingestion problem at four customers, wrote it up with the evidence, and helped build the connector that now cuts setup for new accounts from ten days to two.

I recommend Ishaan without reservation and am happy to talk to you about his work.

Meera Iyer, Head of Deployments, Lumen Data Systems (fictional) · meera@example.com

All people, companies and numbers in this sample are fictional. Your recommender should write in their own words.

How to ask, and what to send

Make it easy to say yes: a short email plus a one-page brief.

Email to your recommender

Subject: Would you be a reference for a Forward Deployed Engineer role?

Hi [Name], I am applying for Forward Deployed Engineer roles, starting with [Company]. You saw my work on the [customer or project] deployment more closely than anyone, so I would be grateful if you could write a short recommendation or take a reference call. To make it easy, I have attached a one-page brief: the role, three deployment stories you might mention, and the numbers. I have kept customer names out of it. Please change anything that does not match your memory. The deadline is [date]. If now is a bad time, no problem at all. Thank you, [Your name]

The brief to attach

The job description and why you want customer-facing engineering work (two lines).
Three deployment stories they saw, each with the customer situation, what you built or decided, and the outcome.
The exact numbers (time to go-live, adoption, accuracy, hours saved), so they do not have to look them up.
Which customer details are safe to mention and which must stay anonymous.
The deadline, the format (letter, form or call) and where to send it.

Job, MBA, promotion or referral

Same stories, different emphasis.

Job application or reference call

Lead with one deployment and its outcome. Many companies prefer a 15-minute call to a letter, so ask which they want and prepare your recommender with the two stories in the brief.

MBA or master’s application

Add growth and leadership: how the candidate grew from writing code to running customer relationships, and how they took feedback. Follow the school’s questions exactly.

Internal move or promotion (e.g. to senior FDE or deployment lead)

Show they already work at the next level: leading an engagement alone, mentoring newer FDEs, or writing playbooks others use.

Referral note to a recruiter

Three sentences: how you know them, the best deployment they delivered, and why they fit this FDE role.

Mistakes that weaken a recommendation

Praising coding skill only. FDE hiring managers also want proof of judgement with customers.
Naming a customer or sharing their numbers without permission.
Asking a customer for a letter without telling your manager. Always ask your manager first.
Generic praise (“great communicator”) with no story about a real customer conversation.
Writing the letter yourself and asking them to sign it. Send a brief instead and let them use their own words.

Fix your resume next

Bullet bank, keywords from real job posts and a sample one-page FDE resume.

FDE resume (CV) guide

Keep going

FDE resume (CV) guide FDE interview questions with answers Practise out loud in a free AI mock interview

Frequently asked questions

Do FDE employers ask for letters of recommendation?

Most tech companies ask for reference calls rather than letters, usually late in the process. Letters matter more for MBA and master’s applications, internal moves and some Indian and European employers. The same brief works for both.

Can a customer write my recommendation?

Yes, and for FDE roles it is one of the strongest signals. Ask your manager first, check your contract, and let the customer decide what they are comfortable sharing.

Who should write it if I am switching into FDE from software engineering?

Someone who saw you work with users or other teams: a manager who watched you handle a customer escalation, or a support or sales lead you built tools for.

How long should a letter of recommendation be?

One page, four to five short paragraphs: introduction, two deployment stories with outcomes, how you work with people, and a clear close.