
Novartis Software Engineer interviews vary by track, typically starting with a recruiter or HR screen and a hiring-manager conversation, followed by technical rounds that range from verbal questions to take-home coding challenges, with post-interview communication timelines that differ widely by candidate.
$128K
Avg. Base Comp
$155K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Novartis Software Engineer interviews differ noticeably depending on the specific track - full-time, contract, or internship (Praktikum) - but the firsthand reports share a common shape: an early screening conversation, a deeper hiring-manager discussion, and then a technical or team-focused round that varies sharply in format.
The process often opens with a brief recruiter or HR conversation. One candidate described this as short as fifteen minutes and focused mainly on background and motivation; another said the HR stage was mostly an overview of what to expect rather than an evaluation. A contract-track candidate went through a recruiting agency instead, which they described as upfront and transparent about the role from the start.
From there, candidates typically meet a hiring manager for a longer, more substantive conversation. One described a roughly 35-minute discussion that pushed for concrete examples of conflict and difficult team dynamics rather than technical depth. A candidate interviewing for the Praktikum (internship) track instead had a casual conversation about role expectations and day-to-day work, followed by a presentation component and meetings with people across levels - including senior leadership - as part of what they described as a full-day process.
Technical evaluation is where accounts diverge the most. One candidate reported five separate technical interviews covering system design and problem-solving across the stack. Another said the technical portion amounted to basic verbal questions with no coding involved at all. A third completed a take-home coding challenge followed by a phone interview centered on reading and debugging a buggy program, OOP principles, and command-line basics.
Post-interview communication is the most consistent complaint. Candidates who did not receive offers described long silences after their final round - in one case, a new HR contact eventually reached out with no real feedback, and in another, a follow-up email went entirely unanswered. One candidate who accepted an offer described the process as taking roughly a couple of weeks from start to finish, with an additional wait after that before a final decision. Given how much the format and timeline vary by track, it's worth treating any single account here as one data point rather than a fixed script.
Synthesized from 8 candidate 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 Novartis process.
The interview process at Novartis for a Software Engineer role felt thorough and well-organized, at least from what I experienced. I went through five technical interviews with different team members covering various aspects of the engineering organization, which gave me a real sense of how they evaluate depth across the stack. Each interviewer brought their own focus—some zeroed in on system design, others on problem-solving approach—so by the end I had a pretty complete picture of what the role would demand. The questions themselves were solid and fair; I wasn't asked any gotchas or obscure algorithms, just substantive technical discussions that felt directly relevant to the work. One thing that did stand out negatively, though, was the communication after the rounds wrapped up. There was a long silence after my final interview, and when I finally heard back it was from a completely new HR contact with no real feedback on how the process went or where things stood. That radio silence was frustrating and made what had been a competent technical interview feel sloppy on the logistics side. The whole experience left me uncertain—the technical bar seemed reasonable and the team members I met were clearly sharp, but the lack of transparency about next steps and timeline really undermined my confidence in how the company operates.
Prep tip from this candidate
Expect five or more technical rounds with different team members diving deep into various engineering domains. Be ready to discuss system design and problem-solving across the stack, but also prepare for questions about career trajectory and long-term vision—and following your interviews, push for clear communication timelines and feedback, since the process can go silent for months.
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 Novartis
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| 2nd Highest Salary | |
| Monthly Customer Report | |
| Weighted Keys | |
| Hurdles In Data Projects | |
| Cumulative Distribution | |
| Retailer Data Warehouse | |
| Total Spent on Products | |
| P-value to a Layman | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Last Transaction | |
| Brain Cancer Treatment Outcomes | |
| Always Excited Users | |
| Sum to Zero | |
| Flatten JSON | |
| Valid Anagram | |
| 85% vs 82% | |
| Cumulative Reset | |
| Rider Discount | |
| Digit Accumulator | |
| Multi-Reaction | |
| Time Difference | |
| Search Linked List | |
| Common Prefix | |
| Greatest Common Denominator | |
| Count Transactions | |
| Subscription Retention | |
| Possible Triangles | |
| Concurrent LLM Serving |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates describe an initial recruiter or HR conversation. One candidate said this stage ran about fifteen minutes and focused on background and interest in the role; another described the HR round as mostly an overview of what to expect rather than a real evaluation. A candidate interviewing for a contract role went through a recruiting agency instead, which they said was upfront and transparent about the position from the start. This stage generally does not involve technical questions.
A hiring-manager round typically follows; one candidate said theirs lasted around thirty-five minutes. That candidate said the conversation pushed for concrete examples of conflict and difficult team dynamics rather than technical depth, with the interviewer focused on judgment and problem-solving. A candidate on the internship (Praktikum) track instead described a casual discussion about role expectations and day-to-day work, including follow-up questions about what they'd do differently on a past project. Expect questions about your resume and specific past experiences rather than coding.
Technical content differs sharply across reports. One candidate went through five separate technical interviews with different team members, covering system design and problem-solving across the stack. Another said the technical portion consisted only of basic verbal questions with no coding at all. A third, interviewing for a contract role, completed a take-home coding challenge at their own pace, followed by a phone interview that included spotting the bug in a program, questions on OOP principles, command-line basics, and how to define arrays. Prepare for either a light verbal check or a deeper, multi-round technical loop depending on the role.
Later stages can involve meeting several people. One candidate's final round lasted about forty-five minutes and included one-on-one and small-group conversations with multiple team members, with pharmaceutical industry context such as regulatory considerations coming up during the process. The internship (Praktikum) candidate described a full-day process that included meetings with people at different levels, including senior leadership, along with a presentation component. These rounds tend to focus on collaborative style and cultural fit rather than additional technical testing.
Outcomes and communication after interviews differ noticeably. One candidate who accepted an offer said the process took roughly a couple of weeks from start to finish, with an additional wait before a final decision. Candidates who did not receive offers reported long silences afterward - in one case a new HR contact eventually reached out with no real feedback, and in another, a follow-up email went completely unanswered after three rounds. It's worth asking interviewers directly for an expected timeline and following up proactively if you don't hear back.