Johnson & Johnson Software Engineer interview typically runs 3-5 rounds: recruiter screen, behavioral recordings, technical/video interview, presentation, manager or leadership round. It usually takes a few months and is structured but can have long gaps between stages.
$135K
Avg. Base Comp
$172K
Avg. Total Comp
4-6
Typical Rounds
2-4 months
Process Length
Our candidates consistently describe Johnson & Johnson as more polished than punishing: the questions are rarely framed as traps, but they do expect you to be crisp, organized, and easy to follow. A recurring theme is that the team wants to see how you explain your work, not just whether you can produce an answer. That shows up in project walkthroughs, background-heavy conversations, and even casual openers that quickly shift into evaluating whether your story is coherent and credible.
We’ve also seen that the technical bar is selective in a very specific way. It’s not usually about exotic algorithms, but it does include standard coding problems like Three Sum, implementation details in C++, and, in some cases, a real system design discussion such as an LRU cache. The non-obvious part is that they seem to care as much about tradeoffs and reasoning as the final solution. Candidates who could talk through data structures, edge cases, and why they made a choice tended to come away feeling better about the process.
The behavioral side is just as important, and multiple candidates noted that it can feel surprisingly central even for a software engineering role. We’ve seen repeated prompts around challenges, strengths and weaknesses, and where you see yourself in the future, which suggests they’re screening for maturity and team fit alongside technical competence. In practice, the candidates who did best were the ones with a polished narrative, calm delivery, and enough confidence to handle follow-up questions without sounding rehearsed.
Synthetized from 3 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 Johnson & Johnson process.
The process felt pretty straightforward overall, though it dragged on longer than I expected. I first had to submit short behavioral recordings, each around 30 seconds, and I got three tries for each response. After that, there was a long gap where I didn’t hear anything for a few months, which was honestly the most frustrating part. Eventually I moved on to a one-hour video interview with two team members, and that was the main technical round I experienced.
The interview itself was a mix of coding and discussion. I was asked a Three Sum problem and then some follow-up questions around C++ code, so it wasn’t just about getting to a working solution but also understanding the implementation details. Earlier in the process, there was also a resume screen and a project presentation round where I walked through the work I had done, and the broader process seemed to include a coding round with DSA and Python as well as a behavioral and managerial round. The questions were not especially hard, but they did expect you to explain your thinking clearly. One of the more basic questions I got was a simple “How are you this fine morning?”, which matched the very casual tone of the early screening. I ended up not getting an offer, and the whole experience felt simple and direct rather than deeply technical. If I were preparing again, I’d make sure I could explain my projects clearly, solve a standard Three Sum-style problem cleanly, and talk through C++ code without getting flustered.
Prep tip from this candidate
Be ready to present your projects clearly, since that came up as its own round, and practice a clean Three Sum solution with follow-up discussion on C++ code. The process also included short behavioral video responses, so rehearse concise answers you can deliver in about 30 seconds.
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 Johnson & Johnson
For each cancer type, compute total patients, percentage surviving at least 12 months, and average treatments per patient
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Hurdles In Data Projects | |
| Last Transaction | |
| Always Excited Users | |
| Total Spent on Products | |
| Sum to Zero | |
| Valid Anagram | |
| Flatten JSON | |
| Cumulative Reset | |
| Search Linked List | |
| Time Difference | |
| Impute Median | |
| Common Prefix | |
| Greatest Common Denominator | |
| Subscription Retention | |
| Possible Triangles | |
| String Palindromes | |
| Moving Window | |
| Second Longest Flight | |
| Digit Accumulator | |
| Multi-Reaction | |
| Count Transactions | |
| Uber Eats Customer Experience | |
| K Nearest Entries | |
| Stakeholder Communication |
Synthesized from candidate reports. Individual experiences may vary.
A first conversation with recruiting to review your background, experience, and fit for the role. Candidates described it as straightforward and mostly focused on their resume and general experience.
Some candidates were asked to submit short recorded behavioral responses, with about 30 seconds per answer and multiple tries allowed. This stage was casual and focused on basic self-introduction and communication style.
A hiring manager or team lead conversation that digs into your background and, in some cases, C++ or system design fundamentals. One candidate was asked to design an LRU cache and explain the tradeoffs, while others saw more background- and fit-focused questions.
A live coding interview with one or two engineers that includes LeetCode-style problems and implementation discussion. Examples included Three Sum, DSA/Python coding, and follow-up questions about C++ code and problem-solving approach.
Candidates presented past work and answered questions about their projects, followed by discussion and sometimes additional coding. This round emphasized clear communication, explaining technical decisions, and walking through your experience.
A final conversation with leadership or senior stakeholders focused on behavioral and scenario-based questions. Topics included strengths and weaknesses, handling challenges, difficult situations at work, and where you see yourself in the future.