Senior FPGA Design and Verification Engineer
for section headings.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Other" heading? It's not a standard heading; we can incorporate its content into appropriate sections (like Schedule, Benefits, etc.). The "Other" paragraph includes location, remote work, physical demands, travel, vision abilities, exposure to magnetic fields, etc. We'll incorporate those into Schedule (remote/onsite) and maybe a separate "Working Conditions" but not a standard heading; we could put under Schedule or maybe a new section like "Work Environment" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put location/remote under Schedule. Physical demands maybe also under Schedule or could be omitted? It's substantive; we could include under Schedule as part of work arrangement. Or we could create a separate section not in list? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should prefer those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. So we can put physical demands under Schedule? Might be a stretch but okay. Or we could omit physical demands if not fitting. But we must preserve ALL substantive information. So we need to include it somewhere. Could add a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. So we can put physical demands under Schedule? Might be a stretch but okay. Or we could omit physical demands if not fitting. But we must preserve ALL substantive information. So we need to include it somewhere. Could add a
under Schedule describing remote/onsite, physical demands, travel, vision abilities, exposure. That seems okay. Now structure:
About the role
with the introductory paragraphs (Introduction of the job, FPGA Design and Verification Engineer description). We'll combine the intro paragraphs into proseelements. Then
Responsibilities
with the "Role and Responsibilities" content (the bullet-like paragraphs). We'll convert each sentence or clause into- . Must preserve all detail.
Then
- . Might be long; we can group categories but still as list items.
We must not include placeholder like "commensurate with experience". Not present.
Benefits: medical, dental, vision, basic life insurance, 401k, vacation leave 8 hours per month, 13 paid holidays.
Schedule: flexible workplace arrangement remote up to two days a week, onsite presence required for in-person work-related events, trainings, meetings; routinely required to sit; walk; talk; hear; use hands to keyboard, finger, handle, and feel; stoop, kneel, crouch, twist, reach, and stretch; occasionally required to move around the campus; occasionally lift and/or move up to 20 pounds; may require travel (domestic and/or international) dependent on business needs; specific vision abilities required: close vision, color vision, peripheral vision, depth perception, ability to adjust focus; potential exposure to strong magnetic fields, high voltage and currents.
We should not include Pay section because salary range is placeholder $0-0.
We must not include any boilerplate like "EEO", "Equal Opportunity Employer", etc. Remove those lines.
Also remove "Additional Responsibilities:"? Actually that is part of Other section about exposure to magnetic fields etc. We'll incorporate.
Now produce HTML fragment.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
As an FPGA Design and Verification Engineer, you will specify, design, develop, realize, integrate, and test modules and tools in a multi-disciplined team, collaborating closely with cross-functional partners and suppliers. You will deliver within system specifications, cost targets, and project schedules, ensuring timely realization of solutions that contribute to competitive, achievable, and serviceable products. The FPGA Firmware Engineer provides discipline specific expertise throughout the entire product life cycle. This includes concept feasibility, new product introduction, existing product sustainment and customer facing problem resolution. The position requires highly motivated, extremely organized, and self-driven individuals. The FPGA Design and Verification Engineer will be responsible for definition, design, verification, and documentation for Field Programmable Gate Arrays. They will provide RTL design, simulation, physical implementation and verification of complex FPGA modules comprising a mix of custom RTL with hard and soft vendor IP cores within a larger architecture.
Then maybe another paragraph for Design, Technical Writing, Test, Verification & Integration details. We'll incorporate all. Better to keep as multipleunder About the role. Let's extract the paragraphs from the "Introduction of the job" and the sections under Design, Technical Writing, Test, Verification & Integration. We'll produce a few
elements. Now Responsibilities: we have a big block starting "Role and Responsibilities". We'll break into list items. We'll need to capture each sentence as separate
- . Let's list them:
- Identify, analyze, document, and manage requirements with traceability, and coordinate verification criteria to confirm deliverables meet intent.
- Conduct research and feasibility studies, document findings, and translate results into recommendations, tradeoffs, and decision inputs.
- Develop engineering concepts and solutions, make technical choices, and resolve issues to meet functionality, performance, cost, and compliance needs.
- Define and communicate specifications and high-level designs, align interfaces, and support reviews and approvals to enable quality execution.
- Support system or product integration by coordinating dependencies, applying configuration management, and enabling smooth project execution.
- Define and execute validation and test approaches, improve methods and procedures, and ensure qualification evidence supports release readiness.
- Estimate effort, plan and track work, manage risks and dependencies, and deliver assigned work packages or projects to agreed quality and timelines.
- Maintain accurate technical documentation, share knowledge through coaching and mentoring as applicable, and follow EHS policies while identifying and mitigating safety risks.
That seems comprehensive.
Now Requirements: Bachelor degree in Electrical Engineering required. MS or PhD preferred. Minimum of 4 years of relevant work experience required.
Now Skills: We'll need to list Technical & functional skills, Preferred Skills, Behavioral & leadership skills.
We can break into categories but still as list items; maybe we can have subheadings? Not allowed; only
for sections. So we can just list all skills as
- items. Let's extract: Technical & functional skills: - Requirements, Interfaces & Technical Specification Management: Ability to identify, analyze, document, and manage requirements with traceability, translate them into clear specifications, and align interfaces so engineering deliverables meet intent and enable reliable downstream design, integration, and verification - Engineering Solution Development (Electrical): Ability to develop engineering concepts and solutions, make sound technical tradeoffs, resolve issues, and realize designs that meet functionality, performance, cost, compliance, and schedule constraints within system/module specifications. - Preferred Skills in Embedded Logic and Firmware Design and Verification includes: - Highly proficient use and understanding of FPGA engineering concepts, principles, and theories - Highly proficient in FPGA design languages and tools including VHDL and UVM or OSVVM (Altera High Level Synthesis is preferred) - Experience with FPGA development software - (Modelsim, Quartus, Mentor CDC is preferred) - Highly proficient in Microsoft Office applications - Experience with FPGA SoC, including Avalon and AXI architectures - Experience with architecting and implementing embedded processors including NIOS - Proficient in implementing IP blocks based on interface requirements and designing the required interface logic to overall FPGA architecture - Expertise using VHDL for implementation and verification of FPGA designs - Basic knowledge of signal algorithms - Preferred knowledge and experience using design software and technical tools includes: VHDL, System Verilog, UVM Questa Sim, Modelsim, Quartus GIT, JIRA MATLAB and SimuLink Electronic Laboratory Equipment LabVIEW Python - Integration, Verification & Validation (V&V) Execution: Ability to plan and execute verification and validation, ensure qualification evidence supports release readiness, and support system/product integration by coordinating dependencies and applying disciplined configuration/traceability to deliver working, testable solutions. Behavioral & leadership skills: - Drives Results: The ability to translate strategic and technical goals into clear priorities, execution plans, and measurable outcomes, delivering committed results on time and with the right quality by taking ownership, managing trade-offs, removing obstacles, and sustaining momentum across stakeholders and dependencies. - Demonstrates Self-awareness: The ability to understand and manage one’s own strengths, limitations, emotions, and impact on others; to actively seek and use feedback; and to adapt behaviors and decisions to improve collaboration, leadership effectiveness, and results, especially in high-pressure, ambiguous, or complex environments. - Values Differences: The ability to intentionally seek, respect, and integrate diverse perspectives and working styles to strengthen collaboration and decision quality, ensuring all voices are heard and treated equitably, and enabling inclusive execution across cross-functional and multicultural stakeholders. - Builds Effective Teams: Helps align and enable the team dynamic by clarifying shared goals, roles, dependencies, and ways of working. Fosters trust and inclusion by promoting open dialogue, healthy conflict resolution, inclusion, and mutual accountability. Coaches colleagues to strengthen individual and team capability. - Drives Vision and Purpose: Translates broader direction into clear priorities and practical next steps for a team or technical scope. Builds alignment on goals and trade-offs, communicates context during change or ambiguity, and helps others maintain focus on shared outcomes. We'll need to strip the markup like {{b}} {{/b}} etc. Those appear in the text; we should remove them. Now Benefits: medical, dental, vision, basic life insurance, 401k plan, vacation leave 8 hours per month, 13 paid holidays. Schedule: flexible workplace arrangement remote up to two days a week, onsite presence required for in-person work-related events, trainings, meetings; routinely required to sit; walk; talk; hear; use hands to keyboard, finger, handle, and feel; stoop, kneel, crouch, twist, reach, and stretch; occasionally required to move around the campus; occasionally lift and/or move up to 20 pounds; may require travel (domestic and/or international) dependent on business needs; specific vision abilities required: close vision, color vision, peripheral vision, depth perception, ability to adjust focus; potential exposure to strong magnetic fields, high voltage and currents. Now we need to ensure we didn't include any boilerplate like "EEO", "Equal Opportunity Employer", "Inclusion and diversity", "Need to