The Three Lenses of FDE Work
By Sourav Banerjee · Last updated 5 Oct 2026 · Report an issue
4 min read
Technical depth, customer time and team time all compete for the same day, yet each one is what makes the other two fast.
An FDE's work is not three jobs stapled together. Weigh the three lenses here, then follow them through one day in A Senior FDE's Day.
Objectives:
- name the three lenses and what each is for;
- explain why the lenses are weighted rather than sequential;
- state the interdependence line that separates senior from mid-level.
Weigh Three Lenses Every Day
A senior FDE's day rarely splits into a coding day and a customer day. Most days touch all three lenses. The weighting shifts with the engagement; the presence of all three does not.
| Lens | How it shows up daily | What it is for |
|---|---|---|
| Technical build | Architecture decisions, hands-on code and review, debugging production issues, evaluating retrieval and agent strategies | Staying credible enough that the team trusts your calls, and catching problems before the customer does |
| Customer-facing | Discovery, requirement translation, demos and readouts, escalation handling, setting expectations on scope and timeline | Making sure what gets built is what the business needs now, not what the spec said six weeks ago |
| Guiding the team | Unblocking engineers, reviewing designs before they are built, calibrating scope with delivery leads, mentoring on customer communication | Making the team's output better and faster than any one person's throughput |
Read the right-hand column first. Each lens exists for a reason outside itself, which is the clue to how they connect.
Treat the Lenses as One System
The lenses reinforce each other. Technical credibility lets the team trust the FDE's scoping calls without relitigating them. Direct customer relationships allow fast trade-off decisions without a chain of approvals. The team's growth frees the FDE to stay hands-on where it matters instead of being a bottleneck everywhere.
Pull any one out and the other two get slower. The source calls this the line that separates "senior" from "does three jobs".
Keep Technical Depth for Trust and Risk
Technical depth here is not personal output. It is what makes the FDE's judgement borrowable. The source frames it in terms of risk: the highest-blast-radius decisions are the ones to keep for yourself. Routine tickets are delegated on purpose.
Warning: a senior FDE can become the bottleneck. Staying hands-on everywhere blocks the team on you. The point of the team lens is to stay deep only where it matters most.
Worked Example: Removing One Lens
Imagine an FDE who drops customer time to write more code. Their scoping calls lose their anchor in what the business needs now. The team builds to a spec that is six weeks old, and the FDE reviews code for correctness without knowing the intent has moved.
Now imagine one who drops technical depth. The team stops trusting their scoping calls and relitigates every decision. Each case shows the same pattern: removing one lens slows the other two.
Key Takeaways
- Most days touch all three lenses: technical build, customer-facing and guiding the team, in shifting weights.
- The lenses are interdependent: credibility speeds trust, customer access speeds decisions, team growth frees you to go deep.
- Keep technical depth for the highest-risk decisions and delegate the rest, so you are not the bottleneck.
Check Yourself
What is each lens for? Technical build keeps you credible and catches problems early. Customer-facing keeps the build tied to what the business needs now. Guiding the team makes the team's output better than one person's throughput.
Why are the lenses described as weighted rather than sequential? Most days touch all three; only the weighting changes. They are not phases done one after another.
State the senior-versus-mid-level line in one sentence. The three lenses are interdependent: pull any one out and the other two get slower.