Skip to main content

Senior Embedded Firmware Engineer

Posted yesterday

kasmoIrving (TX)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Job DescriptionJob Description Position: Senior Embedded Firmware Engineer Required Skills: Embedded C, C, RTOS, QNX QNX OS Exp is extremely mandatory with RTOS and Linux Device Driver and Embedded C**** Location: Houston, TX (Onsite)
Role Overview: We are seeking an experienced Senior Embedded Firmware Engineer to join our R&D team. The ideal candidate will take ownership of firmware design, development, and optimization for high-performance embedded systems. This role involves driving innovation, ensuring software reliability, and collaborating closely with cross-functional teams to deliver cutting-edge solutions.
Key Responsibilities: " Enhance and maintain existing firmware systems while ensuring architecture integrity and a seamless user experience. " Evaluate current applications to identify areas for improvement, optimization, and scalability. " Refactor and optimize code for resource efficiency without compromising functionality. " Lead the selection and adoption of tools, technologies, coding standards, and best practices to maintain high-quality outcomes. " Conduct thorough unit testing, debugging, and validation prior to release. " Resolve issues identified during internal testing or reported by customers. " Provide accurate task estimates, progress reports, and documentation. " Contribute to formal verification and validation plans. " Manage version control, product releases, and firmware updates. " Collaborate with management to align deliverables with project goals and schedules. " Work closely with Product Management and Engineering to evaluate the feasibility of new applications and features. " Develop and integrate critical software components, frameworks, and device drivers. " Take initiative in assuming additional responsibilities as project needs evolve.
Experience Requirements: "10 15 years of hands-on experience in Embedded Firmware Development, including: " Programming: Expertise in Embedded C, C, Data Structures, RTOS, and Microprocessors. " Operating Systems: Strong experience with QNX and Linux environments. " Memory Interfaces: Practical experience with NAND, NOR, and DDR4. " Communication Protocols: Working knowledge of UART, I2C, SPI, Ethernet, and Multithreading. " Tools & Debugging: Proficient with IDEs, debug emulators, and version control systems (e.g., SVN, Git).
Qualifications & Skills: "
Education: Bachelor's degree in Engineering or Computer Science, or equivalent combination of education and experience. " Firmware Development Expertise: Deep understanding of the complete firmware lifecycle, from concept to deployment. " Architecture & Design: Strong grasp of software architecture principles and design patterns. " Leadership: Proven ability to lead projects, mentor team members, and deliver on deadlines. " Analytical & Problem Solving: Excellent debugging, analytical, and troubleshooting abilities. " Critical & Innovative Thinking: Ability to assess complex challenges and propose effective, creative solutions. " Communication: Strong written and verbal communication skills with the ability to collaborate across teams and time zones. " Adaptability: Self-motivated, proactive, and capable of working independently or in a collaborative environment. " Time Management: Skilled at prioritizing multiple projects in a fast-paced environment. " Continuous Learning: Enthusiastic about learning new technologies and improving technical expert.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this