Senior Software Developer
Posted Sep 29, 2026 · We last checked this listing on Oct 6, 2026
Apply at Northwestern Medicine
Likely interview questions for this role
Written from this job description, not a generic list. Each one notes what the interviewer is really checking.
About your past
Tell me about an application you designed and led from start to deployment. What were the hardest decisions?
What they are checking: Whether they have really owned a project end to end, as a senior developer here is expected to.
Tell me about a junior developer you mentored. What did you change in how you worked with them?
What they are checking: Whether mentoring is something they actually do and adapt, since the posting expects it.
Tell me about a deployment that went wrong. What did you learn?
What they are checking: Whether they own failures and improve release practices afterward.
How do you explain a technical tradeoff to a non-technical project lead?
What they are checking: Whether they can communicate across cross-functional teams in plain terms.
What would you do
A clinical stakeholder wants a feature by next week that you think is risky. How do you handle it?
What they are checking: Whether they can push back with reasons and offer options rather than just refusing or caving.
Where have you used AI coding tools, and where would you not trust them in a health care codebase?
What they are checking: Whether they use AI with judgment in line with the department's AI and automation push.
About the work
You're building an app that touches patient data. What design choices do you make differently than you would for a regular business app?
What they are checking: Whether they think about PHI, access control, audit logging and HIPAA from the start.
How do you approach integrating with a clinical system like an EHR when the interface is limited or poorly documented?
What they are checking: Whether they can handle the messy integrations common in health care, such as HL7 or FHIR interfaces.
Walk me through how you debug a production issue you can't reproduce locally.
What they are checking: Whether they rely on logs, monitoring and hypotheses instead of guessing under pressure.
What does a good code review look like to you, as reviewer and as the person being reviewed?
What they are checking: Whether they use reviews to teach and catch real problems, not just to enforce style.
How do you decide how much automated testing a feature needs?
What they are checking: Whether they weigh risk and cost when testing, rather than following a rule blindly.
Practice this interview out loud.
Offer builds a real interview for this exact role at Northwestern Medicine from your resume and this job description, asks the questions one at a time, and tells you what landed. The first one is free.
Practice this out loudThe full job description
As published by Northwestern Medicine.