Tiger Analytics Business Analyst interview typically runs 1 round: structured screening. Timeline is about 1 interview; the process is practical, business-focused, and scenario-driven.
$101K
Avg. Base Comp
$155K
Avg. Total Comp
4 rounds
Typical Rounds
1-2 weeks
Process Length
We've seen Tiger Analytics lean hard into applied business thinking rather than abstract theory. In the candidate experience we reviewed, the interviewer set expectations clearly and then moved through Tableau, SQL, prioritization, and scenario work in a way that felt deliberately grounded in day-to-day consulting decisions. The SQL prompts were basic on the surface — HAVING vs. WHERE, JOINs — but the real signal was whether the candidate could explain the why behind the tool choice. The same pattern showed up in Tableau, where the dual-axis question was less about memorizing chart types and more about knowing when a visualization supports a business story.
A recurring theme is that Tiger Analytics seems to value candidates who can triage messy stakeholder situations without losing the commercial thread. The overseas credit card conflict scenario, the pushback from legal and security, and the backlog-in-JIRA question all point to the same expectation: can you make sensible tradeoffs when priorities collide? We also noticed a finance-heavy case around a new credit card launch, complete with fee, APR, usage, and profitability assumptions. That tells us the bar is not just analytical comfort, but the ability to reason through revenue, cost, and adoption in a consulting-style conversation. Candidates who come across as structured, practical, and comfortable defending assumptions seem best aligned with what Tiger Analytics is actually testing.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Tiger Analytics process.
I went into the Tiger Analytics Business Analyst interview expecting a standard screening, but the actual conversation was more structured and practical than I thought. The interviewer first laid out the areas he would cover, which made the round feel pretty straightforward once it started. A big part of it was around Tableau, SQL, behavioral judgment, and scenario-based problem solving, with a few agile questions mixed in. The Tableau question that stood out was why you would use a dual-axis chart, and on the SQL side I was asked the difference between HAVING and WHERE, along with basic JOIN concepts. Those were not overly hard, but they did test whether you really understand the tools rather than just recognize the terms.
The behavioral part was more interesting because it was tied to prioritization. I was asked how I choose between multiple high-priority tasks, and then given a BA scenario involving overseas credit card payment conflicts where several issues were happening at once and I had to explain how I would decide what to handle first. There was also a product-style question where I had to think like a product manager and explain how I would deal with pushback from legal and security after getting approval from product and data engineering. The most involved case was a banking profitability problem: a new credit card with a $90 annual fee, 10% APR, and transaction costs split between vendor cost and bank revenue, with assumptions about a 1 lakh sample population and only 80% usage. I had to reason through whether the bank should launch it nationwide and estimate the average transaction value needed for profitability. On top of that, there were agile questions about managing a backlog in JIRA and handling an urgent stakeholder request during a sprint. Overall it felt fair and business-focused, not algorithm-heavy, but you do need to be comfortable thinking on your feet with numbers, prioritization, and product tradeoffs. I did not get the offer, so my main takeaway is to prepare for practical finance cases, SQL basics, and clear prioritization frameworks rather than memorizing textbook answers.
Prep tip from this candidate
Be ready to explain HAVING vs WHERE, common JOINs, and why you’d use a dual-axis chart in Tableau. Also practice a profitability case with card fees/APR/transaction costs and a prioritization framework for conflicting stakeholder requests in a sprint.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Tiger Analytics
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| New Partner Card | |
| Target Indices | |
| Assumptions of Linear Regression | |
| String Palindromes | |
| Count Transactions | |
| Area Under the ROC Curve | |
| Generative AI Privacy | |
| Empty Neighborhoods | |
| Employee Salaries | |
| 500 Cards | |
| Button AB Test | |
| Top Three Salaries | |
| First Touch Attribution | |
| Largest Salary by Department | |
| Top 3 Users | |
| P-value to a Layman | |
| Minimum Change | |
| Jars and Coins | |
| Size of Joins | |
| Same Side Probability | |
| Top 5 Turnover Risk | |
| Complete Addresses | |
| Hurdles In Data Projects | |
| Last Transaction | |
| Fair Coin | |
| Sort Strings |
Synthesized from candidate reports. Individual experiences may vary.
The first conversation appears to be a structured screening where the interviewer outlines the topics to be covered up front. For this Business Analyst role at Tiger Analytics, the screen quickly moves into practical evaluation rather than broad introductions.
This round focuses on hands-on skills in Tableau, SQL, and business analysis. Candidates can expect questions like dual-axis charts in Tableau, HAVING vs WHERE, basic JOINs, and scenario-based problem solving tied to prioritization, agile/JIRA workflows, and stakeholder management.
A major part of the interview is a practical case that tests quantitative reasoning and business judgment. In the shared experience, this included a banking profitability case for a new credit card product, where the candidate had to assess launch viability and estimate transaction values needed for profitability.
After the interview round, the company communicates the outcome. Based on the experience shared, the process concluded without an offer.