Most of your day as a risk analyst is spent proving that nothing is on fire, and a small part of it is spent finding the thing that is. You pull exposure numbers, check them against limits, question the people who took the risk and write it up so a committee can decide what to do. This is the day in credit and market risk at a mid-size bank, where a lot of risk analysts start.
The title covers several different desks. Market risk analysts watch trading positions and ask what happens if rates or prices jump overnight. Credit risk analysts look at borrowers and loan books and ask who might stop paying. Operational risk analysts chase process failures, fraud losses and vendor problems, and spend more time in interviews and control testing than in spreadsheets. Insurers and fintech lenders hire risk analysts too, and there the work leans toward pricing and underwriting data. Read the posting closely, because a market risk role and an operational risk role at the same bank can feel like two separate careers.
The risk system has run overnight and your first job is checking that it ran properly. You open the daily exposure report, compare it with yesterday, and look for anything that moved more than it should. A position that doubled overnight is usually a data feed problem, not a trader going rogue, but you don't get to assume that. You log the oddities in a tracker before anyone else is online.
One desk is over its limit on interest rate sensitivity. You confirm the breach is real by rebuilding the number from the position data in Excel, then email the desk head asking for an explanation and a plan to bring it back inside. They'll often push back and say the model is wrong. Sometimes they're right, and part of the job is being willing to check before you escalate.
A relationship manager wants to raise a client's credit line. You read the financial statements, run the ratios, look at covenants in the loan agreement and check how the industry is holding up. Your write-up recommends approving a smaller increase with a tighter covenant, which the relationship manager won't love. You attach your spreadsheet so the credit officer can follow your logic line by line.
This is where the plan breaks. The examiners have asked for a breakdown of commercial real estate exposure by property type and region, due by end of week. You write SQL against the loan data warehouse, find that property type is blank on a chunk of older loans, and spend most of the afternoon matching them by hand from the loan files. The credit review you planned to finish slides to tomorrow.
Before you log off, you update the slides for next week's risk committee. You run the stress scenario through the Python script your team maintains, check the loss estimate against last quarter's, and write the short note that explains why it moved. Senior managers read that note and skip the chart, so you rewrite it until they're plain and defensible.
You are paid to say no, or at least to say not yet, and the people you say it to often outrank you and earn more than you. Good weeks are quiet and nobody notices. Bad weeks come with an audit finding, a missed breach or a loss you flagged months ago that someone waved through. Some people love being the skeptic in the room. Others find it lonely, and they usually move to a front office or strategy role within a few years.
Finance, economics, statistics, math and engineering graduates get hired into analyst programs at banks and insurers. Bring evidence you can use Excel and SQL or Python on real data, because interviewers will test it. A class project on credit scoring or portfolio loss is worth putting at the top of your resume.
Credit analysts, underwriters and loan review staff already read financial statements and know how loans fail. Moving into credit risk is a natural step, and your knowledge of how the loan files are actually built is something new graduates don't have. Pick up SQL so you can pull the portfolio data yourself instead of waiting for it.
People from internal audit and compliance often land in operational risk, where control testing and process walkthroughs are the daily work. Accountants move into credit or enterprise risk because they already read balance sheets fluently. Expect to learn the modeling side on the job, and say so honestly in interviews.
8% of openings are fully remote.
$87,500 – $126,600
Typical range in the 36 of the newest 60 postings that list pay.
No. A financial analyst usually helps the business plan budgets and forecast revenue, so the work is about what the company wants to happen. A risk analyst works in a separate reporting line and looks at what could go wrong with positions, loans or processes. The tools overlap a lot, but the risk analyst's job is to challenge the numbers the business produces, and banks keep that independence on purpose.
More and more postings ask for SQL and either Python or SAS, and market risk roles lean on code heavily. You can start in credit or operational risk with strong Excel and learn the rest on the job. If you only learn one thing before applying, learn SQL, because every risk team pulls data from a warehouse.
The page shows the pay figure for this title. What moves it most is the type of employer and the type of risk: market risk and model risk roles at large banks tend to pay more than operational risk roles at smaller firms. A professional certificate such as the FRM and a few years of clean work on a regulated team both push you up the range.
HeroApply applies to them for you, so you can keep doing the job you have.