Biomedical engineer with 5 years in medical device development, focused on design verification for Class II infusion and monitoring products. Led verification testing for a pump that received FDA 510(k) clearance with no additional information requests. Works within ISO 13485 design controls and ISO 14971 risk management.
Experience
Biomedical Engineer II, Clearvein Medical (Minneapolis, MN)
Mar 2023 – Present
Led design verification for a Class II ambulatory infusion pump, writing 60 test protocols that supported a 510(k) cleared without AI requests
Maintained the design history file and traceability matrix in Greenlight Guru under 21 CFR 820 and ISO 13485
Updated the ISO 14971 risk file and FMEA after 9 design changes
Built a LabVIEW flow-accuracy fixture that cut test time per unit from 4 hours to 90 minutes
Prototyped housings in SolidWorks and ran IEC 60601-1 pre-compliance tests with an outside lab
Analyzed bench data in MATLAB and Minitab for a pulse oximetry sensor
Education
B.S. Biomedical Engineering, University of Minnesota (Aug 2017 – May 2021)
Skills
Regulatory: FDA 510(k), 21 CFR 820, ISO 13485, ISO 14971, IEC 60601-1
Engineering: design verification, test method validation, FMEA, root cause analysis
Tools: SolidWorks, MATLAB, LabVIEW, Minitab, Greenlight Guru
How to write a Biomedical Engineer resume
A strong Biomedical Engineer resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Put your most relevant recent role first and make every bullet show a result, not a duty.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page for most candidates; move to two only if every line is relevant.
Summary: Write two or three lines: your role, your strongest skills, and one result that proves them.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
Biomedical Engineer resume FAQ
What should a Biomedical Engineer resume include?
A Biomedical Engineer resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Put your most relevant recent role first and make every bullet show a result, not a duty.
What is the best resume template for a Biomedical Engineer?
Classic, Tech and Modern work well for Biomedical Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Biomedical Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Biomedical Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Biomedical Engineer roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong Biomedical Engineer resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."