Biomedical Engineer interview questions, with worked answers

How to use these questions

Many device interviews hand you a product, such as a pump, a monitor or a handheld instrument, and ask how you would develop it. Start from the user and the intended use, then the risks, the design inputs, the tests and the records. Have one device story ready: your part, the hardest test, and a change you had to make late.

What a biomedical engineer is expected to know

• The system: ISO 13485Work inside a medical device quality system: procedures, records, reviews and changes that can be traced., design controlsRun a design through inputs, outputs, reviews, verification, validation and transfer, with records. and technical documentationWrite and maintain the technical file that shows a device meets its requirements..
• Safety: ISO 14971Run risk management for a device: hazards, risks, controls and the proof that each control works. risk management, IEC 60601Design electrical medical equipment to pass its safety and electromagnetic tests. and biocompatibilityChoose materials and plan the tests that show the parts touching the body are safe..
• Proof: verification and validationPlan and run the tests that prove the device was built right and is the right device. and usability engineeringStudy how users handle the device and design out the mistakes they could make..
• The people: regulatory affairs, quality, clinicians, production and suppliers.

Tools come up side by side and none is a must: SolidWorks or Creo for 3D design, MATLAB and LabVIEW for analysis and test benches, Polarion or another requirements tool for traceability. Panels want the method more than the tool.

From need to verified design

What is a design input, and how do you write requirements that can be verified?

What they check: requirements that can be tested.

Short answer: "A design input is a requirement the design must meet, derived from the users' needs, the intended use, the standards and the risk controls. I write each one so a test can say pass or fail: a value, a tolerance, a condition. Vague words such as easy or fast become numbers or a defined test."

The full answer: A requirement nobody can test will fail you at verification.

A weak answer: "The device should be user-friendly." Follow-up: "Marketing wants it lighter, the clinicians want it sturdier." Say how you write the input.

How do design controls run through a medical device project?

What they check: the backbone of device development.

Short answer: "Design controls are the planned steps and records that take a device from needs to production: design planning, inputs, outputs, reviews, verification, validation, transfer and changes. Each stage has a review with people outside the design, and the records end up in the design history file."

The full answer: Design controls are not paperwork after the fact; they are how the work is planned.

A weak answer: "We write the documents at the end." Follow-up: "An audit finds a design review with no record." Say what that means.

Walk us through risk management to ISO 14971 for a new device.

What they check: risk as a design tool.

Short answer: "I list the hazards in normal use, in misuse and in failure, estimate how likely and how severe each harm is, and choose controls in order: safe design first, then protective measures, then information for users. Each control is verified, the remaining risk is judged against the benefit, and the risk file stays alive after launch."

The full answer: A warning in the manual is the weakest control, not the first one.

A weak answer: "We add a warning label." Follow-up: "Field data shows a harm you rated as rare." Say what you do.

What is the difference between verification and validation?

What they check: the two kinds of proof.

Short answer: "Verification asks whether we built the device right: does it meet each design input, tested on the bench. Validation asks whether we built the right device: does it meet the users' needs in real or simulated use, with real users. Both need a plan, set acceptance criteria and reports before results are known."

The full answer: A device can pass every test and still fail the user.

A weak answer: "They are the same thing." Follow-up: "Verification passed, but nurses keep using the device wrongly." Say what that tells you.

How do you build usability into a device and prove it?

What they check: designing for real users under stress.

Short answer: "I find the critical tasks and the use errors that could cause harm, test early designs with real users in formative studies, change the design, and run a summative test at the end that shows the critical tasks are done safely. The international usability standard, IEC 62366, describes the process."

The full answer: Users are tired, rushed and interrupted; design for that, not for the lab.

A weak answer: "We train the users." Follow-up: "Users keep pressing the wrong button at night." Say what you change.

How do you deal with biocompatibility and sterilisation when you choose a material?

What they check: materials seen as part of safety.

Short answer: "Biocompatibility means the parts that touch the body cause no harm, such as irritation or toxic effects, for the kind and length of contact. I choose materials with a known history, plan the evaluation and tests with the experts, and check that the material survives the chosen sterilisation method, because some plastics change with it."

The full answer: A cheaper material can cost a year of tests.

A weak answer: "The supplier says it is medical grade." Follow-up: "The supplier changes the material's additive." Say what you do.

What changes when the device contains software, and how does IEC 62304 shape the work?

What they check: software treated as part of the device.

Short answer: "The software gets a safety class from what could go wrong, and its class sets how much planning, architecture, testing and documentation it needs. Software risks join the device's risk file, outside libraries are listed and watched, and every release is controlled. Cybersecurity is part of the design too."

The full answer: In a device, a software update is a design change.

A weak answer: "The software team handles the software." Follow-up: "A library you use has a security flaw." Say what happens.

How do you design an electrical device to pass IEC 60601?

What they check: electrical safety planned in.

Short answer: "I plan the insulation, the leakage currents and the separation between the patient and the mains from the start, choose parts that are certified for the purpose, design for electromagnetic compatibility, and run pre-tests before the formal tests at the lab. The standard and its collateral parts set what to test."

The full answer: Electrical safety fixed late often means a new board.

A weak answer: "The lab will tell us what to fix." Follow-up: "The device fails the leakage current test." Say where you look.

The file, the market and the senior round

What goes into the design history file and the technical documentation?

What they check: knowing what proves a device.

Short answer: "A design history file holds the record of how the design was developed: plans, inputs, outputs, reviews, verification, validation and changes. The technical documentation for approval draws on it and adds the device description, the risk file, the labelling and the evidence of conformity. I keep them current as the work goes, not at the end."

The full answer: An auditor reads the file; the file is what you did.

A weak answer: "Regulatory affairs writes all that." Follow-up: "A reviewer cannot find the test that proves one requirement." Say how you fix it.

How do you handle a design change to a device already on the market?

What they check: change control on a live product.

Short answer: "I describe the change and its reason, assess its effect on risks, on verification and on the approval, decide with quality and regulatory affairs which tests to repeat and whether the authorities must be told, then implement it under change control and update the file."

The full answer: Small changes to a part can be large changes to a device.

A weak answer: "It is a small change, so we just do it." Follow-up: "A supplier's part goes out of production." Say what you do.

How do you work with a supplier of a critical component?

What they check: quality reaching beyond your own walls.

Short answer: "Critical suppliers are qualified before we buy, with an agreement on quality and on telling us about changes. I write clear specifications, agree incoming checks, and look at their data and any failures with them. A change at the supplier is a change for us."

The full answer: The supplier's process is part of your device.

A weak answer: "Purchasing chooses suppliers." Follow-up: "A batch of parts is slightly out of specification." Say whether you use it.

A complaint comes in from a hospital. What happens next on the engineering side?

What they check: learning from the field.

Short answer: "Quality logs the complaint and decides whether it must be reported to the authorities. Engineering investigates the returned device or the data, finds the root cause, checks the risk file against what happened, and proposes a correction. If other devices are affected, the action may reach the field."

The full answer: Every complaint is a test result you did not plan.

A weak answer: "Probably user error." Follow-up: "Three hospitals report the same alarm failure." Say what you do.

How do you work with regulatory affairs and, in the EU, a notified body on a new device?

What they check: working with the people who approve.

Short answer: "A notified body is an organisation the EU designates to assess whether a device meets the EU MDR before it can carry the CE mark. I agree early with regulatory affairs which route the device takes and what evidence it needs, keep my parts of the file clear, and answer the notified body's questions with facts and references to the file."

The full answer: Clear evidence answers questions before they are asked.

A weak answer: "Regulatory affairs deals with them." Follow-up: "The EU notified body asks for a test you did not plan." Say what you do.

As a senior biomedical engineer or lead biomedical engineer, how do you guide a junior biomedical engineer through a design review?

What they check: reviews that teach and protect.

Short answer: "I help the junior engineer prepare: the inputs, the open risks and the test status, sent out in advance. In the review they present, I make sure findings are recorded with owners and dates, and afterwards we go through the findings together so they see why each one matters."

The full answer: A review that only the senior understands has taught nobody.

A weak answer: "I present it for them." Follow-up: "The review finds a missing requirement a week before verification." Say how you handle it.

In a regulated field, where do AI tools help a biomedical engineer, and where do they stop?

What they check: sober use of new tools in a regulated field.

Short answer: "AI tools can help search standards, draft documents and test reports, and check traceability for gaps. I would still review every line that goes into the file, keep confidential designs in approved tools, and keep design and risk decisions with engineers who answer for them. If the device itself uses AI, in the EU the EU AI Act adds its rules for high-risk AI to the device rules."

The full answer: A document generated quickly is still a document you must be able to defend.

A weak answer: "AI will write the technical file." Follow-up: "A drafted report cites a standard clause that does not exist." Say how you would catch it.

Your CV for these questions

Each line on your CV invites the questions above: which device, which test, which risk. Write each one as a device, a test and a result, so the panel wants to hear more:

Hold your CV against a biomedical engineer job with the free score; then prepare the device story for the area it finds thin, from the user's need to the test report.