Skip to content
Arknomics

Training · IB-1 · Lesson 03 of 08

The analyst role

The rule

The analyst is a quality-control layer. You build the model, format the page, and check every number twice because the vice president signs it.

Own the reliability of an output

An analyst converts incomplete information into work that a senior banker can review and use. That includes models, valuation pages, market updates, transaction materials and process trackers. Ownership means understanding the purpose of the output, not merely completing assigned cells. If you do not know whether a page supports a client decision or an internal discussion, you cannot judge which assumptions and presentation details deserve the most attention.

Quality control has several layers: the source data must be correct, the calculations must be consistent and the conclusion must match what the page actually shows. A neatly formatted table with mismatched periods is still wrong. Keep source references and explain adjustments so reviewers can trace the analysis. When a number changes, check the related text, charts and summary pages rather than treating the correction as a single-cell task.

Model, presentation and process work reinforce each other

Financial modelling is only one part of the role. Presentation work translates analysis into a sequence a client can follow, while process work keeps requests, deadlines and approvals coordinated. These tasks are connected: an overdue data request can weaken a forecast, and a misleading chart can distort an otherwise correct model. Effective analysts understand the flow between information collection, calculation, review and communication rather than treating each as a separate administrative burden.

During a sale process, you might update operating metrics, reconcile buyer questions and revise a management presentation in the same day. The priority is determined by the transaction timetable and the consequences of error, not by which task looks most technical. Ask who needs each output and when, clarify the review chain, and identify dependencies early. Good execution often consists of removing small uncertainties before they become urgent problems for the entire team.

Manage deadlines through explicit prioritisation

Multiple requests can exceed the time available even when every requester believes their task is urgent. Do not silently accept incompatible deadlines and hope to recover through speed. State your current assignments, estimate the work remaining and ask the appropriate senior person to resolve priority conflicts. This is a professional escalation, not an excuse to avoid work. Reliable communication lets the team allocate resources before a deadline becomes impossible.

Time estimates should include checking and review, not just initial production. A model that takes two hours to update may need another hour for source reconciliation and discussion. Build a backwards timetable from the external deadline and protect review time. If a new request removes that buffer, communicate the trade-off explicitly. The aim is not perfect scheduling in an unpredictable job, but avoiding preventable surprises about what will be ready and at what quality.

Worked example
Client deadline
18:00
Required review and revisions
90 minutes + 30 minutes
Analyst delivery target
16:00; a 15:00 request must be reconciled with existing work

Learn through review without repeating mistakes

Comments are useful when converted into a rule you can apply elsewhere. If a reviewer changes a chart axis, ask whether the issue was readability, comparability or an unintended impression. If a model adjustment is reversed, understand the accounting or valuation logic. Keep a concise record of recurring errors and review it before delivery. The value of feedback comes from reducing repetition, not from accumulating a large archive of marked-up pages.

Separate substantive disagreements from house style. You should follow consistent presentation conventions even when another format could also work, but you should question a financial relationship that appears wrong. Raise the issue with a source and a proposed resolution rather than a vague objection. Over time, stronger analysts need fewer mechanical corrections and contribute more useful questions because they have internalised both the technical standards and the purpose of the analysis.

Exercise judgement around confidential information

Analysts can encounter confidential financial results, potential acquisitions and investor-sensitive plans. Treat access as a responsibility, not permission to discuss the information casually. Use approved systems, check recipients and follow the institution’s restrictions on document sharing and personal trading. If a recipient list looks wrong or material appears to have been sent externally by mistake, escalate immediately through the relevant channels rather than quietly trying to repair the situation yourself.

Career development should follow from competence and curiosity, not from treating every assignment as a credential for a later job. Build accounting fluency, commercial understanding and a reputation for clear communication. Hours and promotion paths vary by firm, market and workload; do not assume a fixed programme guarantees a particular next step. The most portable skills are the ability to learn a business, test an argument and deliver accurate work under scrutiny.

Hold onto this

  • ·Typical hours run 70-90 a week, heavier on live deals and during financing windows.
  • ·Two-year program, then associate or an exit to private equity, hedge funds or industry.
  • ·The job rewards accuracy and speed over originality in years one and two.

Progress saved on this device

Education, not financial advice. Figures may be simplified for illustration.

One rule a week, in your inbox