Hardware Engineer Program Manager - Compliance

We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, we have "Who We Are" description: that's not a heading we need; we can include as prose maybe under a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "Verkada Is An Equal Opportunity Employer" etc. We need to include sections only when posting has real specific content. Let's extract content: - About the role: there is a section "About The Role" describing role: Engineering Program Manager - Compliance on Hardware team, leading certification efforts, partnering with hardware, mechanical, software, product, supply chain, legal, owning regulatory efforts from concept definition through mass production & shipping globally. Also mention in-office culture: requires on-site at office in San Mateo, CA 5 days a week. That's schedule info (5 days onsite). So schedule: "This role requires that you be on-site at our office in San Mateo, CA 5 days a week." - Responsibilities: "What You'll Do" bullet list: Lead certification efforts for next generation of life safety & security products. Work directly with RF/EMC labs and NRTLs (TUV, UL, Intertek, etc) to test and certify our products to applicable standards. Collaborate with Product, HW, and SW counterparts to translate standards into clear product requirements and test plans to support global market access. Drive key compliance related deliverables. Define key requirements, develop test plans, own technical documentation, and coordinate various testing efforts with external labs or regulatory bodies. Steer all-new hardware products through a growing set of global compliance. - Requirements: "What You Bring": BS in Engineering. 3-5 years experience in certifying electronic end devices for RF, EMC and Safety. Experience working with NRTLs (Intertek, UL, etc) to coordinate testing and obtain certifications. Strong track record of success developing, manufacturing and shipping new electronic products. Excellent organizational skills and written and verbal communication. Flexible and adaptive in a fast-paced startup environment. Ability to travel domestically up to 10%. Must be willing and able to commute 5 days in office. Bonus: Experience working with overseas vendors & an international supply chain. Experience with safety standards relevant to Verkada including but not limited UL 2610, UL 864, EN 50131. Experience obtaining cybersecurity certifications including but not limited to EU Radio Equipment Directive, ER 01, and the Cyber Resiliency Act. - Qualifications: Might be overlapping with Requirements. The posting doesn't have a separate "Qualifications" heading; but we could treat "What You Bring" as qualifications. However we need to follow instruction: include a section only when posting has real specific content for it. There's no explicit "Qualifications" heading, but we could still include a Qualifications section if we think the content fits. But better to map: "What You Bring" could be considered Requirements and Qualifications both. But we have separate sections for Requirements and Qualifications; we could split: Requirements: BS in Engineering, 3-5 years experience, experience with NRTLs, strong track record, excellent organizational skills, communication, flexible, ability to travel up to 10%, willing to commute 5 days in office. Qualifications: Bonus experience with overseas vendors, international supply chain, experience with safety standards UL 2610, UL 864, EN 50131, experience obtaining cybersecurity certifications EU Radio Equipment Directive, ER 01, Cyber Resiliency Act. However the posting lumps them together; but we can still separate as we see fit as long as we preserve all info and not invent. It's okay to split. - Skills: Not explicitly listed; but we could infer from requirements: excellent organizational skills, written and verbal communication, flexible/adaptive, etc. Could put under Skills. But we need to avoid creating sections with filler. If we don't have explicit skills list, maybe we omit Skills section. However we could include Skills as part of Requirements or Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they ask to use headings for those categories if content exists. We have content for Requirements (mandatory) and Qualifications (bonus). So we can have both. - Benefits: There's a section "US Employee Benefits" with detailed list. So we include Benefits. - Pay: There's "Annual Pay Range" with estimated range $140,000—$210,000 USD. Also mention additional forms of compensation: sales incentives, discretionary bonuses, equity RSUs. So we include Pay. - Schedule: Already mentioned: on-site 5 days a week in San Mateo, CA. Also mention ability to travel domestically up to 10%. So schedule includes that. - About the role: we have a paragraph. We also have "Additional Information": visa sponsorship. That's minor metadata; we could fold into a short p or drop. Probably include as a short p under maybe Additional Information but not a heading. Since we only output headings for the specified categories, we can include that info in a

after the sections or within About the role? Better to add a short p after sections maybe labeled as "Additional Information". But not a heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include visa sponsorship as a short p. We must remove boilerplate: EEO statement, "Verkada Is An Equal Opportunity Employer", "Your application will be handled..." etc. Also remove "Additional Information" heading? Actually "Additional Information" is a heading in the posting but not in our allowed list; we can treat its content as minor metadata and fold into a p. We must not include markdown code fences. Output only HTML fragment. Let's craft:

About the role

As an Engineering Program Manager - Compliance on our Hardware team, you will lead certification efforts for Verkada’s newest safety & security products. Engineering Program Managers partner with our Hardware Engineers, Mechanical Engineers, Software Engineers, Product Managers, Supply Chain, and Legal to navigate the new product introduction process; you will own regulatory efforts from concept definition through to mass production & shipping across the globe. We are committed to a thriving in-office culture. This role requires that you be on-site at our office in San Mateo, CA 5 days a week.

Responsibilities

• Lead certification efforts for our next generation of life safety & security products.
• Work directly with RF/EMC labs and NRTLs (TUV, UL, Intertek, etc) to test and certify our products to applicable standards.
• Collaborate with Product, HW, and SW counterparts to translate standards into clear product requirements and test plans to support global market access.
• Drive key compliance related deliverables.
• Define key requirements, develop test plans, own technical documentation, and coordinate various testing efforts with external labs or regulatory bodies.
• Steer all-new hardware products through a growing set of global compliance.

Requirements

• BS in Engineering.
• 3-5 years experience in certifying electronic end devices for RF, EMC and Safety.
• Experience working with NRTLs (Intertek, UL, etc) to coordinate testing and obtain certifications.
• Strong track record of success developing, manufacturing and shipping new electronic products.
• Excellent organizational skills and written and verbal communication.
• Flexible and adaptive in a fast-paced startup environment.
• Ability to travel domestically up to 10%.
• Must be willing and able to commute 5 days in office.

Qualifications

• Experience working with overseas vendors & an international supply chain.
• Experience with safety standards relevant to Verkada including but not limited to UL 2610, UL 864, EN 50131.
• Experience obtaining cybersecurity certifications including but not limited to EU Radio Equipment Directive, ER 01, and the Cyber Resiliency Act.

Benefits

• Healthcare programs that can be tailored to meet the personal health and financial well-being needs - Premiums are 100% covered for the employee under at least one plan and 80% for family premiums under all plans.
• Nationwide medical, vision and dental coverage.
• Starting January 2027, Verkada will match a portion of an employee’s 401(k) contributions based on eligible earnings. Match vests on 2 year anniversary.
• Health Saving Account (HSA) with annual employer contributions and Flexible Spending Account (FSA) with tax saving options.
• Expanded mental health support.
• Paid parental leave policy & fertility benefits.
• Time off to relax and recharge through our paid holidays, firmwide extended holidays, flexible PTO and personal sick time.
• Professional development stipend.
• Wellness/fitness benefits.
• Healthy lunches provided daily.
• Commuter benefits.

Pay

Estimated Annual Pay Range $140,000—$210,000 USD (base compensation and commissions if applicable). Additional forms of compensation may include sales incentives, discretionary bonuses, and/or equity in the form of restricted stock units (RSUs).

Schedule

On‑site requirement: 5 days per week at the San Mateo, CA office. Ability to travel domestically up to 10%.

Additional information: Verkada sponsors and takes over sponsorship of employment visas for this role; reasonable efforts will be made to obtain a visa if an offer is made.

Check for any duplicated content: we have schedule mention also in About the role; but it's okay to repeat? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Repeating is okay but maybe we should avoid duplication. However the About the role paragraph already mentions the on-site requirement. We could keep it there and not repeat in Schedule, but schedule section should still have the schedule specifics; we could keep schedule section with travel info only. But the schedule section currently includes on-site requirement and travel. To avoid duplication, we could keep About the role paragraph as is (including on-site) and schedule section only mention travel. However the schedule section heading expects schedule content; we can include both but it's duplication. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. Better to avoid duplication: keep on-site in About the role, and schedule section only mention travel. Let's adjust. Update About the role paragraph: keep the on-site sentence. Then schedule section:

Ability to travel domestically up to 10%.

Now check that we haven't missed any substantive info: The "What You'll Do" list includes "Steer all-new hardware products through a growing set of global compliance." That's kept. The "What You