Cybersecurity Software Engineer
Meridian Bioscience, Inc.
—
Jul 1, 2026
—
Jul 21, 2026
What this job asks for AI summary
A software engineering role centered on embedding cybersecurity into diagnostic platform development, bridging R&D, Quality, and Regulatory teams. Day-to-day work involves writing embedded software, translating FDA cybersecurity guidance and standards such as IEC 62304 and ISO 14971 into technical specifications, maintaining design control documentation, and conducting threat modeling and risk analysis. Best suited to engineers with regulated-industry experience who are comfortable operating across both technical and compliance domains.
Senior level · 5+ years · Cincinnati, OH · Bachelor's required · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $116,813 (middle half $84,416–$142,741).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
This role sits at the intersection of software engineering and cybersecurity for medical devices; the primary day-to-day work leans toward security analysis, compliance, and secure design review rather than pure software development, hence 15-1212 (Information Security Analysts) was chosen over 15-1252 (Software Developers). However, the explicit embedded coding duty and software lifecycle ownership make 15-1252 a genuine runner-up.
Meridian Bioscience is headquartered in Cincinnati, OH; no specific work location is stated in the posting, so Cincinnati is assumed.
The degree requirement is a Bachelor's or Master's in a relevant field — Bachelor's is the minimum hard gate.
NIST Cybersecurity Framework and OWASP are listed together under the Preferred section as examples of 'secure development frameworks,' so they are captured as a single preferred skill with alternatives.
AAMI TIR57 and TIR97 are listed together as a single preferred standard reference and are captured accordingly.
No compensation figures are provided in the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): IEC 81001-5-1.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.