A practitioner's roadmap for your first 90 days in Transaction Services — the learning curve, the mistakes everyone makes, and how to go from liability to trusted fast.
You got the offer, you signed, and now the real test starts. Everything you rehearsed in interviews about EBITDA adjustments or the net debt bridge gets stress-tested in week one — on a live deal, with a real client and a deadline that will not move for your benefit. The gap between knowing a definition and producing a clean piece of work under time pressure is wider than any candidate expects. Here is what those first ninety days actually look like, phase by phase, and how to get through them without drowning — and, better, how to come out the other side as someone a senior can hand ambiguous work to.
Nobody expects a first-year analyst to add value in week one. Your job in this phase is to absorb the machinery: how the team structures a databook, where the prior-year files live, which Excel shortcuts the seniors use without thinking, and what the house style for a workpaper looks like. Ask to shadow a call before anyone asks you to join one. Read a finished FDD report cover to cover — not to memorise it, but to see what a complete deliverable looks like before you are asked to produce a fragment of one. If you understand where your tab eventually sits, you will build it differently.
The single most common mistake in this phase is silence. New analysts believe that asking questions signals incompetence. It signals the opposite. A manager would far rather answer three clarifying questions up front than redo two hours of your work because you guessed at what "clean" meant. There is a craft to asking well, though: batch your questions, propose your own answer first, and never ask something a five-minute look at the file would resolve.
The fastest way to lose a reviewer's trust in month one isn't making a mistake — it's making a mistake you could have prevented by asking a thirty-second question and chose not to.
This is where the first real assignments arrive, and they are deliberately narrow and checkable: tie out a schedule, build one tab of the databook, reconcile the management accounts to the trial balance, pull a revenue-quality bridge for a single division. The tasks are small on purpose — small enough that a senior can review them quickly and catch errors before they compound into the report.
Two habits separate the analysts who accelerate here from those who plateau.
Master the technical foundations early, because they recur on every deal. The core four — EBITDA adjustments, the net debt bridge, net working capital, and the quality of earnings analysis — are not interview trivia. They are the grammar of the job, and fluency in them is what lets you spend your scarce attention on judgement rather than mechanics. The analyst who still has to think hard about how a net-debt bridge is built has no spare capacity left to notice that one of its lines looks wrong; the analyst for whom the mechanics are automatic sees the anomaly immediately. That is the whole point of drilling the fundamentals until they are boring — it frees you to be useful where it counts.
A word on speed, too, because juniors obsess over it. You will feel slow for months, and comparing your pace to a third-year's is pointless — they have simply seen the same schedule a hundred times. Speed is a by-product of pattern recognition, and pattern recognition only comes from reps. Do not chase speed directly by cutting corners on self-review; chase accuracy, log every correction, and the speed arrives on its own once the patterns are in your head.
By month two or three you will likely own an entire workstream on a smaller deal — say, the full net working capital analysis — rather than a slice of someone else's. This is the real inflection point. You stop merely executing instructions and start making judgement calls: what is normal, what needs flagging, and how to defend that call when a senior pushes back on it.
Expect your first genuinely hard moment here. A number that will not reconcile no matter how you cut it. A management team giving inconsistent answers across two sessions. A deadline colliding with data that is still 40% missing. How you handle that moment — flag it early, propose an approach, do not sit on it hoping it quietly resolves — is precisely what your staffing manager remembers when the next deal comes up. The analysts who go far are not the ones who never hit these walls; they are the ones who surface them fast and arrive with a proposed way through.
The first ninety days are not only a technical apprenticeship. Much of what separates a smooth first quarter from a rocky one is unglamorous and rarely mentioned in the offer letter: communication, calibration, and composure. When you send an update to your senior, does it lead with the answer or bury it under three paragraphs of process? When you flag a problem, do you attach a size and a proposed next step, or just hand over the worry? These habits are learnable, and they compound fast — the analyst who writes a crisp two-line status note is trusted with more than the one who writes a rambling essay or, worse, goes quiet.
Calibration is the other quiet skill. Early on you will not know which findings are trivial and which are deal-relevant, so you will either escalate everything (and become noise) or escalate nothing (and miss the material item). The fix is to ask, explicitly and early: "Is this the kind of thing you'd want to know about immediately, or is it fine to bundle into the weekly?" Reviewers respect that question because it shows you are trying to build the very judgement they are waiting for. Over a few deals, you internalise where the line sits and stop needing to ask — and that internalised sense of materiality is a large part of what being useful actually means.
Composure is the third. Deadlines slip, data arrives late, and a partner will occasionally be sharp with you under pressure. None of it is personal, and the analysts who thrive are the ones who absorb it, fix the thing, and move on rather than spiralling. The work is demanding by design; treating a bad hour as data rather than a verdict is what lets you keep learning through it.
Reviewers are not tracking your speed yet — they know that comes later. Here is what they are genuinely watching, and roughly when each should be landing.
| Milestone | By when | What a reviewer is checking |
|---|---|---|
| Ask smart, batched questions | Week 2 | You resolve the trivial yourself and escalate the real ones |
| Deliver a tied-out schedule | Week 4 | Your numbers self-review clean before they reach them |
| Source every figure | Week 6 | Any number traces to a document without you scrambling |
| Own a full workstream | Week 9 | You make and defend a judgement call, not just execute |
| Work comes back clean the second time | Week 12 | You don't repeat the same correction deal after deal |
Read that last row twice. Making a mistake once is not the red flag. Repeating the same correction across three deals in a row is — because it says you are not internalising feedback, and that is the one habit no reviewer can coach around.
Strip away the noise and reviewer judgement at ninety days reduces to three questions.
Even for an experienced hire moving from another line, interviewers probe how you handle the early curve — because it reveals self-awareness and resilience. Expect: "You're three weeks in, you own a schedule, and a number won't reconcile the night before a client call. What do you do?"
A strong answer sounds like this:
"First I'd resist the temptation to keep grinding on it silently until 2am — that's the classic first-year trap. I'd time-box the investigation: give myself, say, forty-five minutes to isolate whether it's a cut-off issue, a mapping error between the trial balance and the databook, or a genuine reconciling item. I'd document exactly what I've ruled out so nobody has to retrace my steps. If I can't close it in that window, I'd flag it to my senior that evening, not the next morning — with a clear one-line summary of the size of the gap, what I've already checked, and my best hypothesis for the cause. The point is to arrive with a proposed approach rather than just a problem. Sitting on it hoping it resolves itself is the worst option, because it removes the team's ability to make a call before the client sees it. Getting comfortable escalating early, with a source trail behind me, is the habit I'd want to build in the first ninety days."
That answer works because it shows judgement under pressure, a bias toward early escalation, and an understanding that documentation and a proposed fix are what a senior actually needs — not heroics.
One structural point worth understanding early: the reason the first ninety days feel so intense is that Transaction Services front-loads exposure in a way few graduate roles do. In many first jobs you spend months on training exercises before touching anything live. Here, you are on a real deal in week one because the model only works if juniors learn by doing on genuine engagements under genuine deadlines. That is uncomfortable, but it is also the fastest possible way to become good — you compress into a quarter what a slower environment would spread across a year. The discomfort is the mechanism, not a bug in it.
The learning curve in Transaction Services is steep because the work rewards people who absorb dense technical material fast under real deadlines. Your first ninety days are not a test of how much you already know — nobody expects much on day one — but of how quickly you convert feedback into habit, how honestly you surface what you can't yet do, and how reliably your second attempt comes back clean. Get those right and speed follows on its own. Get them wrong and no amount of raw technical knowledge will save you. Show up curious, self-review ruthlessly, and escalate early: do that for ninety days and you'll have quietly become the analyst the staffing manager asks for by name.
The Transaction Services Interview Programme (€119.99, one-time) includes a first-90-days survival module — self-review discipline, escalation scripts, and the reference-library system that stops you repeating corrections. Enrol today.
Hundreds of candidates prepared their interviews with this programme. Those who landed the role have one thing in common: they worked the cases before walking into the room.
