- Spend the first month mapping commitments and permissions rather than changing the system.
- Own one small delivery with a named acceptance check and a rollback plan before taking a second.
- Close the loop by confirming who operates the result, because an unowned deployment comes back to you.
- Ask before you start which customer you serve, what you can deploy without approval, and who owns support.
- This is a plan to propose, not a standard: employers set their own milestones and the postings do not describe one.
Days 1–30: learn the commitments
Meet the people who own the product, the engineering systems, the deployment process and the customer relationship. Read the architecture, runbooks, incident history, security rules and open customer issues.
Write down who uses the system, which environments and permissions are involved, what the role can decide alone, how incidents and handoffs are recorded, and where the job requires customer contact, production work or travel. Ask your manager to correct that map.
Days 31–60: own one bounded delivery
Choose a small piece of work with a clear user, an acceptance check and a rollback plan. Confirm the scope with the customer or internal owner. Implement it using the team's tests, review, deployment and security practices.
Keep a short decision record: the requirement you accepted, the constraint you found, the trade-off you made, and the evidence that it works. Raise a risk while there is still time to change the plan.
Days 61–90: make the next delivery easier
Complete the handoff and confirm who operates the result. Review what failed, what needed repeated manual work, and which customer requests belong in product or core engineering. Propose one follow-up from that evidence.
You will not have solved every problem by day 90. You should know which problems are yours and which need a different owner.
Confirm the actual job 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?
A posting that says nothing about travel has not told you travel is zero. Ask.