ZipRecruiter

Log In

1

Contract Firmware Jobs in Florida (NOW HIRING)

TEKsystems

Systems Administrator

Tallahassee, FL · On-site

Apply firmware and software revisions to host systems and work with vendors to support operational ... TrueNAS Experience Level Intermediate Level Job Type & Location This is a Contract to Hire position ...

next page

Showing results 1-20

All JobsContract Firmware JobsContract Firmware Jobs in Florida

Contract Firmware information

What is a contract firmware engineer?

Contract firmware engineers are professionals who specialize in designing, developing, and testing embedded software (firmware) for devices, usually on a temporary or project-specific basis. They are hired by companies to work on particular projects, bringing expertise in programming microcontrollers, optimizing code for hardware, and ensuring reliable device performance. Unlike full-time employees, contract firmware engineers typically work for a set period or until the completion of a project, offering flexibility and specialized skills to organizations needing firmware development support.

What are the key skills and qualifications needed to thrive as a contract firmware engineer?

To thrive as a Contract Firmware Engineer, you need a solid background in embedded systems, programming languages like C/C++, and experience with microcontroller architectures, often supported by a degree in electrical engineering or computer science. Familiarity with tools such as oscilloscopes, logic analyzers, version control systems (e.g., Git), and sometimes certifications in embedded development are commonly required. Strong problem-solving skills, clear communication, and the ability to quickly adapt to new projects or client requirements make someone stand out in this position. These skills ensure efficient development, effective collaboration with hardware and software teams, and successful delivery of high-quality firmware solutions for diverse clients.

What are some common challenges faced by contract firmware engineers in managing multiple client projects?

Contract firmware engineers often juggle projects for different clients, which can present challenges such as adapting to varying hardware platforms, coding standards, and documentation practices. Effective time management and clear communication with each client are essential to ensure that project milestones are met and expectations are aligned. Additionally, contract engineers must quickly learn new tools or development environments and stay updated with industry best practices to deliver high-quality, reliable firmware solutions on tight deadlines.

What is the difference between Contract Firmware vs Firmware Engineer?

AspectContract FirmwareFirmware Engineer
CredentialsTypically requires relevant certifications or experience in embedded systemsRequires a degree in electrical engineering, computer science, or related fields
Work EnvironmentTemporary or project-based, often freelance or consulting rolesFull-time employment within a company or organization
Industry UsageCommon in industries needing short-term expertise, such as startups or R&DStandard role in manufacturing, tech, and embedded systems companies
Search & Comparison IntentOften compared for project-based work or freelance opportunitiesCompared for long-term career paths or full-time positions

Contract Firmware roles focus on short-term, project-specific embedded system development, often requiring specialized skills and certifications. Firmware Engineers typically hold full-time positions, developing and maintaining firmware as part of ongoing product development. Both roles involve embedded systems but differ mainly in employment type and duration.

What are the most commonly searched types of Firmware jobs in Florida?

The most popular types of Firmware jobs in Florida are:

Contract Firmware jobs near you

Firmware Integration & Test Systems Engineer

Miami, FL • On-site

Prowinch LLC
Machinery Manufacturing • 11 - 50 employees
Learn more about Prowinch LLCexternal

Full-time

Posted 4 days ago

Job description


Overall Summary


The Firmware Integration & Test Systems Engineer is a systems-focused engineer responsible for making sure the different software and firmware components of MilaY work correctly together. This is not primarily a firmware-development position and it is not a traditional QA role. The engineer builds the automated test infrastructure, simulators, diagnostic tools, and integration environments needed to test system behavior across component boundaries.

MilaY is composed of multiple independently developed systems, including the machine and its firmware, the mobile application, the relational backend, and the telemetry backend. The machine firmware is developed externally and communicates with ProWinch systems through defined interfaces. As the project grows to support additional firmware versions, hardware configurations, and ProWinch equipment platforms, manually verifying every combination becomes increasingly difficult and creates a substantial regression risk.

The primary responsibility of this engineer is to build a repeatable Software-in-the-Loop and Hardware-in-the-Loop testing capability. The goal is to allow firmware and other MilaY components to be exercised automatically under realistic operating conditions without requiring every test to be performed manually on a physical machine. The engineer would create firmware simulators, test harnesses, protocol tests, fault-injection capabilities, compatibility tests, and automated integration scenarios that can eventually run as part of the project's CI/CD pipelines.

A strong candidate will normally have experience spanning embedded software and software test infrastructure. Expected strengths include C/C++, Python automation, firmware debugging, automated integration testing, Software-in-the-Loop testing, binary protocol testing, Linux, fault injection, and CI/CD. Hardware-in-the-Loop testing, simulator development, CAN/CANopen, protocol analysis, and device communication testing are particularly valuable. MilaY-specific technologies such as BLE, MQTT, USB CDC, X.509/TLS, and industrial automation are additional advantages.

This engineer also serves an important cross-team integration function. When the mobile application, firmware, or backend behaves differently from the documented interface, the integration test environment should help determine where the incompatibility exists. Instead of relying on one team's implementation as the definition of correct behavior, tests can be built against the agreed protocol and system contracts.

The role becomes increasingly important as MilaY supports more hardware platforms and firmware versions. Without this capability, compatibility testing tends to depend on developers manually connecting applications to physical boards and reproducing specific conditions. That approach becomes slower and less reliable as the number of supported combinations increases. A dedicated integration test system provides repeatable regression testing, earlier detection of interface problems, controlled fault testing, and evidence that specific combinations of firmware and MilaY software have been validated.

In practical terms, this candidate represents the engineer who builds the infrastructure that allows ProWinch to answer questions such as:
  • Does the new firmware still work with the current mobile application?
  • Does the application behave correctly with older supported firmware?
  • Does a firmware command conform to the documented binary protocol?
  • What happens when packets are lost, corrupted, delayed, or rejected?
  • Does the system recover correctly after a connection or firmware failure?
  • Does telemetry generated by the firmware match the expected format and behavior?
  • Can the same test scenario run against a simulator today and real hardware later?
  • Which combinations of application, firmware, protocol, and hardware configuration have actually been tested?

The long-term objective is a testing environment where important system behaviors can be exercised automatically against simulated firmware during normal development and then validated against real boards through Hardware-in-the-Loop testing. This reduces dependence on manual integration testing and gives the project a scalable way to manage firmware compatibility as MilaY expands.
Requirements: English ( Fluent), written and spoken. 

Skills 

Tier 1: Core


  1. Embedded C/C++
  2. Python automation
  3. Automated integration testing
  4. Firmware debugging
  5. Software-in-the-Loop testing
  6. Test harness development
  7. Binary protocol testing
  8. Linux
  9. Fault injection
  10. CI/CD

Tier 2: Highly desirable

  1. Hardware-in-the-Loop
  2. Simulator development
  3. CAN/CANopen
  4. Protocol analysis
  5. Hardware/software debugging
  6. Docker/reproducible test environments
  7. Firmware compatibility testing
  8. Device communication testing

Tier 3: MilaY-specific advantages

  1. BLE
  2. MQTT
  3. USB CDC
  4. Azure DevOps
  5. X.509/TLS
  6. Industrial automation
  7. Hoists/cranes/motor controls


Tools and Technologies


Embedded development

  • GCC/Clang, CMake, GDB
  • J-Link, OpenOCD, or comparable JTAG/SWD tools

Testing and simulation

  • pytest
  • GoogleTest, Catch2, Unity/CMock, or similar
  • Renode, QEMU, or comparable firmware simulation/emulation environments

Industrial and device communications

  • CANoe / CANalyzer
  • SocketCAN / virtual CAN
  • Wireshark
  • nRF Connect / BLE diagnostic tools
  • Mosquitto / MQTT tooling
  • USB/serial diagnostic tools

Hardware integration

  • Logic analyzers
  • Oscilloscopes
  • CAN interfaces
  • Programmable power and test equipment

Automation and infrastructure

  • Docker / Docker Compose
  • Azure DevOps Pipelines, Jenkins, GitHub Actions, or similar
  • Git
  • Linux development and diagnostic utilities