Your first 90 days should help you understand the customer problem, ship a safe first result, and make ownership clear. Treat this as a planning framework. Employers may use different milestones, and the public job postings reviewed here do not establish a standard FDE onboarding process.
Days 1–30: learn the system and the commitments
Start by learning what the team has promised and what customers or internal users rely on. Meet the people who own the product, engineering systems, deployment process, and customer relationship. Read the architecture, runbooks, incident history, security rules, and open customer issues.
Write down:
- who uses the system and what work it supports;
- which environments, data, APIs, and permissions are involved;
- what the role can decide and what requires another team;
- how success, incidents, and handoffs are recorded;
- where the job requires customer contact, production work, or travel.
Ask your manager to correct this map. The goal is shared context, not a promise to change the system in the first month.
Days 31–60: own a bounded delivery
Choose a small piece of work with a clear user, acceptance check, and rollback or recovery plan. Confirm the scope with the customer or internal owner. Implement or configure it using the team's tests, review, deployment, logging, and security practices.
Keep a short decision record. Include the requirement you accepted, the constraint you found, the trade-off you made, and the evidence that the result works. Surface a risk while there is still time to change the plan. A first delivery can be an integration, a production fix, a useful evaluation, or a documented workflow. The right shape depends on the role.
Days 61–90: make the next delivery easier to run
Complete the handoff and confirm who operates the result. Review what failed, what required repeated manual work, and which customer requests belong in product or core engineering. Propose one follow-up based on evidence. Close the loop with the user and record the outcome.
Agree with your manager whether explaining the role's customer, systems, decisions, listed risks, and next delivery is a useful goal for day 90. You may not have solved every problem. You should know which problems are yours and which need a different owner.
Confirm the actual job
Ask your employer which customers or internal users you will serve, what production work you will own, and when you will travel. A posting that omits travel does not establish that travel is zero.
Ask before you start:
- Which customer or internal team will I learn from first?
- What is the first bounded delivery, and who accepts it?
- What can I deploy, change, or promise without approval?
- Who owns support after handoff?
- How will the team review progress at 30, 60, and 90 days?
Use how to become an FDE for the broader transition and how to compare FDE job offers for scope, location, and travel questions.