Skip to main content

Fluxergy

Firmware Engineer III

Irvine, Californiafull timemidAdded 1 month ago

About this role

Fluxergy, an in vitro diagnostics innovator, seeks a Firmware Engineer III in Irvine to develop firmware for a multi-modal point-of-care laboratory testing platform. You'll work on complex, evolving systems where your contributions directly shape the product's direction and performance in a collaborative, engineering-focused environment.

What you'll do

  • Design and develop firmware for multi-modal diagnostic testing platform
  • Solve complex, ambiguous technical problems with systemic perspective
  • Collaborate with cross-functional teams to influence product architecture and performance
  • Contribute ideas and take ownership of firmware solutions
  • Support molecular, clinical chemistry, immunoassay, and hematology testing capabilities
  • Participate in continuous improvement and adaptation as systems evolve

What they're looking for

  • Firmware development and embedded systems
  • Complex problem-solving and systems thinking
  • Collaborative teamwork and communication
  • Adaptability to evolving requirements
  • Critical thinking and pragmatic engineering approach
  • Ability to work with ambiguity
  • Self-motivation and ownership mentality
  • Continuous learning mindset
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Fluxergy

Fluxergy develops a multi-modal point-of-care diagnostic platform for clinical, veterinary, and food safety testing. The company is hiring backend and firmware engineers to build and maintain the software and embedded systems that power their in vitro diagnostics devices.

View all jobs at Fluxergy

Likely interview questions

  • Tell us about a time you debugged a complex firmware issue in a real-time or embedded system. How did you approach it, and what tools or methodologies did you use?
  • Describe your experience with multi-modal or multi-functional systems. How have you handled the complexity of managing different operational modes or subsystems within a single platform?