Academic snapshot
Marks: 7.0+ / 70% common; some 8.0+
Degree: B.E./B.Tech; MSc/MA Eco/Stats on some lists
Backlogs: None active preferred
Year: Final-year and recent grads
Fractal Analytics Placement Papers 2026
Fractal is an AI and analytics consulting firm that helps Fortune 500 companies build data science and decision intelligence systems. Founded in 2000, it hires engineers and data scientists across Mumbai, Bengaluru, and Gurugram to deliver analytics products for global clients.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Fractal Analytics in 2026?
Who this hub is for
- For: Students targeting Imagineer and early-career analytics / data-science seats at Fractal.
- Not the same track: Experienced AI-architect loops, sales-only, or “fully remote 0 YOE” spam. This hub is the campus 90-minute OA + case/SQL + business round.
- Two flavours: Engineering (CS/IT/ECE with Python/SQL) vs Eco/Stats (MSc/MA on some Imagineer lists). Both still need structured problem-solving. Do not mix prep blindly.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA, PPT, sometimes 8.0+ floor | SQL + case bar |
| fractal.ai / referral | Resume volume; GFG-style multi-stage OA | Same business round |
| Referral drives | Visibility | You still sit the test |
Off-campus does not mean easier JOINs. It often means more applicants who only prepared CAT quant.
Degree, projects, and “is 7.0 enough?”
Is 7.0 CGPA enough? It matches the commonly reported preferred floor (or 70% throughout). A VIT campus GFG account for Imagineer 2026 cited 8.0+ for that drive. Selection still hinges on SQL/Python and a case you can narrate. A 7.1 who can write a window function and structure a metric beats an 8.8 who only memorised aptitude keys.
Branches: Circuit (CS/IT/ECE/EEE/AI) commonly. MSc/MA Economics or Statistics on some Imagineer notices.
What helps the resume screen: A project with a business metric (conversion, churn, forecast error), a Kaggle/internship you can defend without a notebook. See certifications after SQL depth, not as a substitute. A random Tableau badge without a JOIN story is thin.
Skills they actually filter
OA: Quants, logical, SQL, Python
Interview: Case + stats + project
Soft filter: Business storytelling
Exam filter: Fractal Online Assessment
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| Graduation | 7.0+ / 70% often; 8.0+ on some campus JDs | Read the mailer |
| Throughout | 10th/12th listed on some notices | Keep marksheets |
| Branch | Circuit; Eco/Stats on some Imagineer | Not “any branch” |
| Backlogs | None active | Clear before joining |
| Languages | Python, SQL; R sometimes | Whiteboard joins |
Fractal shortlists on academics when the JD prints a floor, then filters on SQL you can write and a case you can structure. Clearing CGPA only gets you into the OA. The pre-onboarding weeks after selection are a second gate.
Who usually fits and who struggles
Good fit: You like messy business questions, you can write a JOIN without Stack Overflow, and you can explain a chart in two minutes. Consulting-analytics culture means they care whether a client would trust your caveat.
Harder path: You only practiced LeetCode hard; you cannot write GROUP BY; you freeze when asked “so what should the VP do?” A high CGPA with zero SQL usually dies in OA. A mid CGPA with clean SQL and one honest case often survives.
Branch myth: Eco/Stats students are not auto-rejected on listed Imagineer drives. They also are not waved through if Python is missing. CS students are not safe if they cannot talk a metric.
Gap years and backlogs: zero active backlogs is the usual campus rule. Plan to clear everything before joining, including before long pre-onboarding if that is your drive.
Fractal Analytics previous year papers & PDFs
Download 2026 Fractal Analytics placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Fractal Analytics previous year papers actually train
Fractal does not publish a permanent official paper set. “Previous year papers” on this site are pattern trainers for the 90-minute OA and case interviews, not leaked live papers.
| Round (typical) | What to practice |
|---|---|
| OA | Quants, logical, SQL, Python |
| Technical | Stats, SQL, Python/DSA, projects |
| Business / Apex | Structured case, so-what, caveats |
| HR | Why Fractal, city, training gate |
Think of papers as simulators for 90-minute stamina. Fractal reuses themes (DI, probability, joins, pandas-style Python, business cases) more than exact clones.
Themes that keep repeating (2024-2026)
- OA: Referral/job posts describe ~90 minutes covering quants, logical, SQL, Python coding. Off-campus GFG accounts sometimes split aptitude then coding+tech MCQ.
- Tech interviews: Projects, statistics, SQL, Python; FaceCode/HackerEarth coding in one off-campus account.
- Business understanding / Apex: “What would you tell the client?” more than “implement Dijkstra.”
- After selection: ~10-12 weeks pre-onboarding before LOI/final offer in multiple GFG reports (VIT campus 2026 and an off-campus Imagineer account).
How to use one paper set in a single sitting
- Timed: 90 minutes mixing aptitude, 4-6 SQL, 1-2 Python tasks.
- Untimed review: rewrite every JOIN you guessed; draw the tables.
- 8-minute case: pick a metric, hypothesis, data, caveat. Speak it.
- Map misses (probability vs window functions vs pandas).
- Log one STAR (messy data, a wrong dashboard, a stakeholder pushback).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Fractal asks it |
|---|---|---|
| Percentages / DI | Mix with a business story | OA + case |
| Probability / Bayes lite | Conditional wording | Stats interviews |
| SQL joins | Window functions, NULL traps | Imagineer daily work |
| Python | pandas groupby, a light DSA | OA coding |
| Case | One metric, one caveat | Apex / business round |
2025 PDFs often drill a simple JOIN. Own why a LEFT JOIN drops rows when you filter in WHERE vs ON, not memorising syntax.
From application to offer at Fractal Analytics
Fractal hires Imagineers through campus cells, fractal.ai, and referral drives. After resume screen, the shape is analytics: a timed OA, technicals that mix code and stats, then a business-understanding round.
Application methods
Campus recruitment
PPT, OA, two technicals sometimes, HR. VIT 2026 GFG: PPT → OA → Tech1 → Tech2 → HR.
Online / referral
fractal.ai or referral posts; follow the invite for OA vendor and duration.
Off-campus GFG pattern
Aptitude → coding+MCQ → tech → business understanding → HR in one public account.
1. Resume / eligibility
Degree, CGPA (7.0+ or the higher campus floor), branch or Eco/Stats, backlogs. Put one analytics project with a number on the first page.
2. Fractal Online Assessment (~90 min)
Referral/job posts: ~90-minute test covering quants, logical, SQL, Python. Off-campus GFG: separate aptitude then coding+tech MCQ stages.
| Section (typical) | What shows up | Pass habit |
|---|---|---|
| Aptitude / logical | Quant, DI, arrangements | 45-second skip |
| SQL | Joins, aggregates, filters | Draw tables first |
| Python | pandas-level or light DSA | Edge cases |
Deeper OA notes: Fractal Online Assessment.
SQL / Python flavour
SQL (illustrative): customers/orders JOIN, revenue by month, a NULL trap, a window function (ROW_NUMBER, running total) at fresher depth.
Python (illustrative): groupby/agg, a simple array problem, string cleanup, a light DSA (frequency map) if the vendor leans coding.
You will not memorise 200 queries. You will write 30 by hand until joins are boring.
3. Technical interviews
Projects, statistics (mean vs median, bias, a simple hypothesis test in words), SQL on a whiteboard, Python/DSA. One off-campus account mentioned FaceCode/HackerEarth. They will ask “why this metric?” as often as “write the query.”
Worked mini-outline - a churn case (8 minutes):
- Metric: monthly churn rate, define numerator/denominator.
- Hypothesis: onboarding drop-off vs price vs product bug.
- Data: signup date, last active, plan, tickets.
- Caveat: seasonality; do not treat a 2-week spike as strategy.
- Next step: one analysis you would run in week one. Stop.
4. Managerial / Apex / business understanding
This is Fractal’s differentiator versus a pure SDE loop. Can you talk to a business problem without drowning in jargon? Structure beats buzzwords. “AI will solve it” is a fail.
5. HR
Why Fractal (AI + decision systems for Fortune clients, in your own words), Mumbai / Bengaluru / Gurugram, and the pre-onboarding reality (~10-12 weeks in recent GFG reports). Ask what the training gate means for your joining date and stipend vs CTC. Full HR banks: HR interview questions.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA | ~90 min | Aptitude + SQL + Python |
| 2 | Technical | 30-45 min each | Stats, code, project |
| 3 | Business / Apex | 20-40 min | Case structure |
| 4 | HR | 15-25 min | City, training, fit |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week |
| OA | 1 day | ~90 min or split |
| Interviews | Days to 2 weeks | Tech + business |
| Selection | Days | Not always a joining letter yet |
| Pre-onboarding | ~10-12 weeks in GFG reports | Training gate |
| Offer / joining | After training on many drives | Ask HR the rule |
Test pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude | Skip rules | mock quiz |
| SQL | Joins + windows | 5 queries/day by hand |
| Python | pandas + light DSA | coding questions |
| Case | 8-minute structure | One case/day spoken |
| HR | City + training | Two STAR + Why Fractal |
Ninety-minute clock you can reuse
| Minute | Move |
|---|---|
| 0-5 | Skim sections. Confirm lock and negative marking. |
| 5-30 | Aptitude: bank easy DI; skip after 45 seconds. |
| 30-60 | SQL: draw tables; write joins; leave window functions if short. |
| 60-85 | Python: working code over clever code. |
| 85-90 | Recheck NULL filters and off-by-ones. |
If the drive is split (aptitude day, coding day), do not steal sleep to cram a new topic between them. Review the error log only.
Pre-onboarding - treat it as a round
GFG VIT Chennai Imagineer 2026: selected, then required ~12-week pre-onboarding before final offer/joining. Off-campus Imagineer GFG: 10-11 weeks before LOI/offer. Plan internships and other offers around that calendar. Ask what happens if you fail a checkpoint. Do not celebrate PPT selection as a joining letter.
Sample technical follow-ups
- Write a JOIN; then add a filter that accidentally drops unmatched rows.
- Mean vs median when the VP looks at “average order value.”
- What is a window function in one sentence.
- How you would check if a campaign lifted conversion (simple before/after + one caveat).
- Your project: what would you measure on day two.
- Python: why a copy vs a view in pandas can bite you (fresher depth).
What to carry on campus day
- ID + college ID
- Resume with one metric
- A calm 60-second Why Fractal
- City yes/no (Mumbai, Bengaluru, Gurugram)
- Awareness that training weeks may follow selection
Leave the 400-page ML book in the bag. They ask you to structure, not to quote a transformer paper.
Sql pack - what “by hand” means
Write these until they are boring. No notebook autocomplete.
- Inner join customers to orders; revenue by month.
- Left join; then a
WHEREon the right table that accidentally drops unmatched rows. Fix it (ONvsWHERE). GROUP BYwith aHAVINGfilter.ROW_NUMBER()to pick latest order per customer.- Running total with a window (
SUM() OVER). - NULL vs empty string in a filter.
- A duplicate-customer cleanup (
DISTINCTvs window). - A date grain mistake (day vs month) and how you would catch it.
If you cannot draw the two tables before writing the JOIN, you will fail the OA and the whiteboard.
Python pack (pandas-level plus one dsa)
groupby+aggon a sales frame- merge two frames (same JOIN traps)
- fill vs drop NA; when each lies
- a frequency map / two-sum style problem if the vendor leans DSA
- one string cleanup (strip, lower, split)
- why a SettingWithCopy warning exists (fresher depth)
Imagineer work is closer to “clean this table and compute a metric” than “implement Dijkstra from scratch.” Still, a light DSA problem on an off-campus coding stage should not surprise you.
Case library (8 minutes each)
Speak these out loud. Stop at caveat plus next step.
Retail conversion: metric, funnel step that dropped, data you would pull, seasonality caveat.
Churn: definition of churn, onboarding vs price vs product, one analysis for week one.
Campaign lift: before/after is not causal; one simple control idea; do not claim RCT if you did not run one.
Forecast miss: MAPE in one sentence; a holiday spike; what you would tell a VP.
Ops / plant (if you have that background): cycle time vs quality; one dashboard lie.
Fractal’s business/Apex round is this muscle. “I would use AI” is not a case.
Stats oral pack
- Mean vs median for AOV when one whale customer exists
- Bias vs variance in one analogy
- What a p-value is not (it is not “probability the hypothesis is true”)
- Train/test leak in one sentence
- Correlation vs causation with a silly example (ice cream and drowning)
You do not need a full inference course. You need to stop saying “significant” when you mean “the line went up.”
Pre-onboarding - what students actually report
VIT Chennai Imagineer 2026 (GfG): ~12 weeks after selection before final offer/joining. Off-campus Imagineer GfG: 10-11 weeks before LOI/offer. Ask:
- Is there a stipend?
- Can you fail a checkpoint?
- Does another offer’s joining date survive this?
- Is attendance remote or office?
Treat those weeks as a round. People who signed another company’s letter during training without reading Fractal’s rule created messy exits. Keep emails.
Six-week imagineer plan if your sql is dusty
| Week | Focus | Output |
|---|---|---|
| 1 | Joins + GROUP BY by hand | 25 queries; draw every table |
| 2 | Window functions + NULL traps | 15 queries; 2 timed 30-min sets |
| 3 | Python pandas + one DSA family | 10 notebooks without peeking |
| 4 | Aptitude speed + DI | 4 timed sets |
| 5 | Cases spoken (8 min) | 8 cases recorded |
| 6 | Full 90-min mocks + project oral | 2 mocks; error log closed |
Do not start a new deep-learning course in week 6. Close the log.
Imagineer first months (ask, do not invent)
Client analytics: messy data, a stakeholder who wants a number yesterday, a dashboard that will be screenshotted out of context. Training weeks exist because they do not assume you already know Fractal’s tools. Ask what the first project type is (marketing, supply chain, pricing). A honest “I want to learn client analytics and write SQL that does not lie” beats “I will deploy an LLM in week two.”
City pack - mumbai, bengaluru, gurugram
Write three columns: must have, can do two years, cannot do. Mumbai is HQ-adjacent in student chatter; that does not make it the only city on your letter. Hybrid norms vary. HR will ask.
What selected vs almost-selected looks like
Selected: clean SQL, a metric they can define, an 8-minute case with a caveat, awareness of 10-12 training weeks.
Almost-selected: CAT-only OA, a random-forest project with no business number, “I like data,” no idea what pre-onboarding is.
The difference is SQL plus storytelling, not a secret paper.
Negative marking and split oas
Some off-campus accounts split aptitude then coding+MCQ. Sleep between days. Do not cram a new window-function chapter at 1 a.m. If there is a penalty, blank is better than a 1-in-4 Bayes guess. Write the rule on your rough sheet.
Where to practise for Fractal Analytics
Week-by-week calendars live on the preparation guide, not here.
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.
Fractal Analytics preparation strategy that works
If a Fractal 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 Fractal Analytics sits around ₹8-14 LPA (candidate-reported - confirm the letter). Languages students mention most often: Python, C, Go, SQL. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Fractal Imagineer eligibility is drive-specific. Common reports: typically 7.0+ CGPA or 70% throughout (one VIT campus account cited 8.0+ for that drive); circuit branches CS/IT/ECE/EEE/AI and sometimes MSc/MA Economics or Statistics; no active backlogs. Always verify fractal.ai careers or your campus JD.
What you are training for: Typical Imagineer loop: resume screen → ~90-minute OA (quants, logical, SQL, Python) → technical interviews → managerial/Apex or business-understanding round → HR. Some off-campus GFG accounts split aptitude then coding+MCQ. After selection, many reports require ~10-12 weeks of pre-onboarding training before the final offer or joining.
Short version of the prep split: Split time roughly: 30% aptitude/logical, 25% SQL, 20% Python (pandas-level plus light DSA), 15% case/business storytelling, 10% HR and Why Fractal. Languages: Python, SQL, sometimes R.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Fractal 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 Fractal 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 Fractal 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 Fractal Analytics?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Fractal 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.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Fractal Analytics story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Fractal Analytics PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Fractal Analytics papers on three different days, then interview prep on the leftovers.
Fractal Analytics fresher CTC in India (2026)
Figures are candidate-reported (as of August 2026). Fractal does not publish a single Imagineer CTC PDF for every intake.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Imagineer / many analytics freshers | ₹8-14 LPA | Primary band used on this hub |
| During pre-onboarding | Stipend vs full CTC varies | Ask HR the rule |
| Experienced / specialist | Higher | Not campus default |
Confirm base, bonus, city, and when CTC starts on the written offer.
Benefits students actually care about
- Health insurance
- Learning on Fortune-client analytics work (ask what the first project actually is)
- Hybrid or office norms by Mumbai / Bengaluru / Gurugram
- Training that is real (the 10-12 week gate)
How to talk CTC in HR
Know ₹8-14 LPA as the hub’s reported band and ask what this Imagineer letter includes, including training weeks. Do not invent a number from AmbitionBox midpoints.
Offer-stage discipline
- Read location and training duration twice
- Confirm joining vs exams
- Do not resign another offer until the letter (or LOI rule) is clear
- Background check will match degree and percentages
Keep every email.
Fractal vs Mu Sigma vs ZS vs Tiger Analytics
Mu Sigma leans puzzles/problem-solving culture. ZS is more structured case + pharma/sales-ops. Tiger is analytics consulting with coding. Fractal’s Imagineer path adds a visible SQL/Python OA, a business-understanding round, and a long pre-onboarding gate. Prep aptitude + SQL for all; customise Why-company to AI/decision systems for Fractal.
Week-of-drive checklist
- Sleep; ID; resume with one metric on line one of projects
- 10 JOINs you can write from memory
- One 8-minute case you can open without notes
- City yes/no (Mumbai, Bengaluru, Gurugram)
- Pre-onboarding question list (stipend, fail rule, dates)
- Error-log only
If the OA is remote, treat it like an exam: charger, quiet, no second laptop “for Stack Overflow.” Proctoring stories are how people get voided after a good paper.
Project storytelling that survives apex
Pick one project. Write four lines:
- Business question (not “I used pandas”).
- Data grain (what is a row).
- Metric and the number you moved or would move.
- What you would redo (leak, wrong join, no baseline).
If you cannot do this, the business round will invent a project for you, badly. A college dashboard with an honest caveat beats a Kaggle gold medal you cannot explain.
Year-by-year paper notes (2024-2026)
2024-2025 packs train aptitude + SQL/Python flavour. Use them in 90-minute sittings.
2026 pages include Imagineer campus notes (VIT-style process) as maps. Pre-onboarding length in GfG write-ups is the new calendar fact seniors from 2019 may not mention.
2025 PDFs often drill a JOIN. Draw the tables and write a LEFT JOIN that does not drop unmatched customers. Reading a query dump does not survive a whiteboard.
Eco/stats students - same bar, different resume
If your Imagineer JD lists MSc/MA Eco or Stats, you still need Python and SQL. Your edge is metric definition and a clean caveat, not a theory dump. Do not skip the OA coding section because “I am not CS.” CS students: do not skip the case because “I will code it.”
Recent Fractal Analytics placement trends
- ~90-minute OA (or a split aptitude/coding pair) remains the first filter in public posts. Confirm your mailer.
- Imagineer pre-onboarding (~10-12 weeks) is a recurring 2025-2026 GFG detail. Budget it.
- Business / Apex rounds still separate Fractal from a pure SDE loop.
- CGPA floors vary (7.0 vs 8.0 on some campuses). Do not assume the hub’s 7.0 covers your JD.
- Treat ₹8-14 LPA as a reported band, not a guarantee.
- SQL + storytelling beat “I trained a random forest” with no business metric.
Net for 2026: pick SQL and one case habit now. A CS student grinding only LeetCode will die on JOINs. An Eco student grinding only CAT will die on Python. Process length includes training weeks; plan other offers around that.
Also expect CGPA floors to move by campus (7.0 vs 8.0). If your college finally gets an Imagineer PPT, treat it as a real shot, not a side quest. The SQL bar does not drop because the venue is new. Ask about pre-onboarding dates before you mentally spend the CTC.
Fractal Analytics placement FAQs
Process & papers
What is the Fractal Analytics placement process?
Typical Imagineer path: resume → ~90-minute OA (or split aptitude/coding) → technical interviews → business/Apex → HR. After selection, many reports require ~10-12 weeks of pre-onboarding before the final offer or joining.
How many rounds are there in Fractal Analytics interview?
Campus GFG (VIT 2026): PPT → OA → Tech1 → Tech2 → HR. Off-campus GFG: five stages including business understanding. Count the mailer.
Can I download Fractal Analytics placement papers PDF?
Yes. Free Fractal Analytics placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the paper archive.
What is the Fractal online assessment pattern?
Commonly ~90 minutes: quants, logical, SQL, Python. Some off-campus drives split aptitude then coding+MCQ. Confirm the vendor mail.
Eligibility & offer
What is Fractal Analytics eligibility criteria for freshers 2026?
Commonly 7.0+ CGPA or 70%; some campus JDs 8.0+. Circuit branches; Eco/Stats on some Imagineer lists; no active backlogs. Your notice overrides this page.
What is Fractal Analytics salary for freshers in India?
Candidate-reported CTC often lands around ₹8-14 LPA as of August 2026. Ask when CTC starts versus pre-onboarding. Cities: Mumbai, Bengaluru, Gurugram.
What is the Fractal Imagineer program?
Flagship fresher/early-career analytics program. Public reports describe multi-week pre-onboarding after selection. Treat that gate as part of the process.
Prep & Fractal-specific
How to prepare for Fractal Analytics placement?
Split time roughly 30% aptitude, 25% SQL, 20% Python, 15% case, 10% HR. Details: preparation guide.
What programming languages are allowed in Fractal Analytics?
Python and SQL are core. R on some JDs. Confirm the OA platform.
Do I have to complete pre-onboarding before the offer?
Many 2025-2026 GFG write-ups say yes (~10-12 weeks). Ask HR the rule for your drive. PPT selection is not automatically a joining letter.
Is Fractal only for CS students?
Circuit branches are common; Eco/Stats appear on some Imagineer lists. SQL + Python + case still decide. Read the JD.
Any pro tip for Fractal Analytics placement preparation?
Write SQL with joins and window functions by hand. Pair it with one 8-minute business case (metric, hypothesis, data, caveat).
Where can I read real interview experiences?
Start with Fractal interview experience (VIT 2026 GFG and off-campus Imagineer). Use them as maps, not formula sheets.
Is the Fractal test harder than a services aptitude test?
Aptitude is familiar. SQL + Python + the business round + training gate are the difference. Treat it as analytics consulting, not NQT with a logo swap.
Fractal vs Mu Sigma vs ZS vs Tiger Analytics for freshers?
All four mix aptitude with analytics interviews. Fractal’s Imagineer path adds a visible SQL/Python OA, a business-understanding round, and a long pre-onboarding gate. Customise Why-company.
What CGPA did the VIT 2026 Imagineer drive use?
That campus GfG account cited 8.0+ for that drive. Many other reports still say 7.0+ / 70%. Use your mailer, not this hub’s common floor, if they disagree.
Do I need machine learning for Imagineer?
A simple, honest metric story beats a random-forest flex with no business number. SQL, Python, and an 8-minute case are the default filters. If they ask ML, explain train/test and a leak, then stop.
Fractal Analytics - recent candidate experiences
A GeeksforGeeks on-campus Imagineer account (VIT Chennai, 2026) describes PPT → OA → Tech1 → Tech2 → HR. After selection the candidate was required to complete about 12 weeks of pre-onboarding training before the final offer/joining. Takeaway: campus “selected” is not the same as a joining letter.
An off-campus Imagineer GFG write-up describes 5 rounds: aptitude → coding+MCQ → tech (Python/DSA/projects) → business understanding → HR, then 10-11 weeks of pre-onboarding before LOI/offer. Takeaway: off-campus adds a business round you should practice out loud, and the training gate still applies.
What to steal this week
Steal: 90-minute SQL+Python stamina; one 8-minute case; calendar space for 10-12 training weeks.
Ignore: treating Fractal like a LeetCode-only SDE drive; assuming 7.0 covers an 8.0 campus JD; celebrating PPT selection as CTC.
If you only do three things: write 10 JOINs by hand, speak one case, and ask what pre-onboarding means on your mailer.
More narratives: Fractal interview experience.
What a 90-minute oa feels like (composite)
Students who cleared describe banking easy DI, drawing JOIN tables before typing, and leaving a hard window-function if time was gone. Students who failed often treated SQL as “I’ll guess the keyword” and spent the Python block on a clever one-liner that failed a null. Takeaway: working joins beat clever code.
Business round composite
A recurring fail is a 15-minute ML lecture when the prompt was “why did conversion drop.” Structure: metric, two hypotheses, data, caveat, next step. Eight minutes. If you do not know the industry, say so and reason from the metric. Interviewers prefer a clean boundary to a fake CPG expert.
Training-gate composite
Both GfG stories (campus 2026 and off-campus) put 10-12 weeks between “selected” and a joining-grade letter. Steal the calendar, not the exact week count. Ask HR. Plan other offers around the answer you get in writing.
If you’re also targeting…
Tiger Analytics · Mu Sigma · ZS Associates · EXL · Optum