Janssen Data Analyst interview typically runs 2 rounds: HR screening and technical interview. It usually takes about 1-2 weeks and is time-limited, with little recruiter support during the technical stage.
$87K
Avg. Base Comp
$94K
Avg. Total Comp
2
Typical Rounds
1-2 weeks
Process Length
Our candidates report that Janssen is looking for someone who can move comfortably between analytics and product thinking, but the real separator is how cleanly you reason under pressure. The technical screen was described as time-limited and unsupportive, which means the interviewers seem to care less about polished storytelling and more about whether you can produce a correct, defensible answer quickly. One candidate’s month-over-month expense problem is a good example: the winning approach was to aggregate early and explicitly handle edge cases like clients with only one month of data. That tells us they are watching for whether you can spot the hidden traps, not just write working SQL.
A recurring theme is that Janssen wants practical judgment, not textbook recitation. Multiple candidates reported questions on complex joins, window functions, and working across three to four tables, plus model-selection logic and dashboard design principles. That combination suggests they value analysts who can connect data modeling, metric design, and business presentation in one conversation. We’ve also seen that the HR conversation tends to be straightforward, so the harder signal comes later: can you explain why a model fits, why a dashboard is structured a certain way, and where the data could mislead you? In this process, precision with edge cases and a clear rationale for your choices matter more than broad familiarity.
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 Janssen process.
Interview with HR went well. They asked basic questions about motivation and a few behavioral questions. The technical interview was challenging because it was time-limited and there was no help from the recruiter during the interview.
Questions asked: Practice timed SQL and analytics screening questions before this process. Specific questions from the technical screening included:
A concrete SQL example was to calculate month-over-month user expenses while handling the main edge cases. The key parts of a valid answer were to aggregate at the beginning and make sure to handle clients with only one month available through the WHERE clause.
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 Janssen
Write a query to show the number of users, transactions, and total order amount per month in 2020
| Question | |
|---|---|
| Merchant Dashboard Design | |
| Optimize Model Performance | |
| 2nd Highest Salary | |
| Last Transaction | |
| Cumulative Distribution | |
| Brain Cancer Treatment Outcomes | |
| Total Spent on Products | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Reducing Error Margin | |
| Fair Coin | |
| Causal Email Journey | |
| Greatest Common Denominator | |
| Random Forest Explanation | |
| Subscription Retention | |
| Always Excited Users | |
| Secret Wins | |
| Missing Housing Data | |
| Flatten JSON | |
| Cumulative Reset | |
| Rider Discount | |
| Digit Accumulator | |
| 85% vs 82% | |
| Time Difference | |
| Count Transactions | |
| Data Preparation for Imbalanced Data | |
| Possible Triangles | |
| String Palindromes | |
| Mapping Nicknames |
Synthesized from candidate reports. Individual experiences may vary.
The process began with an HR conversation that went well and focused on motivation for the Data Analyst role, along with a few standard behavioral questions. This stage appeared to be an early fit check before moving into the technical assessment.
The main interview was a time-limited technical screen with no recruiter help during the session, making pacing important. It covered SQL with complex joins, window functions, and queries across three to four tables, plus a month-over-month user expenses problem that required careful handling of edge cases such as clients with only one month of data.
Within the technical interview, the interviewer also asked machine learning questions about how to choose an appropriate model and how to optimize it. The candidate was expected to explain the logic behind model selection rather than just naming algorithms.
The technical round also included questions about dashboard design principles. This portion tested how the candidate would structure analytics outputs for stakeholders and think about clarity, usability, and practical reporting needs.