Verification Designer
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content.
From posting:
- Position Overview/Mandate: description about verification designer. Could be "About the role". We'll put that under About the role
with paragraph(s).
- "Make an Impact with US:" description of work areas. Could be part of responsibilities? Might be more about role. Could be included in About the role or Responsibilities. We'll decide.
- "What You'll Be Doing:" list of duties. That's responsibilities.
- "Who You are:" list of qualifications/experience. That's requirements/qualifications/skills.
- "Location and travel:" mention fully remote role and travel may be required. That's maybe Schedule? Actually location/travel not pay/schedule. Could be part of About the role? But we have no heading for location. Could drop or put in a short p under About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location/travel is minor metadata, we can fold into a short p. - Benefits: paragraph about benefits. - Pay: not mentioned explicitly. So we should NOT create Pay section. - Schedule: not mentioned. So no Schedule. - Skills: maybe separate from Requirements? Could combine. We'll have sections: About the role, Responsibilities, Requirements, Benefits. We need to preserve all substantive information, not invent. Let's extract: About the role: combine Position Overview/Mandate and Make an Impact with US? Might be two paragraphs. Paragraph 1: "Fidus is a global high-tech design firm headquartered in Ottawa, with additional design centres in Kitchener-Waterloo and San Jose. We specialize in leading-edge electronic product development, with hardware, embedded software, FPGA/ASIC, and signal integrity teams working together to design and deliver next-generation products for clients in emerging technology markets." Paragraph 2: "Position Overview/Mandate: The Verification Designer owns block- and system-level verification of ASIC and FPGA designs for Fidus clients, planning and executing complex verification projects end to end — building UVM, formal, and assertion-based verification environments and driving coverage closure. This role is ideal for someone who takes lead-level ownership of verification strategy, is comfortable moving between different application domains (communications, storage, signal processing, video), and takes pride in producing thorough, well-documented verification work — often working directly with clients on verification approach." Paragraph 3: "Make an Impact with US: At Fidus, you'll work on high-speed, high-complexity electronic systems, often using emerging technologies before they reach the broader market. You'll collaborate across FPGA/DSP, hardware, embedded software, verification, SI/PI, PCB layout, and mechanical/thermal design as part of cross-functional teams delivering real products for our clients. In practice, that means contributing to projects in areas such as space and satellite systems, next-generation communications and networking, high-performance compute and storage platforms, advanced video, imaging, VR/AR applications, and industrial, medical, and automotive systems. You won't be limited to a single product or industry—your work will follow the technology, not just one roadmap." We could combine into About the role. Responsibilities: from "What You'll Be Doing:" bullet list. List items: - Own block- and system-level verification of ASIC and FPGA designs, from test plan development through coverage closure - Design and implement UVM, formal, and assertion-based verification environments, applying constrained-random verification (CRV) techniques - Develop behavioral models and write test cases to achieve functional coverage goals; define and track coverage metrics to closure - Debug and troubleshoot failures in simulation and regression runs, collaborating with designers and system architects to resolve issues - Automate verification tasks and monitor regressions using scripting (Python, Perl, or Tcl) - Plan, execute, and report status on multiple verification activities as a verification lead - Work directly with external clients on verification strategy and support We'll put each as
Requirements
with list of experience, education, etc.Skills
with list of technical skills. But we risk thin sections. However each list is decent. Let's decide: We'll have Requirements (experience + education) and Skills (technical proficiencies). That seems reasonable. Location/travel: we can fold into a short p under About the role or separate? It's minor metadata. We'll add a short p after About the role: "Location: Fully remote; travel may be required domestically and internationally to support customer engagements.
" Benefits: paragraph: "Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits." Also note: "We also recognize that candidates show interest throughout different career stages and welcome all applications. When there is a great fit, the level of the role may be shifted as applicable." That's also part of benefits? It's more about flexibility. Could include in benefits paragraph. We'll put benefits asBenefits
withcontaining that info. Now ensure we don't repeat job title as heading. We didn't. No Pay or Schedule sections. Now output HTML fragment. Let's craft. We need to wrap sections in appropriate tags. Example:
About the role
...
Location: Fully remote; travel may be required domestically and internationally to support customer engagements.
Responsibilities
- ... ...
Requirements
- 8+ years of ASIC/FPGA verification experience, with proven verification-lead ownership — able to plan and execute complex verification projects end to end ...
- Bachelor's or Master's degree in Electrical Engineering, Computer Engineering, or a related field
Skills
- Strong SystemVerilog and UVM methodology fluency, including constrained-random verification (CRV) techniques ...
- Proficiency in scripting languages (Python, Perl, or Tcl) to automate verification tasks ...
Benefits
Our competitive compensation package also includes a comprehensive benefits package, including medical, dental, and vision plans, matching 401(k) contributions, annual profit-sharing bonus, along with other supplementary benefits. We also recognize that candidates show interest throughout different career stages and welcome all applications. When there is a great fit, the level of the role may be shifted as applicable.
Check we didn't miss any substantive info: The "About Fidus & Why Work Here" section includes more about company. That's also substantive but maybe could be part of About the role? It's about company, not role. Could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Could add another section "About Fidus". But we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Fidus" not in list, but we could put under About the role? Might be okay to include as part of About the role? However the instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? It says use