Academic snapshot
Marks: 7.0+ / 70% on many campuses; 6.5 on some off-campus posts
Degree: BE/BTech/MTech; CS/IT/ECE/EEE common
Backlogs: None active
Year: Drive-specific (2025-only posts exist)
Tiger Analytics is an analytics and AI consulting firm with roots in Santa Clara and a major presence in Chennai. It works with retail, consumer packaged goods, and technology clients on data science projects. India freshers typically join as Trainee Analysts before moving into client-facing analytics roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Tiger Analytics does not publish one eternal CGPA. Campus cells often print 7.0 / 70%. Some 2025 off-campus Trainee Analyst drives listed 6.5 plus a city filter. Read the mailer.
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | PPT, 7.0-style list, online interviews | SQL + case bar |
| Off-campus | City restriction (Chennai/BLR/HYD), in-person assessment, batch year | Same technical flavour |
| Referral | Visibility | You still write SQL live |
Off-campus does not mean easier SQL. 2025 Chennai drives advertised ~150 Trainee Analyst seats and still ran in-person technicals.
Is 7.0 enough? It matches many campus notes. 6.5 appears on some off-campus Trainee Analyst posts. If your cell says 7.0, a 6.7 will not debate its way in. A 7.1 who cannot write a JOIN loses to a 6.8 (when 6.5 is allowed) who can.
What helps the resume screen: SQL projects, Python notebooks with a business question, internships in analytics. A GAN tutorial with no metric is weaker than a simple sales dashboard you can explain. See certifications after SQL, not instead of it.
Academic snapshot
Marks: 7.0+ / 70% on many campuses; 6.5 on some off-campus posts
Degree: BE/BTech/MTech; CS/IT/ECE/EEE common
Backlogs: None active
Year: Drive-specific (2025-only posts exist)
Skills they actually filter
OA: SQL, Python, probability/aptitude
Interviews: SQL live, puzzles, case, resume
Languages: Python, SQL (C/C++ on some JDs)
HR: Chennai/hub relocate, often very short
| Item | Typical expectation | Reality check |
|---|---|---|
| Graduation | 7.0 / 70% campus; 6.5 some off-campus | Mailer wins |
| Branches | CS/IT/circuital | Broader on some lists |
| Backlogs | None live | Clear before joining |
| City | Relocate to Chennai/BLR/HYD | Some drives require you already live there |
| Joining | Immediate on some off-campus | Exam dates: say so early |
Good fit: You like business questions with data, you will write SQL in front of someone, and you will move to Chennai if asked. You do not need a Kaggle Grandmaster badge.
Harder path: You only practised TCS aptitude; you refuse to relocate; you answer cases with “I would use BERT.” Tiger HR can be five minutes and still fail you on city.
Branch myth: Circuital students clear Trainee Analyst when SQL is real. CS students fail when they only know LeetCode and cannot define a KPI.
Gaps: Immediate-joiner language on some 2025 posts. A gap needs a story. Live backlogs are a no.
Download 2026 Tiger Analytics placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Tiger Analytics does not publish a permanent official paper set. Papers here are pattern trainers for SQL/Python/aptitude and for interview puzzles. Exact OA breakdowns are not fully detailed in cited posts.
| Round (typical) | What to practice |
|---|---|
| OA | SQL, Python, probability, aptitude |
| Tech 1 | Coding, SQL, OOP/DBMS, puzzles |
| Tech 2 / case | Resume, scenarios (traffic, retail), more SQL |
| HR | Relocate (Chennai), sometimes almost nothing else |
Think of papers as simulators for SQL-under-clock, not as leaked live forms. Themes repeat (joins, averages from DOB, water-jug, churn framing) more than exact clones.
| Theme you saw | Drill next | Why Tiger asks it |
|---|---|---|
| SQL JOIN / GROUP BY | Window functions next | Core job |
| DOB → age filter | Date functions | GFG-style live SQL |
| Probability puzzle | Bayes + expected value | Tech round |
| Water jug / logic | Speak constraints first | Puzzle style |
| Python list/dict | pandas filter/groupby | OA + tech |
| Churn / traffic case | One metric + data plan | Consulting |
Tiger Analytics hires freshers through campus cells, tigeranalytics.com careers, and referrals. After eligibility, the shape is analytics consulting: an OA that is not only quant, then SQL/case interviews, then a short location HR.
Campus recruitment
PPT → OA → two technicals (often virtual) → HR. GFG DS loop was fully online until a tiny HR.
Off-campus / office
Trainee Analyst drives may be in-person in Chennai (or BLR/HYD) with a city filter. Apply on careers; show up if shortlisted.
Referrals
Help the screen. You still write SQL while someone watches.
7.0 or 6.5 as printed. Branch. City. Immediate joiner if listed. Put SQL + one business project on line one of skills.
Student reports: present before interviews on Trainee-Analyst accounts; coding/SQL/probability across the process. Section-level counts are not verified in our source set. Working map:
| Block | What to expect | Pass habit |
|---|---|---|
| Aptitude / prob | Easy-medium quant, stats | Accuracy over CAT tricks |
| SQL | Joins, aggregates, maybe windows | Write, do not only MCQ-pick |
| Python | Easy coding or data tasks | Complete > clever |
Details: online assessment.
GFG DS: OOP and DBMS confidence areas, then SQL (employees in HR older than 30 when table stores DOB). Other accounts: coding + probability + puzzles. Speak the approach. If you claim OOP, expect overloading vs overriding in one minute, then they will still ask SQL.
Resume walkthrough, what you learned, real-world scenarios (traffic management in one note), more SQL or Python. Structure: metric → data → simple analysis → caveat. “I would build a deep learning pipeline” without a KPI is a reject tell.
GFG DS: only “will you relocate to Chennai?” Some loops add Why Tiger, PORs, notice. Do not prepare a 10-minute life story for a 5-minute round. Prepare the city sentence.
| Phase | Duration | What happens |
|---|---|---|
| Apply / cell list | 3-10 days | Shortlist |
| OA | 1 day | SQL/Python/aptitude |
| Two technicals | 2-14 days | Virtual or onsite |
| HR + offer | Same day to 1 week | Location check |
| End to end | ~2-6 weeks | Off-campus can compress into office days |
SELECT nameFROM employeesWHERE department = 'HR' AND TIMESTAMPDIFF(YEAR, dob, CURDATE()) > 30;(or the equivalent date logic your dialect uses). Explain why you did not store age as a static column. That is the GFG-style bar.
Next drills: ROW_NUMBER() for latest order per customer; HAVING COUNT(*) > 1 for duplicates; a self-join for manager names.
Interviewer: “Customer churn is up.”
Good: “I would define churn (no purchase in 90 days vs subscription cancel), pull cohort by acquisition month, compare frequency and AOV, then check one operational cause (stockouts, delivery).” I need those tables; I would not start with a neural net.”
Bad: “I would use XGBoost and SHAP.”
Traffic scenario: constraints, data you would collect, one metric (wait time, throughput), one experiment. Same skeleton.
Water jug (3L and 5L to get 4L): state the invariant (you can obtain multiples of gcd). Then walk fills. Dice/Bayes: write the formula before plugging numbers. Silence while you stare at the ceiling is worse than a slow correct setup.
Saturday: 20 SQL queries (timed 40 min) + 2 Python tasks.
Saturday evening: one case recorded.
Sunday: OOP/DBMS 20 min + jug/Bayes 20 min + Chennai sentence.
Two weekends beat a month of unread “AI consulting” LinkedIn posts.
1. Churn is up. Define churn, cohort by start month, compare frequency and AOV, check one ops cause (stockout, late delivery). Name the tables. Caveat: seasonality.
2. A campaign “did not work.” Ask what “work” meant (revenue, new users, ROAS). Compare holdout vs exposed if they have it; if not, say you cannot claim causality. Next data pull: spend, conversions, margin.
3. Warehouse wait time. Metric: minutes from dock-in to putaway. Data: timestamps, labour, inbound volume. Simple view: peak hours vs staffing. Experiment: extra shift on the worst two hours.
Memorise the skeleton (metric → data → analysis → caveat), not a script. Interviewers change the industry; the skeleton does not.
If you only know JOIN + GROUP BY, add:
ROW_NUMBER() OVER (PARTITION BY customer_id ORDER BY order_date DESC) for latest orderLAG(amount) OVER (PARTITION BY customer_id ORDER BY order_date) for previous spendSUM(amount) OVER (PARTITION BY customer_id) vs GROUP BY (when you still need row detail)Write each once on paper with a 6-row toy table. Tiger interviews love “latest / previous / running” questions more than graph DP.
If the post says candidates must currently be in Chennai, Bengaluru, or Hyderabad, do not apply from another city and hope. In-person assessment plus a 5-minute HR on relocate is how they enforce it.
If you are in those cities but do not want Chennai long-term, say the truth in HR. A yes you will reverse in two months is worse than a clean no.
If campus HR only asks Chennai and you need to finish exams first, say the exam date and ask if joining can wait. Immediate-joiner off-campus posts may not wait.
Speak the setup. A correct setup with arithmetic slip is more hireable than a silent lucky number.
Degree, all marksheets, ID. Analytics offers still run background checks on CGPA. Keep the OA screenshot and interview mails. If they flew you to Chennai for in-person, keep travel proofs for reimbursement if the mailer promised it.
Tiger can take a large Trainee Analyst batch and still reject you for a blank JOIN. Volume is not a participation trophy. Your edge is SQL you can write + a business sentence + a city yes, not a transformer-from-scratch repo.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Tiger Analytics invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Tiger Analytics sits around ₹8-14 LPA (candidate-reported - confirm the letter). Languages students mention most often: C++, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Campus notes commonly cite 7.0+ CGPA or 70%; some 2025-2026 off-campus Trainee Analyst posts list 6.5 CGPA, BE/BTech/MTech in CS/IT/circuital branches, no active backlogs, and immediate joining. One GFG Data Analyst campus account mentioned 7+ at a Tier-1 non-circuital list. Always verify the careers page or college mailer.
What you are training for: Typical fresher loop: online assessment (SQL, Python, probability/aptitude) → two technical interviews (coding/SQL/stats plus resume/case) → short HR. GFG Trainee-Analyst DS: OA → tech (OOP/DBMS) → resume tech → ~5 min HR on Chennai relocate. Timeline often 2-6 weeks. Some off-campus drives run in-person assessments in Chennai/Bengaluru/Hyderabad.
Short version of the prep split: Prioritise SQL (joins, windows, aggregations) and Python data manipulation, then probability/statistics puzzles, then one business case you can structure aloud (churn, pricing, campaign). Aptitude still appears. Full plan: /tiger-analytics/preparation-guide/.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Tiger Analytics previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Tiger Analytics drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Tiger Analytics usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Tiger Analytics?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Tiger Analytics-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Tiger Analytics story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Tiger Analytics papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Tiger Analytics papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Tiger Analytics-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Figures are candidate-reported as of August 2026.
| Band | Typical CTC | Notes |
|---|---|---|
| Trainee Analyst / DS fresher (this hub) | ₹8-14 LPA | Campus-style reports; confirm letter |
| Off-campus trainee blogs | ₹6-12 or ₹6-9 LPA | Same title, different post |
| Intern | Stipend | Separate |
Do not treat the top of ₹14 LPA as a negotiation opening before you have paper. Analytics consulting bands sit above mass GET 4 LPA and below FAANG.
Client analytics work (retail/CPG/tech), learning on live data, Chennai/HYD/BLR offices. Hybrid depends on team. Relocation is the benefit you must accept to get the rest.
Know ₹8-14 LPA as the hub band and that some trainee posts quote lower. Ask split. This is not the round to case-interview your own salary.
Trainee Analyst volume
Off-campus 2025 notes cited ~150 Chennai seats with in-person selection and a city filter.
SQL + case still the filter
Not a 60Q services mill. Probability puzzles and live SQL remain.
HR can be tiny
5 minutes, relocate question only, in one GFG DS report. Still eliminatory.
6.5 vs 7.0
Off-campus 6.5 exists beside campus 7.0. Use the number on your post.
Net for 2026: do not wait for a leaked OA PDF with perfect sections. Write SQL every day, keep one case, decide Chennai before they ask.
Yes. Free Tiger Analytics placement papers PDF and 2024-2026 style SQL/Python/aptitude practice are on this site. Start with the 2026 PDF or the archive.
OA → one or two technical/case interviews → HR. GFG DS: OA, OOP/DBMS+SQL, resume tech, 5-min Chennai HR. Often 2-6 weeks. Some off-campus loops are in-person.
Usually 3-4 stages. Count OA plus technicals plus HR. HR can still be a round even at 5 minutes.
Yes on many loops: business scenarios plus probability puzzles. Structure a metric and data plan. Not a full MBB case library.
Main fresher analytics consulting title. SQL/Python on client problems (retail/CPG/tech). Selected via the process above. Chennai is a frequent hub.
Python and SQL. C/C++ on some JDs. Interviews expect live SQL either way.
Often yes. One GFG HR was only that question. Some off-campus drives require you already live in Chennai, Bengaluru, or Hyderabad.
Commonly 7.0+ CGPA or 70% on campus; some Trainee Analyst posts 6.5; listed engineering degrees; no live backlogs. City/batch rules are post-specific. Same spirit as recent cycles unless your mailer changed.
Candidate-reported ₹8-14 LPA on this hub; some trainee blogs ₹6-12 / ₹6-9 LPA. Confirm the letter. Cities: Chennai, Hyderabad, Bengaluru.
SQL every day, Python data tasks, probability puzzles, one 90-second case, location decision. Guide: preparation guide.
Different. Less mass aptitude, more SQL/stats/case. TCS-only prep is the wrong sport.
Write 20 SQL queries a week, then explain one business metric in 90 seconds. Decide location before HR. Do not treat this as a generic coding test.
All analytics/decision-science flavours. ZS/Mu Sigma can feel more case/gating-test. Fractal similar AI consulting. EXL more services-analytics hybrid. Tiger’s public fresher notes emphasise SQL + puzzles + Chennai. Prep SQL+case for all; add the city filter for Tiger off-campus.
Basics help. Live SQL and a business sentence matter more than a GAN repo. If you list ML, expect “when would you not use it.”
Joins, GROUP BY, HAVING, date/DOB filters, then window functions (latest row, LAG, running totals). Write them on paper, not only in a GUI.
Circuital branches are common. Some campus lists include non-circuital with a 7+ CGPA. SQL still decides the cabin. Match the mailer.
OA, then two technicals, then HR offline. Tech: coding, SQL averages, probability, 3L/5L jug puzzle. Small final select set. Takeaway: puzzles are in-scope; SQL is not optional. Source: GeeksforGeeks.
OA → 30-min tech (OOP/DBMS + SQL on DOB/age) → 30-min resume tech → 5-min HR: Chennai relocate, no Why Tiger. Takeaway: know your resume cold; decide city before they call. Source: GeeksforGeeks DS.
Chennai office, in-person, city filter (Chennai/BLR/HYD), Python/SQL/C, large seat count in one blog. Takeaway: if you are not in those cities, the “open drive” may not be open to you.
What to steal: SQL on paper; one puzzle spoken; one case; Chennai sentence; resume bullets you can defend.
What to ignore: Memorising someone else’s exact jug steps as the only puzzle; quoting ₹14 LPA as guaranteed; skipping location because technicals went well.
Selected vs rejected: Helped: clean JOIN, calm puzzle talk, yes to city. Hurt: ML buzzwords without a KPI, surprise at Chennai, blank SQL on DOB.
In-person office day composite: OA or written in the morning, technicals afternoon, HR if you survive. Students who “saved case prep for later” never got later. Takeaway: have the 90-second churn skeleton ready before you enter the building.
Resume-tech composite: Interviewers opened GitHub and asked what you changed in a group project. A fork with no commits is a red flag. Delete or own it.
Puzzle freeze composite: A candidate knew the 3L/5L solution from a video and could not adapt when asked for 1L or a different jug pair. Takeaway: learn the gcd invariant, not one YouTube choreography.
Tiger Analytics is an analytics consulting hire. The sport is SQL you can write, a probability setup you can speak, a 90-second business skeleton, and a city sentence. It is not TCS NQT and it is not a FAANG onsite. Students who only practise one of those four still fail a round that looked “easy” on paper.
Use this site sets as SQL/Python/aptitude simulators, not as leaked OA. Follow the preparation guide for a week calendar. Read interview experience for the GFG DS and DA notes and the HR page even if HR is five minutes. Five minutes is enough to fail relocate.
If Tiger, Fractal, Mu Sigma, ZS, and EXL are all on your list, keep a shared SQL+case core and add each firm’s twist (ZS case density, Mu Sigma gating tests, EXL services hybrid, Tiger’s Chennai filter). Do not build five unrelated prep piles.
Immediate joiner: if the post says it and you have finals in three weeks, ask before you travel for in-person. A wasted office day helps no one.
Kaggle and certificates: one notebook with a clear question and a metric beats five course badges. If you list a competition, know your rank and what you actually did.
Group projects: interviewers will ask who wrote the SQL. If the answer is “my teammate,” delete the bullet or learn it tonight.
Week-of-drive: 10 queries from the error log, one case, city sentence, sleep. Do not start a new deep-learning course. Do not memorise a 40-page casebook. The skeleton is enough.
Offers: read city and joining date. Analytics CTC chatter (₹8-14 LPA vs ₹6-9 trainee blogs) is not your letter. Believe the PDF. Keep marksheets matching the CGPA you typed. Background check will notice.
If you will not move to Chennai/Hyderabad/Bengaluru, stop applying to city-filtered Trainee Analyst posts and spend the week on a firm that will let you stay. That is a better use of SQL practice than a 5-minute HR no. Be kind to yourself and to the next candidate on the waitlist.
Interview day (virtual): stable network, notebook for SQL, no second laptop “notes” that you will get caught reading. Write the query in the shared editor as you explain. Interviewers care that you can talk a JOIN, not that you paste a perfect query silently.
Interview day (Chennai office): reach early, ID, printed resume matching the portal, water, a calm 90-second case. In-person days run long. Eat. Do not schedule another company’s OA in the same afternoon “just in case.”
PORs and internships: HR may skip them (GFG DS). Technical 2 will not skip the internship SQL. If you interned in a “data” role that was actually Excel-only, say Excel and what you learned. Fake pandas is worse than honest Excel plus a JOIN you practised this month.
Stats beyond puzzles: mean vs median, what a p-value is in one sentence, why correlation is not causation on a campaign. That is enough for most Trainee Analyst cabins. Do not start a PhD defence.
After the offer: city, joining, CTC split. If two analytics offers arrive (Tiger vs Fractal/ZS), compare the team (retail analytics vs pharma case) and whether you will write SQL in week one. Title inflation is common. Ask what the first project looks like.
Keep this hub as the spine. Linked practice pages hold mocks and stories. The preparation guide holds the week calendar on purpose. Your job is SQL, one case, one city sentence. Do that until it is boring. Then the OA and the 5-minute HR are just logistics. That is the Trainee Analyst path at Tiger Analytics in 2026. Do not make it a mystery.
What not to do: start a new LLM course this week; memorise a 2019 Mu Sigma puzzle book cover to cover; apply from Delhi to a Chennai-only in-person drive and hope; list five ML models you cannot explain. Do: 10 queries, one case, city sentence.
Santa Clara vs Chennai: HQ branding is US/Chennai. Your joining is an India hub. Do not prep as if you are flying to California. Prep as if you will sit in Chennai and write SQL for a retail client. That picture is accurate enough to steer HR.
Team allocation: you may not pick retail vs CPG on day one. Saying you are curious about both is fine. Saying you will only do NLP research is how Trainee Analyst loops stall.
After rejection: reuse the SQL muscle on Fractal/ZS/EXL. The case skeleton travels. The Chennai sentence does not. Update it.
Nested drills: coding, aptitude, interview experience. Use them as timed sets, not as novels.
Kit for the cabin: city sentence, marksheets, a JOIN you can rewrite on a six-row toy table (latest order per customer), and the exam-date line if you are not an immediate joiner. Analytics consulting is not a 12-round product onsite. Do not turn it into one. SQL first, case second, city third, sleep, drive, letter. If Tiger says no, the same JOIN still opens Fractal, ZS, and EXL. Keep the muscle. Close the tab and write the query.
More: Tiger Analytics interview experience.