Skip to content

Lesson 5 of 5

Your Action Plan

Assess your current skills against the role and write a personal plan with next steps to become a Forward Deployed Engineer.

4 minForward Deployed Engineering

After this lesson, you will be able to assess your current skills against the Forward Deployed Engineer role and write a personal action plan with concrete next steps.

Review the Role

You have learned what a Forward Deployed Engineer does and how the role differs from other engineering roles. An FDE works closely with customers to scope problems, integrate solutions into the customer's systems, and ship reliable software in environments the customer controls. The role needs both technical and communication skills.

Before you plan, list the main skills from the earlier lessons. Technical skills include writing Python scripts that run in someone else's environment, handling paths and permissions, and testing code. Communication skills include scoping a problem with a customer and explaining technical choices clearly.

Assess Your Current Skills

Make a simple table for yourself with three columns: skill, current level, and evidence. Current level can be beginner, intermediate, or advanced. Evidence is a short note about what you have done that shows your level.

For example, if you completed the exercise from the lesson on shipping in someone else's systems, you have evidence for writing a Python script that reads system information and writes a log file. If you have explained a technical problem to a non-technical friend, that is evidence for communication.

Be honest in your assessment. The goal is to find gaps, not to feel bad about them. Many FDEs start with strong skills in one area and build others on the job.

Find Your Gaps

Compare your table with the skills an FDE needs. Look for rows where your current level is beginner or where you have no evidence. These are your gaps.

Common gaps for people starting out include working with a customer's existing code, writing tests for code that runs on different systems, and explaining a technical decision in plain language.

Choose two or three gaps to work on first. Trying to fix everything at once is hard. Pick the gaps that matter most for the kind of company you want to join.

Write Your Action Plan

For each gap, write one action you can take in the next two weeks. An action should be small and specific. For example, if your gap is writing tests, an action is to add a test to the disk_check.py script from the earlier lesson that checks the log line format.

If your gap is communication, an action is to write a one-paragraph explanation of what disk_check.py does, as if for a customer who is not a programmer. Read it aloud and shorten any sentence longer than twenty words.

Write your plan in a file called action_plan.md. Use a simple format:

# My Action Plan

## Gap: testing code that runs on different systems
- Action: add a test to disk_check.py that checks the log line format.
- Deadline: two weeks from today.

## Gap: explaining technical choices
- Action: write a one-paragraph explanation of disk_check.py for a non-technical customer.
- Deadline: one week from today.

Keep the plan where you will see it. A file in your home directory or a note on your phone works.

Make the Plan Real

An action plan only helps if you do the actions. Set a reminder to review the plan in two weeks. When you finish an action, update the file with a short note about what you did and what you learned.

If an action turns out to be too big, split it into smaller steps. For example, adding a test can be split into: read the current disk_check.py, write down what the log line should look like, write the test, run it.

You can repeat this process every few months. Your skills will change, and so will the gaps.

Use Your Existing Code

The scripts from the earlier lessons are good material for your plan. You can improve disk_check.py or the cpu_check.py script you may have written. Working on code you already understand saves time and shows real progress.

If you want to practise working in someone else's system, ask a friend if you can run a small script on their computer. Explain what the script does and ask permission before you run it. This is a safe way to practise the FDE skill of shipping in a constrained environment.

Key takeaways

  • Assess your skills honestly using a simple table with skill, level, and evidence.
  • Choose two or three gaps to work on first.
  • Write small, specific actions with deadlines in a file you will see.
  • Use the code from earlier lessons as material for practice.
  • Review your plan regularly and update it as you learn.

Try it

Create your own action plan file called action_plan.md. First, list at least five skills an FDE needs, using the earlier lessons as a guide. For each skill, write your current level (beginner, intermediate, or advanced) and one piece of evidence. Then choose two gaps and write one specific action for each, with a deadline within the next two weeks. A good result is a plan that is honest, has actions small enough to finish in two weeks, and is written in a file you can open and edit.

Official documentation

Ready to use this in a job?

Rolebound applies to matching roles for you.

Start now

Written with AI and checked automatically. Tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.

    Cookies on Rolebound

    We use necessary cookies to sign you in and keep the site working — those cannot be turned off. We would also like to set analytics and advertising cookies so we can see which pages help people get interviews and which adverts brought them here. Nothing optional is set unless you say yes, and you can change your mind at any time from “Cookie settings” in the footer. Read our Privacy Policy.

    Your Action Plan | What a Forward Deployed Engineer Does and How to Become One | Rolebound