Skip to main content

Orion Innovation

Associate Engineer

Bridgewater, New Jersey, United StatesentryAdded today

About this role

Orion Innovation seeks a Diagnostic Software Engineer to develop low-level embedded diagnostic software and hardware validation tools. The role requires deep expertise in direct hardware access, embedded systems, and diagnostics with 3+ years of experience in electrical or computer engineering disciplines.

What you'll do

  • Write low-level code for direct hardware access using device datasheets and embedded controller peripherals
  • Develop comprehensive test suites to exercise and validate hardware functionality
  • Analyze and debug hardware failure scenarios using schematics and digital circuit analysis
  • Implement device drivers and work with communication bus systems (SPI, I2C, MDIO, PCIe)
  • Collaborate with cross-functional teams to diagnose product issues and implement solutions
  • Maintain code quality and version control practices using Git

What they're looking for

  • Embedded systems development
  • C/C++ and Python programming
  • Low-level hardware access and protocol implementation
  • Linux OS and shell scripting
  • Hardware schematic reading and circuit analysis
  • Device driver development
  • Git version control
  • Communication bus protocols (SPI, I2C, MDIO, PCIe)
Apply on the employer's site

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

Orion Innovation

Orion Innovation builds scalable web applications and AI-powered enterprise software solutions, with expertise in cloud-native database systems and GxP-compliant digital systems. The company is hiring full stack developers, sales professionals, database engineers, validation engineers, and support specialists to support its product development and market expansion efforts.

View all jobs at Orion Innovation

Likely interview questions

  • Describe your experience with low-level hardware access and working directly with device datasheets—can you walk through a specific example?
  • Tell us about a time you debugged a complex hardware issue; what was your approach and what tools did you use?