The offer is the start line, not the finish. Here is what to do, learn, and ship across your first three months as a cloud engineer — as a checklist you can tick — and how to handle the voice that says you don't belong here. You do.
Companies with structured onboarding see new hires reach productivity in 8–12 weeks instead of the usual three to six months. If your employer hands you a plan, follow it. If they don't — and many won't — this is the plan. Tick the boxes as you go; your progress is saved on this device.
The ramp begins before your first login. A little groundwork in the days before you start turns a nervous week one into a confident one.
The first month is not for heroics — it is for orientation. Your job is to become dangerous slowly: get access, meet people, read the estate, and prove the pipeline works for you with one tiny change. Nobody expects output yet; they expect you to be learning fast and asking well.
Month two is where you shift from taking help to doing work — with a mentor still close. You own real tickets, you start reviewing others' code (which teaches the codebase faster than writing it), and you turn your newcomer eyes into better documentation before they fade.
By month three you are operating at near-full capacity with appropriate support. You deliver things others depend on, you take a real on-call shift, and — the move that marks the transition from new hire to engineer — you propose an improvement with a written trade-off, not just execute what you're handed.
You learn a team faster by asking than by guessing. Bring these to your first 1:1s — the answers align your effort with what actually matters, and asking them well is itself a senior signal.
Somewhere in the first ninety days — often right after a compliment — a voice will tell you that you fooled everyone, that the others are real engineers and you are faking it, and that any day now they'll find out. That voice has a name, and a statistic.
report feeling like impostors — in a survey that included engineers at Google, Amazon, Microsoft, and Meta. It is not evidence that you don't belong. It is the ordinary tax of a fast-moving field full of high-achievers, and the people who intimidate you are very often paying it too, quietly, in the next chair.
The reframe that actually helps: the gap you feel is the distance between everything there is to know (infinite, and growing) and what you know (also growing, faster than you notice). Everyone has that gap — principal engineers included. They have simply made peace with it and learned to say the most senior sentence in the field: "I don't know that yet — I'll find out." Feelings are not facts. If you're in the seat, someone competent bet on you; that bet is evidence, and it outranks the voice.
Feel the doubt. Ship the pull request anyway.
Further reading, on this site: the questions to ask in the interview that reveal whether a team will actually support this ramp are on the interview page; the three projects that got you here — the ones you'll draw on in month one — are the capstone plates; and the résumé and job-search craft is Class 42. The first ninety days are where the whole course stops being study and starts being your job.