A 90-Day FDE Roadmap for Software Engineers
You are a software engineer. You want to become a Forward Deployed Engineer. You have 90 days.
This is not a theoretical guide. It is a week-by-week plan with specific actions, deliverables, and checkpoints. By the end of 90 days, you will have the skills, evidence, and stories needed to interview credibly for FDE roles.
Prerequisites
Before you start this roadmap, confirm:
- You have 2+ years of production software engineering experience.
- You can write, debug, and ship code in at least one language without tutorials.
- You have basic familiarity with Git, cloud platforms, and CI/CD.
- You can commit 10–15 hours per week to this plan alongside your current job.
If any of those are false, address them first. This roadmap assumes you have a solid engineering foundation and need to build FDE-specific skills on top of it.
Month 1: Customer proximity (Weeks 1–4)
The first month is about one thing: getting close to customers. Every FDE skill starts with understanding the person you are building for.
Week 1: Start your discovery log
Goal: Begin recording customer-facing observations.
Actions:
- Create a simple document (Notion, Google Docs, or plain Markdown) titled "Customer Discovery Log."
- Attend one customer-facing meeting at your company. If you do not have access to customer calls, ask your PM or sales team. If that is not possible, find a public forum where your product's users discuss problems (Reddit, Discord, GitHub Issues).
- Write down three observations: What problem did the customer describe? What did they actually need? What was the gap between the two?
Checkpoint: You have a discovery log with your first entry.
Week 2: Practice the discovery conversation
Goal: Learn to ask questions that reveal actual needs.
Actions:
- Read "The Mom Test" by Rob Fitzpatrick (or a summary). This book teaches you how to ask questions that produce honest, useful answers instead of polite confirmations.
- Conduct two informal discovery conversations. These can be with friends, colleagues, or anyone who uses a product in their work. Ask: "Walk me through how you do [X]. What is the most frustrating part? What have you tried to fix it?"
- Add both conversations to your discovery log. For each, write: What I heard, What I think they actually need, What I would build.
Checkpoint: You have three entries in your discovery log with structured observations.
Week 3: Observe a customer workflow
Goal: See how a real user works, not just what they say.
Actions:
- Ask to shadow a customer-facing team member (sales engineer, solutions architect, customer success manager) for one session.
- If that is not possible, watch a screen recording of a user using your product (many companies have these from usability testing).
- Document the workflow step by step. Note where the user hesitates, works around the product, or expresses frustration.
Checkpoint: You have a workflow map in your discovery log that shows the user's actual process, not the ideal process.
Week 4: Write your first customer brief
Goal: Translate a customer observation into a technical recommendation.
Actions:
- Pick the most interesting problem from your discovery log.
- Write a one-page brief with three sections: (1) What the customer needs, (2) Why current solutions fall short, (3) What I would build and why.
- Share it with a colleague and ask for feedback. Is it clear? Is it actionable? Would they trust this person to solve the problem?
Checkpoint: You have a written customer brief that you can add to your portfolio.
Month 2: Technical breadth and deployment (Weeks 5–8)
The second month is about building the technical skills that FDEs use daily: deploying in unfamiliar environments, configuring systems, and debugging in production.
Week 5: Deploy something to a new platform
Goal: Build confidence deploying outside your comfort zone.
Actions:
- Pick a platform you have not used before: Cloudflare Workers, Fly.io, Railway, or AWS Lambda.
- Build and deploy a simple service: a REST API, a webhook handler, or a data transformer.
- Document the deployment process step by step. What was confusing? What took longer than expected?
Checkpoint: You have a deployed service on a new platform and a written record of the experience.
Week 6: Learn infrastructure-as-code
Goal: Understand how to define infrastructure declaratively.
Actions:
- Pick one IaC tool: Terraform, Pulumi, or SST.
- Define the infrastructure for your deployed service using that tool. Create the resources, configure networking, and set up monitoring.
- Destroy and recreate the infrastructure from scratch using only your IaC definitions.
Checkpoint: You can describe your infrastructure in code and recreate it reliably.
Week 7: Debug a production issue
Goal: Practice debugging in an unfamiliar system.
Actions:
- Find a real production issue. This could be: an open-source project with a reported bug, a colleague's project with an issue, or a deliberate bug you introduce into your own deployed service.
- Debug it end-to-end. Read logs, trace requests, identify the root cause, and fix it.
- Write a brief postmortem: What happened, why, how you found it, what you would do to prevent it.
Checkpoint: You have a postmortem document that demonstrates your debugging process.
Week 8: Build a customer-like solution
Goal: Combine discovery and deployment into a single deliverable.
Actions:
- Pick a problem from your discovery log (Month 1).
- Build a solution that solves it. This does not need to be a full product — it can be a script, a dashboard, an integration, or a configured tool.
- Deploy it as if a customer would use it. Set up monitoring, write a README, and create a short demo.
Checkpoint: You have a deployed solution that demonstrates both customer understanding and technical execution.
Month 3: Communication and portfolio (Weeks 9–12)
The third month is about packaging your work into evidence that FDE hiring managers can evaluate.
Week 9: Write a technical brief for a non-technical audience
Goal: Practice translating technical work into business language.
Actions:
- Take your deployed solution from Week 8.
- Write a one-page brief aimed at a VP of Operations or a business stakeholder. Explain: What it does, Why it matters, What outcome it creates.
- Avoid jargon. If you cannot explain it without technical terms, you do not understand the business value well enough.
Checkpoint: You have a non-technical brief that makes a business case for your technical work.
Week 10: Present to a mixed audience
Goal: Practice presenting technical work to people with different backgrounds.
Actions:
- Find an opportunity to present: a team meeting, a lunch-and-learn, a local meetup, or even a recorded video.
- Present your deployed solution and the customer problem it solves.
- Get feedback from at least one non-technical person. Was it clear? Did they understand the value?
Checkpoint: You have presented your work and received feedback from a mixed audience.
Week 11: Build your FDE portfolio
Goal: Package your 90-day work into a compelling portfolio.
Actions:
- Create a portfolio document (or a simple website) that includes:
- Your customer brief (Week 4)
- Your deployed solution (Week 8)
- Your non-technical brief (Week 9)
- Your debugging postmortem (Week 7)
- A summary of your customer discovery process (Month 1)
- For each piece, add context: What was the problem? What did you build? What was the outcome?
Checkpoint: You have a portfolio that demonstrates customer discovery, technical execution, and communication skills.
Week 12: Prepare your FDE stories
Goal: Develop the specific stories you will tell in FDE interviews.
Actions:
- Write out three stories in the STAR format (Situation, Task, Action, Result):
- A time you discovered a customer's actual need (not their stated need).
- A time you deployed or debugged something in a challenging environment.
- A time you translated technical work for a non-technical audience.
- Practice each story until you can tell it in 2–3 minutes.
- Get feedback from a friend or mentor.
Checkpoint: You have three polished stories and a complete portfolio.
What you should have after 90 days
By the end of this roadmap, you will have:
- A customer discovery log with 4+ entries showing structured observation
- A deployed solution on a new platform with IaC
- A debugging postmortem demonstrating your diagnostic process
- A non-technical brief translating technical work into business value
- A presentation delivered to a mixed audience
- A portfolio packaging all of the above
- Three polished interview stories
This is not a guarantee of a job offer. It is a guarantee that you will walk into FDE interviews with credible evidence of the skills the role requires.
What happens after 90 days?
This roadmap gets you ready to interview. The next steps are:
- Update your resume to lead with customer outcomes, not technical output.
- Target FDE roles at companies whose products you understand.
- Apply broadly — FDE roles exist at Palantir, Scale AI, Anduril, Databricks, Snowflake, and many enterprise SaaS companies.
- Use your portfolio and stories in every interview.
Your next step
Want to know where you stand before starting this roadmap? Take our free self-assessment. It scores your current readiness across technical depth, customer proximity, communication, and outcome ownership — then shows you exactly where to focus your 90 days.
Frequently asked questions
Can I do this roadmap faster than 90 days?
If you can commit 20+ hours per week, you can compress the timeline to 6–8 weeks. The key constraint is not time — it is the number of real customer interactions you can arrange. Discovery conversations and shadowing opportunities are scheduled around other people's availability.
Do I need to leave my current job to do this?
No. This entire roadmap is designed to run alongside a full-time engineering job. All the activities — discovery logs, deployments, briefs, presentations — can be done with resources available at most companies. The only external dependency is access to customer-facing conversations, which most companies will accommodate if you ask.
What if I cannot access real customers?
Substitute with: public forums where your product's users discuss problems (Reddit, Discord, GitHub Issues), user research recordings (ask your design or product team), or friends and family who use technology in their jobs. The goal is to practice the skill of observation and translation, not to have a formal customer relationship.
Is 90 days enough to be competitive for FDE roles?
It depends on your starting point. If you have 3+ years of production engineering experience and strong communication skills, 90 days of focused FDE skill-building can make you competitive. If you are earlier in your career or have significant gaps in customer interaction or deployment experience, you may need more time. The assessment will help you calibrate.