Research Analyst Resume Format, with 3 Full Samples

The format that works for research analyst resumes in India

Reverse chronological is the only layout worth using. Put the most recent role first, work backwards, and let the dates sit in plain view. Functional resumes that group everything under Skills and quietly drop the dates read as an attempt to hide a gap, and hiring desks treat them that way. A research role is built on judgement, and hiding your timeline is the opposite signal. Length is decided by evidence. One page holds everything a fresher and most analysts up to roughly six years have to say. Past that, a second page is fine when it carries real coverage, real calls and real study ownership rather than a longer tool list. A page two built from a declaration paragraph and a hobbies line is a padded one-page resume. Four things belong nowhere on a professional resume here: a photograph, date of birth, marital status and father's name. They survive from an older template that circulated through campus placement cells. Nobody screening a research analyst is looking for them, and every line they occupy is a line a call, a study or a result could have used. Send a PDF unless the posting asks for DOCX, and name the file with your own name and the target role rather than resume_final_v4. Use a single column all the way down, because two-column layouts parse unpredictably when a sidebar sits beside the experience. The table below sets out the section order.

Listing Bloomberg is not the same as proving a call

The single most common research resume failure is a skills line that reads Excel, PowerPoint, Bloomberg, Refinitiv, SPSS, SQL, financial modelling, valuation, data analysis, with no bullet anywhere that shows any of it producing a decision. A parser matches those terms, but a research lead reads the wall and assumes it is a course list, then goes looking for the one call or study you can actually defend. The fix is to let the experience prove the tool. If you write DCF on the skills line, at least one bullet should describe a valuation you built and the target it produced. If you write conjoint, a bullet should name the pricing decision that conjoint changed. The equity sample lists provisioning and asset-quality analysis precisely because a bullet shows an asset-quality turn called ahead of consensus. The market research sample lists conjoint because a bullet shows a 12 percent price change. The skills line and the experience agree, which is what makes both believable. Be specific about method and sector. "Covered 14 banks and non-bank lenders" or "ran brand-health and usage-and-attitude studies for consumer clients" tells a reviewer exactly what kind of analyst you are, where "experienced in research and analysis" tells them nothing. Sector and method are the two facts a research desk screens on first. Do not pad the tool list with software you touched once. Listing SPSS, R, Python, SAS, Stata, Tableau, Power BI and Qlik when you have only ever used Excel and SPSS invites a question you cannot answer. Two tools you can be interviewed on beat eight you cannot.

For every tool and method on your skills line, ask: is there a bullet where it produced a call, a study or a decision. If not, either add the bullet or cut the item. A wall of unproven tools helps the parser and hurts the interview.

Writing a summary a research lead actually reads

The block under your name is the part you can be reasonably sure gets read, so it should carry three facts: what you research, how long you have been doing it, and the strongest thing that happened because of your work. Three or four lines, no adjectives that cannot be checked. The old objective line, seeking a challenging position in a reputed organisation to utilise your analytical skills, tells the reader nothing they did not assume from the application. Replace it with a summary. An objective describes what you want, a summary describes what you have already done, and only one is evidence. Freshers often believe they have nothing to summarise. Look at the fresher sample: it names the coverage attempted, states the internship length, and points at an initiating-coverage note with a target and a thesis. That is a genuine summary built from coursework, one internship and real notes. What it avoids is "passionate about finance and markets", a phrase so common on graduate resumes it now carries no information. A practical test: read your summary and ask whether a classmate with the same degree and CFA level could paste it onto their resume unchanged. If they could, it describes the qualification, not you. Add the specific sector, the specific call and the specific ownership until it stops being transferable.

Experience bullets: method, finding, decision

Every strong bullet in the samples follows the same shape. It names the method or study you ran, states what you found, and closes with the decision it drove or the number it moved. The method establishes rigour. The finding shows judgement. The decision does the persuading, because research that nobody acted on is just a document. Start with the outcome and work backwards. Analysts usually write the activity first, then struggle to attach a consequence, which produces bullets like "conducted market research and prepared reports for the management". Instead ask what was different after your work landed: a launch happened, a price changed, a position was sized, an estimate was proven right, a turnaround dropped. Then write the sentence that ends in that fact. Vary the metric. Four turnaround numbers in a row read as one trick repeated. Across a real role you can honestly reach for accuracy of a call, revenue or margin impact, price change, study turnaround, sample quality, coverage size, client meetings and notes published. The samples use several metric types each, which reads as range. Where you lack a number, give scope: how many companies covered, how many studies a quarter, how many clients, how large the sample. "Own 6 to 8 studies a quarter for two FMCG clients" carries weight without inventing a percentage. In research, being honest about what you cannot measure is itself a credibility signal. Allocate bullets by recency. Current role gets five or six, the previous role four or five, anything older two or three.

If a bullet would read identically on a teammate's resume, it is describing the desk, not you. Rewrite it until it only fits the coverage or study you actually owned.

The skills section: grouped, honest, and short enough to defend

A research resume's skills section has two audiences with opposite preferences. The parser wants literal terms it can match, financial modelling and SQL and conjoint. A human wants a short, organised list that signals what kind of analyst you are. Grouping satisfies both. Group by function rather than one long line. Research method, valuation or analysis, tools, and data sources is a grouping that works for almost every research analyst. The exact headings matter less than the fact that structure exists. Write names the way the industry writes them: Refinitiv not Reuters Eikon if that is what you used, Power BI not PowerBI, SPSS not spss. A parser matches on strings. Twelve to sixteen skills is the working range. Below eight the section looks thin. Above twenty it stops being a signal, and a research resume is especially prone to tool padding: listing eight statistical packages and four visualisation tools when your work lives in Excel and SPSS. The list is a contract: every item is a question you have agreed to answer. Do not include a proficiency bar. Star ratings invite an argument you cannot win, and nobody agrees on what four stars in valuation means. Let the experience prove the depth instead.

Notes, studies and projects: what to include and how to describe it

For a fresher, real research output is the resume. A published note, a full model, a survey you designed and read out sits above experience, gets the most space, and is where a reviewer decides whether you can actually form a view or only pass exams about finance and statistics. For an experienced analyst this moves into the experience section as coverage, and any standalone project is kept only if it shows something the day job does not. The common failure is describing the activity instead of the argument. "Prepared a research report on the FMCG sector" tells a reviewer nothing, because thousands of resumes carry that exact line. Describe what you concluded, what it rested on, and what would prove it wrong. The initiating-coverage note in the fresher sample is a stronger entry than a longer report would be, because it names a target price, a thesis and the assumptions the whole call depends on. Pick output that shows range rather than three versions of the same report. One full model with a valuation, one primary study you designed and analysed, and one comparative sector piece that ends on a call is a stronger set than three descriptive summaries. Two well-argued pieces beat five listed by title. If your work is public, on a research portal, a blog or a competition, say so in plain text. If it is a class assignment dressed as a note, do not oversell it, because an interviewer who reads it will read the gap between the claim and the content. Be honest about the sample size of a survey and the limits of a model, because stating limits is exactly the judgement a research desk is hiring for.

Where education and certifications belong

Education goes at the bottom for anyone with a full-time job, and near the top for a fresher, who has nothing stronger to lead with. Degree, institution, years. That is the whole entry for most people. A research MBA or a strong economics or commerce degree is worth naming clearly, because it is a real screen for entry roles. CGPA or percentage is worth keeping while you are a fresher and it is good, roughly 7.5 out of 10 and above, because campus and early-career screening still filters on it. Once you have your first full-time role and a call or study to point at, drop it. A number from four years ago competes for space with research that is far more predictive. Coursework and academic projects are for freshers only, and only when directly relevant. Financial statement analysis, econometrics, corporate finance and consumer behaviour are worth naming. A generic management module is not. Skip school details once you have a degree. Certifications sit just below education, or beside skills if you hold only one or two. For research in India the ones that carry weight are specific: the NISM Research Analyst certification is a regulatory requirement to publish equity research, so listing it says you are already cleared. The CFA, at whatever level you have cleared, is the single strongest signal for equity research, and the FRM for risk-tilted roles. For market research, a modelling or analytics certificate and a conjoint or advanced-methods course are worth naming. Write the full name, the body and the year or level. An expired or overstated certification is easy to catch, so keep it accurate.

Getting through the applicant tracking system

An applicant tracking system is a parser and a search index, not a judge. It reads your file, tries to break it into name, dates, employers, titles and skills, and stores the result so a recruiter can search across candidates. Almost every ATS problem is a parsing problem, and parsing problems come from layout, not wording. The layout rules are short. One column. Standard section headings, so use Work Experience rather than My Journey, and Skills rather than My Toolkit. No text inside images, because a chart or logo strip reads as empty space. No critical information in the header or footer region, which some parsers drop. Avoid text boxes and nested tables in the resume body. On wording, mirror the language of the job description where it is honest. If the posting says equity research, write equity research. If it says market research analyst, use that exact title rather than a clever internal one. Include the expansion alongside an acronym at least once, for example "DCF (discounted cash flow)" and "UAT (usage and attitude study)", so both searches find you. Keyword stuffing does not work. A hidden block of every tool and method in white text is found quickly, and the outcome is worse than being filtered. Write real bullets that naturally contain the right terms, because a bullet describing a conjoint that changed a price contains the word conjoint in a context that survives human review too. Save as PDF from a tool that embeds real text, then open the file and confirm you can select and copy a sentence. If you cannot select the text, neither can the parser.

Test your own file before you send it. Copy the text out of the PDF into a plain text editor. Whatever you can read there is roughly what the parser sees, and anything scrambled is a real risk.

What gets research analyst resumes rejected

Most rejections at the resume stage are not close calls. They come from a small set of recurring problems, and all of them are fixable in an afternoon. The list below covers what reviewers of Indian research analyst resumes see most often, in rough order of how much damage each one does.

• A tool and method wall with no bullet showing any of it produced a call or a decision. Every item is a question you have agreed to answer.
• Activities copied from the job description instead of findings and outcomes. "Responsible for conducting research" is the tell.
• No decision anywhere. Research that nobody acted on reads as a document, not analysis. Name the launch, the price change, the position, the estimate that was proven right.
• No sector or method stated, so a desk cannot tell whether you cover banks or FMCG, or run quant studies or qualitative ones.
• For equity roles, no mention of the NISM Research Analyst certification, which India requires to publish research.
• A photo, date of birth, marital status or father's name. None of it belongs on a professional resume, and it takes a call's space.
• Padding the tool list with statistical packages and BI tools you touched once, which an interviewer probes in the first five minutes.
• A generic objective line. Replace it with a summary that states domain, years and one result.
• Overstated CFA or certification status, such as writing CFA when you have cleared only Level I. Verification is standard and a mismatch ends the process.
• Charts and dashboards pasted as images with the numbers trapped inside them, which the parser reads as blank and a busy reviewer skips.

Read your resume aloud once before sending it. Any line you could not defend to an analyst across a table is a line to cut or rewrite.

Skills to put on a research analyst resume

Certifications worth listing as a research analyst

Keywords an ATS scans for in a research analyst resume

These are the literal terms a parser matches against the job description. Use the ones that are true of you, in the sentences where you did the work, not as a list at the bottom.

• research analyst
• equity research
• market research
• financial modelling
• valuation
• DCF
• financial analysis
• quantitative research
• survey design
• data analysis
• SQL
• excel
• SPSS
• power bi
• bloomberg
• consumer insights
• market sizing
• sector coverage
• report writing
• NISM research analyst

Research Analyst resume FAQ

Related resume examples and guides