Internetbrands Business Analyst Interview: Questions, Experience & Prep (2026)

Internetbrands runs a network of digital properties across health, legal, automotive, and other verticals, making money primarily through lead generation and display advertising. Business Analyst roles there sit at the intersection of web analytics, product, and business strategy. Internetbrands currently has 56 open roles on knok's jobradar (as of July 2026), a sign of active hiring across teams. Candidates typically report a process of two to three stages: an HR screening call, a technical or case-study round, and one or two stakeholder interviews. Expect practical questions grounded in traffic analysis, conversion metrics, and stakeholder communication rather than abstract puzzles.

Questions candidates report seeing most often at Internetbrands BA interviews:

1. Walk me through how you would diagnose a sudden drop in traffic on one of our web properties.
2. Write a SQL query to find the top five pages by unique visitors for a given period.
3. How do you prioritise competing requests from multiple stakeholders with different goals?
4. Describe your experience with A/B testing. How do you judge when a test result is ready to act on?
5. How do you turn a vague business problem into a clear data question?
6. Tell me about a dashboard or report you built that directly influenced a business decision.
7. How would you evaluate the performance of a new content vertical on a health or legal site?
8. What KPIs would you track for a lead-generation business like the one Internetbrands runs?
9. Describe a time your analysis was challenged by a stakeholder. How did you respond?
10. How do you handle ambiguous or incomplete requirements from a product team?
11. Which data visualisation tools have you used, and how do you choose the right chart for a given audience?
12. How would you estimate the revenue impact of a conversion-rate improvement on a landing page?

Q: Walk me through how you would diagnose a sudden drop in traffic on one of our web properties.

*Situation:* At a previous company, organic traffic to our main content hub dropped noticeably over a single weekend.

*Task:* I was asked to identify the cause and present a recovery plan to the SEO and product teams within a week.

*Action:* I segmented the drop by channel, device type, geography, and landing page to isolate where it was concentrated. I then cross-referenced the timing with known Google algorithm update announcements and checked Search Console for any manual action notices. The data pointed to a cluster of pages that had lost featured-snippet positions after an update targeting thin content.

*Result:* We prioritised rewriting those pages with deeper, better-sourced content. Traffic to the affected pages recovered over the following weeks, and the team adopted a monthly content-depth audit as a standing process.

---

Q: Tell me about a dashboard or report you built that directly changed a business decision.

*Situation:* Our marketing team was spending budget across several paid channels but had no unified view of cost per qualified lead by channel.

*Task:* I was asked to build a report that would help the team decide where to cut spend and where to invest more.

*Action:* I pulled data from the CRM and ad platforms into a single SQL-based model, then built a dashboard showing cost per lead, lead-to-close rate, and revenue contribution by channel. I added a trend view so the team could see how channel efficiency was shifting over time.

*Result:* The team shifted budget away from channels with high cost and low close rates. The head of marketing cited the report in the next quarterly review as the basis for the reallocation decision.

---

Q: Describe a time your data analysis was challenged by a stakeholder. How did you handle it?

*Situation:* I had presented findings suggesting a particular product feature had low engagement and was a candidate for deprioritisation. The product manager strongly disagreed.

*Task:* I needed to either defend my analysis or identify where I might have missed something.

*Action:* Instead of digging in, I invited the PM to walk through the data with me and asked them to point to any segment or time window where they expected different results. This revealed that they were looking at a specific user cohort I had averaged into the broader population. I recut the analysis by that cohort.

*Result:* The PM's intuition turned out to be partially right: the feature had strong engagement among that specific segment. We agreed on a more targeted recommendation rather than a blanket deprioritisation, which both teams felt good about.

STAR for behavioural questions. Structure every 'tell me about a time' answer as Situation, Task, Action, Result. Keep Situation and Task brief (a sentence or two combined). Spend most of your time on Action, since that is where interviewers assess your actual thinking. End with a concrete Result, not a vague positive outcome.

Issue tree for analytical questions. When asked to diagnose a problem (falling traffic, declining conversion, rising churn), break it into branches before diving in. For a traffic drop: is it all channels or one? All pages or a cluster? All devices or mobile only? Showing this structure signals disciplined thinking before you commit to a hypothesis.

Hypothesis-first for open-ended business questions. State your hypothesis upfront, then walk through how you would test it. For example: 'My first hypothesis is that the drop is algorithm-related rather than a technical issue, and here is how I would confirm or rule that out.' This mirrors how senior analysts actually work.

Metric pyramid for KPI questions. Start with the north-star metric (revenue, leads, engagement), then show the levers that drive it, then the diagnostic metrics that tell you which lever is moving. This prevents you from listing metrics randomly and shows you understand causality.

Internetbrands interviewers are typically looking for a few things beyond technical correctness.

Business context awareness. They want to see that you understand the lead-generation and content business model, not just generic analytics. Frame your answers around metrics like cost per lead, content engagement, and conversion rather than abstract KPIs.

SQL comfort. Candidates report that SQL comes up in almost every technical round. You do not need to be a data engineer, but you should be able to write joins, window functions, and aggregations comfortably and talk through your logic as you write.

Stakeholder communication. Because BA roles at media companies sit between product, marketing, and engineering, interviewers watch for how you handle disagreement and how clearly you explain data to non-technical audiences. Show moments in your answers where you adapted your communication style.

Structured thinking. More than memorised answers, they want to see a clear process. When a question is ambiguous, candidates who pause to state assumptions out loud consistently report a better experience than those who jump straight to a conclusion.

Understand the business first. Spend time on Internetbrands' main properties across health, legal, and automotive verticals. Understand how they make money: lead generation and advertising are the core models. Think about what metrics matter most in each model before your interview.

Refresh your SQL. Practice writing queries for common BA tasks: aggregations by segment, ranking with window functions, joining multiple tables, and calculating period-over-period changes. Focus on clarity and commenting your logic, not just getting the right answer.

Build a story bank. Write out four to five STAR stories covering: a time you diagnosed a data problem, a time you influenced a decision, a time you handled a difficult stakeholder, and a time you worked with ambiguous requirements. Practice saying each one out loud in a few minutes.

Prepare a few good questions. Strong questions focus on the team's current data stack, how BA work feeds into product decisions, and what the biggest analytical challenges are right now. Avoid questions whose answers are clearly on the company website.

On the day, go slow on case questions. Interviewers report that candidates who pause, state assumptions, and structure their answer before diving in perform noticeably better than those who rush straight to a conclusion.

If you want to track new BA openings at Internetbrands without manually checking boards every day, knok checks 150+ job sites nightly, applies to jobs that match your resume, and messages HR for you.

Skipping the business model check. Many candidates prepare generic BA answers without learning how Internetbrands actually makes money. Answers that reference metrics irrelevant to a content and lead-gen business signal a lack of preparation.

Writing SQL without explaining it. In a technical round, narrating your query as you write it matters as much as the correct output. Silence while you type can read as low confidence.

Vague results in STAR answers. Saying 'the stakeholders were happy' or 'the project went well' is not a result. Push yourself to describe a concrete change in decision or behaviour, even when you cannot share specific numbers.

Listing tools instead of showing thinking. When asked about your analytics experience, leading with 'I used Tableau and SQL' without explaining what decision the work supported misses the point. Lead with the business question, then bring in the tools.

Not asking clarifying questions on ambiguous problems. If an interview question is open-ended, jumping straight to an answer without checking your assumptions reads as sloppy rather than fast. A brief 'can I confirm a couple of assumptions?' sets you apart.

Treating the interview as one-directional. Candidates report that Internetbrands interviewers respond well to genuine curiosity about the team and the data problems they are solving. An interview where you ask nothing often leaves a flat impression.