Sr Hardware Engineer Lead

or drop it. Application deadline is minor metadata; we can include in a paragraph maybe under a generic "Details" but better to drop? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Application deadline is substantive? It's a date; but it's not a heading. We can include it in a paragraph maybe under a heading like "Details" but we don't have a heading for that. Could just include as a

after other sections. - About TEKsystems etc: that's boilerplate about company, equal opportunity, etc. Should be removed as per instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should strip all that. Thus final HTML will have sections: About the role (maybe using heading "About the role" or "Position Summary"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. For "About the role" we have Position Summary. So we will use

About the role

with the summary. Responsibilities:

Responsibilities

• each duty. Requirements: maybe we can combine Qualifications and Requirements? The instruction lists Requirements as a possible heading. We have qualifications list; we could put under Requirements. But we also have Qualifications heading. We need to decide: we should not create thin sections; prefer few substantive sections. We have both Requirements and Qualifications content; we could merge them into one section called "Requirements" or "Qualifications". Which is more appropriate? The posting has "Qualifications Additional Skills & Qualifications". So we can use

  Qualifications

  and include all the bullet points (education, experience, technical skills). That seems fine. Skills: we have a list of skills; we can put under

  Skills

  . Benefits: we have benefits list; we can put under

  Benefits

  . Pay: we have pay range; we can put under

  Pay

  . Schedule: we have workplace type (fully onsite) and location; maybe we can put under

  Schedule

  but schedule usually refers to work schedule (full-time, part-time, shift). We have location and workplace type; not exactly schedule. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we don't have schedule specifics (like full-time, hours), we should not create Schedule section. Instead we could include location and workplace type under a generic "Details" but we don't have a heading for that. Perhaps we can put location under "About the role" or as a paragraph after responsibilities. But we need to preserve all substantive info. Location is substantive. We could add a

  after the sections: "Location: Jacksonville, FL (fully onsite)." Or we could incorporate into Qualifications? Not ideal. Maybe we can create a section "Job Details" but not in allowed headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we need to fit location into one of those. Perhaps we can put location under "About the role" as part of the summary. Or we could add a short paragraph after the sections not under a heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside headings. So we can add a

  for location after the sections. But we also have "Job Type & Location" and "Workplace Type". So we can combine: "This is a Permanent position based out of Jacksonville, FL. This is a fully onsite position in Jacksonville,FL." We can deduplicate. Thus final HTML:

  About the role

  The Sr. Hardware Engineer Lead provides hands-on technical leadership in the design, development, and support of embedded electronic products throughout the product lifecycle. This role leads hardware development and product improvements while partnering cross-functionally to ensure products are reliable, manufacturable, compliant, and successfully supported from development through production.

  Responsibilities

  • Lead the design and development of embedded electronic products from concept through production, including circuit design, component selection, prototyping, design reviews, documentation, EVT/DVT/PVT, and product release.
  • Lead and perform analog, digital, mixed-signal, power, sensor, wireless, and microcontroller-based hardware design, including schematic development and PCB layout reviews to ensure performance, manufacturability, and design quality.
  • Lead prototype bring-up, functional verification, environmental and reliability testing, EMC pre-compliance testing, hardware debugging, root cause analysis, and design validation.
  • Provide hands-on technical support for production and existing products, including manufacturing issues, pilot builds, engineering changes, yield improvement, product enhancements, defect reduction, and complex troubleshooting.
  • Partner with Procurement and Supply Chain on component availability, alternate component qualification, obsolescence, supplier technical issues, second sourcing, and cost reduction initiatives.
  • Serve as a Sr technical escalation point for complex product and customer issues, including field failures, returned products, hardware/firmware troubleshooting, root cause analysis, and corrective actions.
  • Partner with Quality to support engineering documentation, design controls, CAPA investigations, configuration management, ISO 9001 requirements, and product certifications including EMC/EMI, FCC, CE, UL, HazLoc, environmental, and reliability testing.
  • Provide team, technical, and organizational guidance to engineering team members, including technical direction, mentoring, prioritization, design reviews, engineering best practices, cross-training, and knowledge sharing to support effective execution and accountability across the team.
  • Work closely with Firmware, Mechanical Engineering, Manufacturing, Supply Chain, Quality, Technical Support, and Operations to prioritize technical issues and ensure successful product development and ongoing product support.

  Qualifications

  • Bachelor's degree in Electrical Engineering or Computer Engineering (required).
  • Master's degree in Electrical Engineering or a related field (preferred).
  • 3–7 years of experience in hardware design and development of embedded electronic products.
  • Proven experience taking products from concept through production and sustaining engineering.
  • Experience supporting manufacturing, production, supply chain, and field technical support.
  • Experience working in cross-functional product development teams.
  • Strong knowledge of analog, digital, and mixed-signal circuit design.
  • Experience with microcontroller-based embedded systems and common communication interfaces (SPI, I²C, UART, CAN, USB, Ethernet).
  • Experience designing power supplies, sensor interfaces, and battery-powered products.
  • Proficiency with schematic capture, PCB design, and PCB layout review using tools such as PADS, Altium Designer, or OrCAD.
  • Familiarity with signal integrity, EMC/EMI mitigation, Design for Manufacturability (DFM), and Design for Testability (DFT).
  • Experience using laboratory equipment, including oscilloscopes, logic analyzers, spectrum analyzers, digital multimeters, and power supplies.
  • Ability to troubleshoot complex hardware issues and perform root cause analysis.
  • Experience with product validation, environmental testing, and regulatory compliance (FCC, CE, UL, EMC, HazLoc preferred).
  • Working knowledge of Engineering Change Notice (ECN) processes, configuration management, and engineering documentation.
  • Familiarity with embedded firmware development and debugging is preferred.
  • Software/middleware expertise – knowledge of python, c, c++, linux systems.