Johnson & Johnson Software Engineer Interview Guide

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.