Beyond Lectures

Experience, Portfolio & Community Notes

Direct guidance for students building credibility through projects, communication, internships, and professional habits.

4Evidence Types
3Portfolio Habits
1Clear Direction
Portfolio direction

Experience is not only placement time. It is evidence that you can think like an engineer.

Your portfolio should make your thinking visible: show requirements, risks, test methods, data, failures, fixes, and what changed after you learned from clinical or user constraints.

If you do not have a formal internship yet, build small, honest proof: a device case study, signal notebook, risk table, service workflow, or interview story bank.

System maps Test reports Risk tables Reflection notes
Show method Show results Show what changed

Show the Engineering Trail

A strong biomedical portfolio should show problem definition, constraints, design choices, test setup, results, and what changed after failure.

  • Include requirements and assumptions
  • Show test data, even when imperfect
  • Explain patient, clinician, or user constraints

Learn the Environment Before the Tool

In hospitals and device companies, technical skill matters, but context matters more. Learn who uses the device and what can go wrong.

  • Ask how success is measured
  • Track safety and usability concerns
  • Write concise notes after every observation

Use Social Platforms With Purpose

A good professional presence is a clear record of what you are learning, building, reading, and asking.

  • Post project breakdowns, not vague motivation
  • Credit sources and collaborators
  • Connect with engineers in your target area

Translate Between Disciplines

Biomedical engineers sit between clinicians, researchers, designers, software teams, and quality teams. Practice explaining the same idea at different levels.

  • Write a one-sentence version of each project
  • Prepare a technical version with numbers
  • Explain risk and limitations honestly
Portfolio Build Path
1

System map

Draw how a device connects user, sensor, electronics, software, maintenance, and patient safety.

2

Test report

Write what you tested, why it matters, what failed, and how you would improve the design.

3

Risk table

List hazards, causes, effects, controls, and verification evidence in simple language.

4

Reflection note

Explain what the project taught you about users, clinical workflow, documentation, and teamwork.

Experience Without a Placement

Medical Device Case Study

Pick one device such as an infusion pump, ECG monitor, or LINAC subsystem. Explain the user workflow, main risks, sensors, outputs, and maintenance concerns.

Signal Processing Notebook

Use sample ECG, PPG, EMG, or EEG data. Show filtering, noise sources, feature extraction, plots, and what a clinician should be careful about.

Risk and Safety Table

Create a simple hazard table with failure mode, possible harm, existing control, verification method, and residual risk.

Service Workflow Note

Write how a hospital engineering team might receive, inspect, test, label, maintain, and document a device.

Technical Reading Summary

Summarise a standard, textbook chapter, or manufacturer page. Extract what matters for safety, usability, and clinical workflow.

Interview Story Bank

Prepare short examples for problem solving, teamwork, failure, safety awareness, and learning a difficult technical topic.

How to write experience on a CV

Use evidence-based wording. Instead of "worked on biomedical project", write what you actually did.

  • Weak: Built a health monitoring project.
  • Better: Built a pulse sensor prototype, filtered noisy PPG data in Python, compared peak detection settings, documented limitations from motion artefact.
  • Strong: Connect the project to safety, validation, users, or clinical workflow.
Interview Preparation
SituationWhat problem, user need, or device workflow were you dealing with?
TaskWhat did you personally need to investigate, build, test, or explain?
ActionWhat method did you use: measurement, analysis, troubleshooting, or teamwork?
ResultWhat changed, what did you learn, and what would you improve next?