Biomedical equipment
How medical devices work, and what it takes to trust what they measure.
I trained as a biomedical equipment engineer. Now I clean up data that doesn't agree with itself.
I'm a data science student at BYU-Idaho. At work I evaluate transfer credit: 300+ academic records a semester from schools that each describe the same course differently. Most of what I know about messy data, I learned there.
I studied biomedical equipment engineering in Dar es Salaam. The hard part was rarely one device. It was everything around it that had to be right before you could trust a reading. I came to the U.S. for computer science, switched to data science, and kept running into the same kind of problem.
My campus job is transfer credit evaluation. Every semester, hundreds of transcripts come in from schools that name, number and weight their courses differently, and someone has to decide what counts as what. It's basically schema matching, except a student's graduation date depends on getting it right.
So I build tools for the tedious parts: pulling data out, matching it, and checking it. At a hackathon I built a tool that reads web pages so researchers don't have to open every one. At work I reordered our verification steps and cut processing time by 20%. It's not the exciting part of data work, but everything after it depends on it.
In each one, the job was making sure the pieces agreed before anyone relied on the result.
How medical devices work, and what it takes to trust what they measure.
Learning to turn manual, step-by-step work into code people can reuse.
Matching and cleaning up records before anyone analyzes them or makes decisions with them.
Evaluate 300+ academic records per semester with 100% accuracy, matching courses between schools whose catalogs don't line up. Reordered the verification steps, which cut processing time by 20%. Resolve 50+ data discrepancies a term by tracing each one back to the department that created it.
Ran exam security procedures for 50+ test-takers at a time and helped 20+ people a week with technical problems.
This demo uses made-up records to show the kind of mismatch I deal with at work: the same course listed under different titles, credit values or department codes.
I'm looking for data science and data engineering internships, and full-time roles starting in 2027.
I enjoy the early part of the pipeline most: getting data out, matching it, and making sure it's right. Either way, feel free to reach out. I reply to every message.