LSS Software Engineering Co-op - Madison, WI
Posted Sep 11, 2026 · We last checked this listing on Oct 6, 2026
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 the most substantial C++ project you've worked on. What were the hardest parts?
What they are checking: Whether their C++ experience is real and deep enough to contribute to production and tool code.
Tell me about a time you got feedback in a code review that you disagreed with.
What they are checking: Whether they can discuss code on its merits and learn from experienced engineers without getting defensive.
What would you do
Walk me through how you'd debug a problem that only shows up once every few hours on the hardware.
What they are checking: Whether they have a patient, methodical approach to intermittent bugs using logs and narrowing conditions.
You're stuck on a task and your mentor is busy. How long do you wait before asking for help?
What they are checking: Whether they balance trying on their own with not burning days stuck in silence.
About the work
What's the difference between real-time and non-real-time software, and why would it matter in a ventilator?
What they are checking: Whether they understand that missing a timing deadline in life-support software can be as bad as a wrong answer.
How do you manage memory in C++, and what kinds of bugs come from getting it wrong?
What they are checking: Whether they know about leaks, dangling pointers and RAII, which matter a lot in long-running embedded systems.
What changes when your code runs on embedded hardware instead of a laptop?
What they are checking: Whether they appreciate limited memory, fixed timing and hardware interaction instead of assuming desktop resources.
You're building a test tool that verifies product performance. How do you make sure the tool itself is trustworthy?
What they are checking: Whether they see that a buggy test tool can hide real defects and give false confidence.
Why would software development for a medical device be slower and more documented than at a startup?
What they are checking: Whether they accept that traceability and review are part of the job in a regulated environment, not obstacles.
How do you write code so the next person can understand and safely change it?
What they are checking: Whether they value clarity, naming and documentation in code that will live for years.
Practice this interview out loud.
Offer builds a real interview for this exact role at GE HealthCare 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 GE HealthCare.