Do ordinary people have a chance to enter the FDE? What abilities do I need to supplement? How to prepare for the interview? And-whether this position is worth investing in.
Give the conclusion first:
The entry threshold for FDE is lower than most people think; but it is by no means a simple job with more money and less work.
Many people can't enter this field. It's not that they are not capable enough, but that they set themselves on the standards of senior engineers from the beginning.
In fact, FDE is more like a comprehensive position:
You need to understand some technology, but you don't need to be an algorithm expert;
You need to understand the business, but not necessarily from a traditional consulting background;
You need to be able to communicate with customers, but not just sales.
What really opens the gap is whether you can turn a vague problem into a workable, measurable, and replicable solution.
This is also why some people are very skilled but are not suitable for FDE; while some people with ordinary engineering skills but are good at solving real problems grow up quickly.
1. Three paths to enter the FDE
If sorted by recommendation level:
Give priority to internships/school recruitment entrances, and at the same time, no matter which path you take, you must do real projects.
Because the FDE ultimately examines not "what have you learned", but:
Have you ever really solved someone else's problems?
Path A: Internships and new entrance-the most easily underestimated opportunities
Many people think that FDE is a position that can only be filled after several years of experience, but in fact, many companies have opened up internships and school recruitment.
Recruitment requirements are often not as high as expected.
The core is to look at three things:
The first is whether you have actually used AI.
Instead of simply asking a few questions, it's:
- What tasks have I accomplished with AI?
- Have you changed the original workflow?
- Have practical problems been solved?
Second, whether it has basic engineering capabilities.
You are not required to be an advanced developer, but at the very least you need to:
- Can write Python scripts;
- Can call API;
- Can build simple applications;
- Know how to investigate yourself when encountering problems.
Third, have you ever taken the initiative to do a project?
Coursework, personal projects, hackathons, and even helping others solve practical problems can all be proof.
Because what recruiters really want to know is:
Are you a person who will take the initiative to do things?
Path C: Complete a real delivery yourself-this is the main line
Whether you take an internship, school recruitment or policy channel, this path cannot be avoided.
Because the core question of an FDE interview is always:
"What problems have you solved in the past?"
Instead of:
"What courses have you seen?"
Education, certificates, and training experience cannot replace a real delivery.
A qualified FDE project should at least meet:
- Use real data;
- AI enters real business processes rather than staying in chatting;
- Have clear results;
- Ability to deploy and operate;
- Used by real users;
- Can measure the effect.
The most important of these are the last two points.
Many people can do demos but cannot complete the delivery.
The real difference is:
Demo proves that you can make things;
Delivery proves that you can solve the problem.
The first real customer is more important than the first technical project
The paths many people learn AI are:
Learn models → learn frameworks → do demos → find a job.
But the FDE is closer:
Find problems → design → rapid verification → deliver results.
So you need to face real users as soon as possible.
The first customer does not have to pay.
Its value isn't income, it's the experience you get:
Customers do not accurately describe their needs;
Data is usually incomplete;
The process must be more complex than imagined;
Things will definitely change halfway through.
These experiences cannot be gained by reading tutorials.
The way to find customers is actually very simple:
- Your past industry connections;
- Small businesses without technical teams;
- Individuals or teams who often complain about duplication of work.
The first cooperation can be cheap or even free, but it must be clear:
Delivery of what?
How to accept it?
How to judge the effect?
When you are done, record the process.
Because this copy is the most valuable resume material for you in the future.
The biggest difference between FDE and ordinary implementation is not how much technology is used.
Instead:
Can you identify the real problem and build a method that you can replicate later?
This is also the core ability of the FDE.