| Job Title | Business Analytics Analyst |
|---|---|
| Company | Citi (Citigroup) |
| Location | Gurugram, Haryana, India |
| Job Type | Full-Time |
| Work Mode | Hybrid |
| Experience Required | 1–3 years relevant experience (not fresher-friendly) |
| Education | Bachelor’s/University degree or equivalent experience |
| Application Deadline | October 1, 2026 (as of posting) |
| Estimated Salary/CTC | Roughly ₹9 LPA – ₹23 LPA for 1–3 years’ experience in this band. |
What You’d Actually Be Doing
Day to day, a Citi Business Analytics Analyst in Gurugram leans heavily on data-to-decision work: gathering operational data from cross-functional stakeholders, spotting patterns and trends, and translating findings into recommendations for business planning and process improvement. There’s a strong customer-behavior angle too — the JD specifically calls out translating data into “consumer or customer behavioral insights” to shape targeting and segmentation strategy, which suggests this sits closer to marketing/retail analytics than pure back-office reporting.
You’d also be expected to explore new data sources and tools on an ongoing basis rather than just running the same report every week, and to work directly with both internal and external partners on building and refining decision strategies. One line worth flagging for anyone in banking-adjacent analytics: the JD explicitly ties the role to risk awareness — “appropriately assess risk when business decisions are made” — which is fairly standard boilerplate at a regulated bank like Citi, but worth being ready to speak to in an interview if asked about compliance-mindedness.
Skills That Actually Matter Here
Citi’s qualifications list is short but specific: SQL, Python, Marketing Analytics, Statistics, and Market Research. That combination — coding plus classical stats plus a marketing lens — tells you this isn’t a pure data-engineering role; it’s closer to a decision-science/marketing-analytics hybrid. If your SQL is rusty on joins and aggregations or you haven’t touched Python for anything beyond notebooks, that’s the gap to close before applying, since multiple candidates in past Citi analyst interviews report being tested on exactly these basics early in the process.
FAQs
1. Is this a fresher-friendly role at Citi?
No. Citi’s own posting lists 1–3 years of relevant experience as a requirement. Final-year students or fresh graduates with no professional experience should look at Citi’s dedicated campus/graduate hiring programs instead of this specific listing.
2. Is this role remote or in-office?
Hybrid, based out of Gurugram, Haryana. The listing does not specify exact in-office days — confirm this directly with the recruiter or HR during the process, as hybrid policies can vary by team at large banks like Citi.
3. What technical skills should I brush up on before applying?
SQL (especially joins and aggregations), Python for data analysis, core statistics, and comfort with marketing/customer-analytics concepts like segmentation. Past Citi analyst interviews in India have tested SQL fundamentals directly, so this is worth prioritizing.
4. How long is Citi’s hiring process for analyst-track roles?
It varies by team, but past candidates for similar Citi Business Analyst roles report processes ranging from around 2–3 weeks up to 6+ weeks, typically across 2–4 rounds. Treat any single timeline estimate as a rough guide rather than a guarantee.
About Citi
Citigroup is an American multinational investment bank and financial services company headquartered in New York City. Founded in 1812 as the City Bank of New York, it has grown through mergers and acquisitions into one of the world's largest banking institutions, serving consumers, corporations, governments, and institutions across roughly 140–160 countries. Headquarters: 388 Greenwich Street, New York, NY 10013 Founded:...
View Company Profile →Top Interview Questions
Prepare with commonly asked questions for this role
In my last role, I used SQL to join transaction and customer-profile tables to identify a segment with declining engagement over three months. I flagged the pattern to the marketing team, who ran a targeted re-engagement campaign based on the segments I'd defined, which recovered a meaningful share of at-risk customers within the following quarter.
I'd describe exploratory analysis as "looking for patterns we didn't know to expect" — poking around the data with no fixed hypothesis. Confirmatory analysis is the opposite: we already have a specific question or hypothesis, like "did this campaign increase conversions," and we're testing it directly with a defined method rather than browsing.
I once found that a "high-value" customer segment the team had been prioritizing was actually shrinking in profitability once acquisition cost was factored in. I walked the stakeholder through the numbers step by step rather than leading with the conclusion, which made it easier for them to arrive at the same read on the data and adjust the targeting strategy.
Before finalizing any recommendation touching customer targeting, I check whether the underlying data use and segmentation logic align with internal policy and any applicable regulatory guidelines — for instance, avoiding proxies that could create unintended bias in who gets targeted or excluded, and flagging anything ambiguous to a compliance contact rather than assuming it's fine.
I'd start by understanding what business question the data is meant to answer before touching any code — talking to whoever requested the analysis to clarify scope. Then I'd profile the data for quality issues, run an exploratory pass to spot obvious patterns, and only then narrow down to the two or three angles most likely to produce something actionable within the timeframe.