Real, anonymous reports from people who interviewed for Software Engineer at Smith+Nephew, newest first and distilled into what to expect across the loop.
Get your personalized Smith+Nephew Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After the recruiter outreach, they sent me a HireVue for the first step. Not long after, I got pulled into a live video interview track where I had two back-to-back sessions scheduled across consecutive days. The questions felt mostly based on my resume, with a few curveballs that weren’t exactly coding-focused—things like whether I understood certain niche acronyms and whether I’d had any exposure to systems architecture while studying.
Overall, the difficulty felt average and the process was fairly straightforward. I remember the timeline moving quickly enough once it started, and then waiting to hear back after the final interview. I ended up getting a response within about a week after my last round, and the experience felt like a professional but somewhat generic screen of my background rather than a deep technical dive.
9 months ago
Average Positive Austin, TX
My interview path felt clean and organized. First there was a HireVue on demand step, and then I moved to a video chat with my potential boss. The final stage was in-person if I got selected, and I did.
What stood out most was how relaxed the whole experience felt—everyone I talked to came across as friendly, and the process didn’t drag. It had the rhythm of a standard progression from asynchronous screening into live conversations, and then the final meeting after that. By the end, I felt like the evaluation was straightforward, not overly combative, and it matched the general tone of the people I met.
10 months ago
Average Positive United States
The hardest part of my experience wasn’t the interviews themselves—it was waiting. They took a long time to respond to me, and the full process stretc…
12 months ago
Average Negative United States
My experience felt rough from the start. The initial interview was a one-way recording, the kind where you watch someone ask a question and then you a…
> 1 year
Average Neutral Andover, MA
My process started with a manager discussion where I walked through the projects listed on my resume. After that, I had another interview with a senio…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Process Structure
Candidates typically start with a HireVue or phone screening, followed by one or more technical and behavioral interviews, often culminating in an onsite interview with multiple interviewers. The process is generally organized and flows from asynchronous to live interactions.
HireVuePhone screeningOnsite interviews
Technical and Behavioral Focus
Interviews often include a mix of technical questions, particularly around coding practices and specific programming languages like C++, alongside behavioral questions using the STAR format to assess candidates' experiences and problem-solving approaches.
Technical questionsBehavioral questionsSTAR format
Communication and Timeline
While the initial stages of the interview process are often quick, candidates report significant delays in receiving feedback or offers, leading to feelings of uncertainty and frustration during the waiting period.
CommunicationTimelineFeedback delays
Interview Atmosphere
The overall tone of interviews varies, with some candidates experiencing a friendly and relaxed environment, while others report confrontational or uncomfortable interactions, particularly during initial screenings.
Interview atmosphereFriendlyConfrontational
Onsite Interview Intensity
Onsite interviews can be intense, often involving multiple back-to-back sessions that include technical problem-solving under pressure, which candidates feel requires thorough preparation, especially for unexpected components like whiteboard challenges.
Candidates suggest that anticipating the structure and components of the interviews, especially the technical depth and behavioral expectations, could improve their confidence and performance during the process.