In this post10 sections
You interviewed for senior. The offer arrives, the number looks fine at a glance, and then you see the level: one below the one you were told you were interviewing for. Here is the short answer. A down-leveled offer is a decision about evidence, so ask which rounds set the level and on what signal, give the recruiter evidence the loop did not see, and if the level still holds, accept only with a written review date and written criteria. This post is one narrow piece of the FDE salary guide, which covers posted bands, filings and the rest of the offer.
What candidates report
Candidates on Blind report FDE offers a level below the one they aimed for: one candidate reported, in July 2026, a Google FDE offer at L4 after targeting L5, and another candidate, with 3 years of experience, reported in May 2026 a Google Cloud Applied AI FDE offer at L3 that they described as down-leveled. Source 1Google FDE AdvicePublisherBlind (teamblind.com)Source typecandidate report on BlindSource 2Google Cloud FDE or Adobe Applied AI SWEPublisherBlind (teamblind.com)Source typecandidate report on Blind
Other reports show it from other angles:
- A level attached to one round. One candidate with 10 years of experience reported, in May 2026, that the feedback on the coding round of their Google FDE GenAI loop in India was “Hire for L4, not for L5.” Source 3Google Rejected for FDE. Need immediate referralPublisherBlind (teamblind.com)Source typecandidate report on Blind That loop ended in rejection, so read it only for what it shows: one round can come back with a level on it. Rejected as not technical enough covers the rest.
- A level read from the number. One candidate negotiating a Google UK FDE offer reported, in August 2026, that they felt the base aligned with L4, although they had expected L5. Source 4Advice on Google UK FDE Offer NegotiationPublisherBlind (teamblind.com)Source typecandidate report on Blind
Each of these is one Blind poster’s account of a Google FDE loop, from May to August 2026, and none says how often down-leveling happens. Source 1Google FDE AdvicePublisherBlind (teamblind.com)Source typecandidate report on BlindSource 2Google Cloud FDE or Adobe Applied AI SWEPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 3Google Rejected for FDE. Need immediate referralPublisherBlind (teamblind.com)Source typecandidate report on BlindSource 4Advice on Google UK FDE Offer NegotiationPublisherBlind (teamblind.com)Source typecandidate report on Blind The posters use Google’s internal level numbers (L3, L4, L5); the public postings number the title instead, as in “Forward Deployed Engineer III” and “Forward Deployed Engineer IV”. Source 5Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 6Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting Where an employer titles roles Senior or Staff, a down-level shows up as a different word in the title line. Who hires FDEs, and under which titles shows how to read those titles, and the evidence map shows how much weight one report can carry.
What the level changes
A level is not a label on the offer. It picks the band you negotiate inside, and the band caps what any negotiation can reach.
Google’s two posted FDE levels make this concrete. As of September 2026, the Forward Deployed Engineer III and IV postings each list their own US pay range and bonus target, and the IV posting asks for 8 years of software development experience where the III asks for 5, with the bonus target and equity listed on top of each range. Source 5Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 6Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting
The same split shows up outside Google. As of September 2026, Scale AI’s Senior Frontier Agents Engineer (Forward Deployed Engineering) posting asks for 5+ years and its Staff version for 8+ years, each with its own base range, and the top of the Senior range sits below the top of the Staff one. Source 7Senior Frontier Agents Engineer (Forward Deployed Engineering)PublisherScale AI (Greenhouse)Source typecompany job postingSource 8Staff Frontier Agents Engineer (Forward Deployed Engineering)PublisherScale AI (Greenhouse)Source typecompany job posting
Where the bands overlap
Here is the part that changes how you read a down-level. As of September 2026, the two Google bands overlap: the top of the III range sits above the bottom of the IV range, and the IV posting’s bonus target is 20% against the III’s 15%. Source 5Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 6Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting Scale’s Senior and Staff base ranges overlap the same way. Source 7Senior Frontier Agents Engineer (Forward Deployed Engineering)PublisherScale AI (Greenhouse)Source typecompany job postingSource 8Staff Frontier Agents Engineer (Forward Deployed Engineering)PublisherScale AI (Greenhouse)Source typecompany job posting
So a lower-level offer at the top of its band can match a higher-level offer’s base today. It still loses on three things:
- The bonus target, the lower of the two, every year you stay.
- The ceiling. Every future raise inside the lower band stops at its top, which sits below the top of the higher band.
- The promotion clock. To get back to the level you interviewed for, you need a promotion, and that clock starts only once you’re in.
The salary guide has the figures.
At some employers the level is the whole negotiation. One Blind poster wrote, in March 2024, that an Anthropic recruiter was strict that Anthropic doesn’t negotiate offers and said “each level is pretty set.” Source 9Does Anthropic negotiate?PublisherBlindSource typecandidate report on BlindSource 10Does Anthropic really not negotiate?PublisherBlindSource typecandidate report on BlindSource 11OpenAI/Anthropic/Stripe: Is "no negotiating" a lie?PublisherBlindSource typecandidate report on Blind Where pay inside a level is fixed, the level is the only lever left, which makes the evidence step below worth the effort.
Here is what we’d check before reacting to any down-level, and the question that gets each answer:
| What the level sets | What to ask |
|---|---|
| The band | “Which band is this offer in, and where in it?” |
| The bonus target | “What is the target at this level?” |
| The equity grant | “Is the grant sized by level? What would it be one up?” |
| Your scope | “What would I own at this level that I wouldn’t one up?” |
| The next promotion | “When is the first review, and who decides?” |
| The title | “What exact title goes on the offer letter?” |
In our view, the last two rows matter most: a down-level costs you a promotion you must earn to get back where you started, and a written review date is what shrinks that cost.
How a loop lands a level lower
Some employers say in their postings that the level is decided during the interviews. As of September 2026, Glean’s Founding Forward Deployed Engineer posting says its range covers varying levels of the role and that you will be assessed for your level during the interview process. Source 12Founding Forward Deployed EngineerPublisherGlean (Greenhouse job board)Source typecompany job posting Scale AI’s postings say a posted range may span several career levels, and that pay is set during the interview process based on factors that include interview performance. Source 13Forward Deployed Engineer, GenAIPublisherScale AI (Greenhouse)Source typecompany job posting MongoDB’s Lead Forward Deployed Engineer posting says the Lead FDE takes a lead role in hiring and leveling decisions. Source 14Lead Forward Deployed EngineerPublisherMongoDB CareersSource typecompany job posting
So treat every round as a level round, whether or not anyone says so. In our reading, a loop lands a level lower in one of four ways:
- One round came in low. One candidate reported that a Google FDE coding round came back as “Hire for L4, not for L5.” Source 3Google Rejected for FDE. Need immediate referralPublisherBlind (teamblind.com)Source typecandidate report on Blind If the rest of the loop was mixed, that one signal can anchor the result.
- The loop was short. One candidate described their Google FDE process as two interviews: a coding question and a system-design-style conversation about building an agentic system. Source 1Google FDE AdvicePublisherBlind (teamblind.com)Source typecandidate report on Blind Fewer rounds means fewer chances to show scope, so each one carries more of the level call.
- Your stories were told a level down. You described the tasks you did, not the decisions you owned or the people and systems those decisions touched.
- Your years fell short of the posting’s ask. If the higher posting asks for 8 years and your resume shows fewer, the committee needs other evidence to place you there. Source 5Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting
Knowing which one it was tells you what to bring: new evidence of depth for the first, unheard scope for the second and third, and scope at the level’s size for the fourth.
The call: ask for the evidence behind the level
Don’t accept, decline or counter on the first call. The aim is to learn what set the level and whether anything can still move it. The opening moves (get the offer in writing, ask what set the level, ask what can still move it, settle the level before the money) are set out in the question the offer came in one level below (Pro), with a model answer. This section covers what comes after them: the follow-up email and the pushback.
The follow-up email
Send it the same day:
Thanks for walking me through the offer. To confirm what we discussed: you’ll check which rounds set the level at L4, and whether a hiring manager conversation or an extra interview at L5 is possible. I’ll send two examples of my scope by Thursday that I don’t think the loop covered.
The email does two jobs. It gives the recruiter something to forward, and it puts a date on your side of the exchange, which makes it easier to ask for one on theirs.
When the recruiter pushes back
Expect at least one of these. Each reply below is our method: it accepts the recruiter’s limit and asks for the next useful thing.
“We can’t share interview feedback.” Don’t push for the feedback. Ask for the standard instead: “Understood. Then which expectations of the higher level does the committee look for, so I can show where I’ve done them?” That gives you the words to write your evidence in.
“Levels are final once the committee decides.” Take it as an answer on the level, not on the rest: “Then can we agree the first review date and the higher level’s criteria in writing now?” You’ve moved from the decision you can’t change to the one you can.
“We can bump the base instead.” Remember the overlap. More base can close today’s gap, but it doesn’t raise the ceiling or the bonus target, and it doesn’t start your promotion clock. A reply that keeps both on the table: “That helps, thank you. Can we also put a review date and the criteria for the higher level in writing, so the base isn’t the only thing that moves?” If they then say the grant is fixed, the equity number is final (Pro) has what to ask next.
Will asking put the offer at risk?
We know of no source that says how employers react, so here is our reasoning rather than a fact. Each question above asks for information or a written commitment. None of them rejects the offer, sets an ultimatum or disputes the panel’s judgment. “I thought my design round went well” asks the recruiter to overrule interviewers, which they can’t do; new evidence gives them something they can take back. Keep the tone of someone who wants the job, and say so: “I want to make this work; I’m asking so I can accept with a clear picture.”
Evidence the loop didn’t see
This is the part that can change a level. Send two examples, no more, each short enough to forward without editing. Write each example as four short lines:
- The problem, and who owned it. Name the customer or team and what was at stake.
- The scope. How many systems, teams or customers your decisions reached.
- The decision. What you chose, and the alternative you turned down.
- The result. A number you measured.
Use the posting’s own words for the higher level where you can. If the senior posting asks for leading technical work with customers, your example should read like someone doing exactly that, in those words.
A worked example, fictional. Here is a version that gives the committee nothing new:
I led the migration of our data pipeline to a new warehouse and worked closely with stakeholders.
And the version that gives a committee something to place:
A logistics customer’s nightly reports were failing about once a week, and I owned the fix end to end. The change touched three services and two teams, and I chose an incremental load over a full rebuild because the customer couldn’t take downtime at month end. Failures dropped to zero over the next quarter, and I wrote the runbook the customer’s own team now uses.
The second one shows ownership, scope across teams, a named tradeoff and a measured result. None of that is a claim about seniority. It is evidence, and the recruiter can forward it as it stands.
Two other kinds of evidence count if you have them. An offer or current title at the higher level, stated with its scope. And a reference who saw your work at that scope and can say so in a short call.
When to accept, and what to get in writing
Sometimes the level holds after you’ve made your case. A firm answer is still an answer, and you can decide on it.
A down-level can still be the right offer. Here is how we’d weigh it:
| Accept with a review date if | Push harder or walk if |
|---|---|
| The band still beats your other options | Your current role is already at the higher level |
| The team and scope are what you want | The scope is visibly smaller than you were told |
| You get a written date and criteria | They won’t commit to any review in writing |
| The equity makes up part of the gap | The only offset is a one-off payment |
If you accept, get these in the offer letter or a follow-up email from the recruiter or hiring manager:
Before you sign a down-leveled offer
- The exact title and level, as they’ll appear in the offer letter
- The date of your first promotion review, as a month
- The criteria for the higher level, in the company’s own words
- Who makes the decision, and whether your manager can put you forward
- Whether the band, bonus target and equity move with the promotion
- Any offset agreed now: the top of the band, a sign-on, or a larger grant
A review date without criteria is a meeting. A review date with criteria is a plan you can work toward from day one, and it gives your future manager something concrete to argue for.
Heading it off in your next loop
The cheapest time to fix a level is before the first interview.
- Ask the level on the recruiter screen. “Which level is this loop for, and what would a strong hire at that level have shown?” If the answer is a range, ask what separates the two ends.
- Name your own level with evidence. What level do you think you are, and why? is a free question with a model answer that shows how to argue for a level without sounding like you’re negotiating.
- Tell every story at the target scope. Decisions, not tasks. Teams and systems, not tickets. Tradeoffs you turned down, not only the one you chose.
- Hold both bars. FDE loops test technical depth and how you work with a customer, and a soft round on either side can come back as a level call. The double bar covers what each side looks for.
- Rehearse the customer half. In our method, level shows in the scoping questions you ask before you build. The free practice customer case at /try (sign-in required) lets you practice exactly that against an AI customer, and the score quotes you.
If your Google loop passed and you’re still waiting on a team, treat each team call as more evidence of your scope; the post on Google FDE team matching covers what to ask while you wait. For everything else on the table once the level is set, from sign-on to deadlines, see how to negotiate an FDE offer.
Before your recruiter call, rehearse it. The recruiter round’s questions each come with a model answer. What level do you think you are? is free; the down-level call and the equity follow-up are in Pro, which you can open with a 7-day free trial (see plans) along with all 180 questions in the bank.
Questions people ask
Why was I down-leveled on my FDE offer?
The employer sets the level from what the loop showed, and some postings say so: as of September 2026, Glean’s Founding FDE posting says its range covers several levels and that you will be assessed for your level during the interview process. Ask the recruiter which rounds set your level and on what signal.Source 12Founding Forward Deployed EngineerPublisherGlean (Greenhouse job board)Source typecompany job posting
Can you get a down-leveled FDE offer moved back up?
Ask. Ask what evidence would change the level, such as another interview at the higher level or a call with the hiring manager, and offer examples of your scope that the loop did not see. If the level holds, ask for a promotion review date and its criteria in writing.
Should I accept an FDE offer one level below what I interviewed for?
It can be worth it if the band, equity and scope still beat your alternatives and you get a written review date. Compare offers by level, not title: as of September 2026, Google posts Forward Deployed Engineer III and IV as separate postings, each with its own pay band.Source 5Forward Deployed Engineer IV, GenAI, Google Cloud — Google CareersPublisherGoogleSource typecompany job postingSource 6Forward Deployed Engineer III, Generative AI, Google Cloud — Google CareersPublisherGoogleSource typecompany job posting
Keep reading
Lessons
More from the blog
Pay and offers
How to negotiate a forward deployed engineer offer: what moves, what doesn’t, and the words to use
Your FDE offer came with a deadline. What candidates report moved and what didn’t, with scripts for the first call, competing offers, equity and deadlines.
Pay and offers
‘What are your salary expectations?’ An FDE answer that doesn’t cost you money
The recruiter asks your FDE salary expectations before you know the level. Scripts to hold off, anchor to the posted band and answer when pushed.
Pay and offers
Comparing FDE offers: the math for base, equity, bonus and travel
One FDE offer has more base, the other more equity and more travel. A worked comparison: annualized equity, bonus at target, OTE risk and travel as a cost.