ASIC & FPGA Design Engineer Sr Stf - E5
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
We must not include filler like "commensurate with experience". Not present.
We need to decide sections:
- About the role: could be first paragraph describing role and team.
- Responsibilities: list of duties from "Your responsibilities will include:" bullet list (though it's a sentence with commas). We need to extract each responsibility as list items.
- Requirements: Basic Qualifications list.
- Skills: Desired Skills list.
- Benefits: list of benefits.
- Pay: Salary range.
- Schedule: flexible work schedules mention.
We must ensure we don't create sections with placeholder text. All have content.
We must not include duplicated lines. Ensure we capture each piece once.
Let's extract content.
Original text:
"Job Description You will be the ASIC & FPGA Design Engineer for the Hardware Engineering team at Lockheed Martin Missiles and Fire Control (MFC). Our team delivers precision engagement aerospace and defense systems, designing, building and fielding the electrical hardware that powers missiles, sensors and other mission critical subsystems for the United States and allied militaries. What You Will Be Doing As the ASIC & FPGA Design Engineer you will own the end‑to‑end development of complex, multi‑function FPGA modules. You’ll work side‑by‑side with software, hardware, and systems engineers to shape architecture, define requirements, and drive designs from concept through production. You’ll also serve as a technical mentor, guiding less‑experienced engineers and fostering cross‑disciplinary collaboration. Your responsibilities will include: Architecting complex FPGA designs, including specification, design, verification, and implementationDeveloping trade studies to select an FPGA solution optimized for device utilization, power and thermal requirementsCollaborating with cross-functional teams, including software, hardware, and systems engineering to develop an optimal architecture and develop FPGA requirementsCollaborating with the team through the Design Architecture development processLeading investigations to understand complex programmable logic problems and providing innovative and ingenious solutionsActing independently to uncover and resolve issues associated with the implementation of operational productsMentoring less experienced engineers on our team and collaborating with other engineering disciplinesWorking with technical and manufacturing support personnel to ensure successful product development and production Why Join Us Do you want to be part of a company culture that empowers employees to think big, lead with a growth mindset, and make the impossible a reality? We provide the resources and give you the flexibility to enable inspiration and focus. If you have the passion and courage to dream big, work hard, and have fun doing what you love then we want to build a better tomorrow with you. We offer flexible work schedules to comprehensive benefits investing in your future and security. Learn more about Lockheed Martin’s comprehensive benefits package here. Further Information About This Opportunity This position is in Andover, MA. Discover more about our Chelmsford, Massachusetts location. MUST BE A U.S. CITIZEN - This position is located at a facility that requires special access. The selected candidate must be able to obtain a secret clearance. Basic Qualifications Bachelor of Science or higher from an accredited college in Electrical Engineering or related discipline, or equivalent experience/combined education HDL programming experience with VHDL, Verilog, and/or System Verilog. Experience in Hardware-Software Integration and Validation. Experience with Xilinx FPGAs and related toolsets such as Vivado. Experience with FPGA simulation tools and languages such as Synopsys VCS and SystemVerilog. Strong understanding of digital design principles, including timing analysis, clock domain crossing, and signal integrity. Extensive experience with troubleshooting designs and resolving integration issues. Excellent communication and presentation skills. Candidate must be eligible to obtain a Secret Clearance and be able to obtain at least an Interim Secret Clearance before starting the position, therefore you must be a US Citizen. Desired Skills Master of Science Degree in Electrical Engineering or closely related technical field. Active DoD Secret or Top Secret Clearance Significant relevant experience in the defense electronics industry, including FPGA development for RF systems. Experience with version control systems, such as Git Experience with multiple FPGA vendors, such as Altera or Microchip Knowledge of software programming languages, such as C, C++, or Python Experience with debugging and troubleshooting complex digital systems Knowledge of UVM and experience with UVM-based verification methodologies Experience with the MFC DAR process Experience with Missile systems Experience with Missile Safety Extensive experience with troubleshooting designs and resolving integration issues in a production or manufacturing environment. Expertise with datalink or T/R module architecture. Expertise with technical documentation such as specifications, schematic drawings, and test data. Experience with customer interface including technical presentations. Ability to lead failure investigations on production and/or technical issues. Ability work in a team collaborative environment especially with manufacturing and industrial engineers and/or operator on production support. Pay Information Full-Time Salary Range: $166900.00 - $309900.00 At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer. Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year."
We need to remove boilerplate like "Learn more about Lockheed Martin’s comprehensive benefits package here." That's maybe okay to keep? It's a link reference but not substantive. Might be considered navigation? Probably safe to drop.
Also "Further Information About This Opportunity" heading is not a standard heading; we can incorporate its content into About the role or a separate section like "Location & Requirements". But we must only use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have location and citizenship/clearance info. Could go under About the role (maybe as part of description). Or we could create a "Requirements" section for basic qualifications (including citizenship). But citizenship is more of a requirement. We'll include in Requirements.
We have "Why Join Us" paragraph about culture, flexible work schedules, benefits. That could go under Benefits or Schedule? The flexible work schedules mention is under Benefits offered also. We'll keep flexible work schedules in Benefits (since they list it) and also maybe Schedule section if we have specific schedule info. The posting mentions "We offer flexible work schedules to comprehensive benefits investing in your future and security." Also later "Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), ..." So schedule info is part of benefits. We could still have a Schedule section if we have explicit schedule info like "flexible work schedules". But we already have that in Benefits. The instruction: Prefer a few substantive sections over many thin ones. So maybe we omit Schedule section and keep flexible work schedules under Benefits. However they explicitly said to include Schedule section only if posting actually states them. It does state flexible work schedules. But we could still include Schedule section with that info. But we already have flexible work arrangements in Benefits; duplicating might be redundant. Better to have Schedule section with flexible work schedules info, and Benefits section without that duplicate. But we need to preserve all info; we can mention flexible work schedules in Schedule section and still list other benefits in Benefits section (excluding flexible work arrangements). However the benefits list includes "Flexible work arrangements and schedules (e.g., 4x10)". If we move that to Schedule, we should remove from Benefits to avoid duplication. But we must preserve all substantive information; we can still include it in Schedule and not duplicate in Benefits. That's fine.
Thus:
- About the role: introductory paragraphs describing role, team, mission, what you will be doing (maybe up to "Your responsibilities will include:" but we separate responsibilities). So About the role includes first two paragraphs: "Job Description You will be the ASIC & FPGA Design Engineer..." and "What You Will Be Doing As the ASIC & FPGA Design Engineer you will own the end‑to‑end development..." plus maybe the "Why Join Us" culture paragraph? Actually "Why Join Us" is more about company culture; could be part of About the role or separate but we don't have a heading for culture. We'll include it in About the role as it's descriptive.
- Responsibilities: list items from "Your responsibilities will include:" we need to split by the conjunctions. The text after colon: "Architecting complex FPGA designs, including specification, design, verification, and implementationDeveloping trade studies to select an FPGA solution optimized for device utilization, power and thermal requirementsCollaborating with cross-functional teams, including software, hardware, and systems engineering to develop an optimal architecture and develop FPGA requirementsCollaborating with the team through the Design Architecture development processLeading investigations to understand complex programmable logic problems and providing innovative and ingenious solutionsActing independently to uncover and resolve issues associated with the implementation of operational productsMentoring less experienced engineers on our team and collaborating with other engineering disciplinesWorking with technical and manufacturing support personnel to ensure successful product development and production"
We need to separate each responsibility. They are separated by capital letters? Actually each starts with a verb: Architecting..., Developing..., Collaborating..., Collaborating..., Leading..., Acting..., Mentoring..., Working... There's a duplicate Collaborating phrase appears twice; but we should keep both as they are distinct? The first Collaborating: "Collaborating with cross-functional teams, including software, hardware, and systems engineering to develop an optimal architecture and develop FPGA requirements". Second: "Collaborating with the team through the Design Architecture development process". They are similar but distinct; we keep both.
Thus we will create
- for each.
- Requirements: Basic Qualifications list. Items:
* Bachelor of Science or higher from an accredited college in Electrical Engineering or related discipline, or equivalent experience/combined education
* HDL programming experience with VHDL, Verilog, and/or System Veril
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must not include filler like "commensurate with experience". Not present. We need to decide sections: - About the role: could be first paragraph describing role and team. - Responsibilities: list of duties from "Your responsibilities will include:" bullet list (though it's a sentence with commas). We need to extract each responsibility as list items. - Requirements: Basic Qualifications list. - Skills: Desired Skills list. - Benefits: list of benefits. - Pay: Salary range. - Schedule: flexible work schedules mention. We must ensure we don't create sections with placeholder text. All have content. We must not include duplicated lines. Ensure we capture each piece once. Let's extract content. Original text: "Job Description You will be the ASIC & FPGA Design Engineer for the Hardware Engineering team at Lockheed Martin Missiles and Fire Control (MFC). Our team delivers precision engagement aerospace and defense systems, designing, building and fielding the electrical hardware that powers missiles, sensors and other mission critical subsystems for the United States and allied militaries. What You Will Be Doing As the ASIC & FPGA Design Engineer you will own the end‑to‑end development of complex, multi‑function FPGA modules. You’ll work side‑by‑side with software, hardware, and systems engineers to shape architecture, define requirements, and drive designs from concept through production. You’ll also serve as a technical mentor, guiding less‑experienced engineers and fostering cross‑disciplinary collaboration. Your responsibilities will include: Architecting complex FPGA designs, including specification, design, verification, and implementationDeveloping trade studies to select an FPGA solution optimized for device utilization, power and thermal requirementsCollaborating with cross-functional teams, including software, hardware, and systems engineering to develop an optimal architecture and develop FPGA requirementsCollaborating with the team through the Design Architecture development processLeading investigations to understand complex programmable logic problems and providing innovative and ingenious solutionsActing independently to uncover and resolve issues associated with the implementation of operational productsMentoring less experienced engineers on our team and collaborating with other engineering disciplinesWorking with technical and manufacturing support personnel to ensure successful product development and production Why Join Us Do you want to be part of a company culture that empowers employees to think big, lead with a growth mindset, and make the impossible a reality? We provide the resources and give you the flexibility to enable inspiration and focus. If you have the passion and courage to dream big, work hard, and have fun doing what you love then we want to build a better tomorrow with you. We offer flexible work schedules to comprehensive benefits investing in your future and security. Learn more about Lockheed Martin’s comprehensive benefits package here. Further Information About This Opportunity This position is in Andover, MA. Discover more about our Chelmsford, Massachusetts location. MUST BE A U.S. CITIZEN - This position is located at a facility that requires special access. The selected candidate must be able to obtain a secret clearance. Basic Qualifications Bachelor of Science or higher from an accredited college in Electrical Engineering or related discipline, or equivalent experience/combined education HDL programming experience with VHDL, Verilog, and/or System Verilog. Experience in Hardware-Software Integration and Validation. Experience with Xilinx FPGAs and related toolsets such as Vivado. Experience with FPGA simulation tools and languages such as Synopsys VCS and SystemVerilog. Strong understanding of digital design principles, including timing analysis, clock domain crossing, and signal integrity. Extensive experience with troubleshooting designs and resolving integration issues. Excellent communication and presentation skills. Candidate must be eligible to obtain a Secret Clearance and be able to obtain at least an Interim Secret Clearance before starting the position, therefore you must be a US Citizen. Desired Skills Master of Science Degree in Electrical Engineering or closely related technical field. Active DoD Secret or Top Secret Clearance Significant relevant experience in the defense electronics industry, including FPGA development for RF systems. Experience with version control systems, such as Git Experience with multiple FPGA vendors, such as Altera or Microchip Knowledge of software programming languages, such as C, C++, or Python Experience with debugging and troubleshooting complex digital systems Knowledge of UVM and experience with UVM-based verification methodologies Experience with the MFC DAR process Experience with Missile systems Experience with Missile Safety Extensive experience with troubleshooting designs and resolving integration issues in a production or manufacturing environment. Expertise with datalink or T/R module architecture. Expertise with technical documentation such as specifications, schematic drawings, and test data. Experience with customer interface including technical presentations. Ability to lead failure investigations on production and/or technical issues. Ability work in a team collaborative environment especially with manufacturing and industrial engineers and/or operator on production support. Pay Information Full-Time Salary Range: $166900.00 - $309900.00 At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer. Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year." We need to remove boilerplate like "Learn more about Lockheed Martin’s comprehensive benefits package here." That's maybe okay to keep? It's a link reference but not substantive. Might be considered navigation? Probably safe to drop. Also "Further Information About This Opportunity" heading is not a standard heading; we can incorporate its content into About the role or a separate section like "Location & Requirements". But we must only use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have location and citizenship/clearance info. Could go under About the role (maybe as part of description). Or we could create a "Requirements" section for basic qualifications (including citizenship). But citizenship is more of a requirement. We'll include in Requirements. We have "Why Join Us" paragraph about culture, flexible work schedules, benefits. That could go under Benefits or Schedule? The flexible work schedules mention is under Benefits offered also. We'll keep flexible work schedules in Benefits (since they list it) and also maybe Schedule section if we have specific schedule info. The posting mentions "We offer flexible work schedules to comprehensive benefits investing in your future and security." Also later "Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), ..." So schedule info is part of benefits. We could still have a Schedule section if we have explicit schedule info like "flexible work schedules". But we already have that in Benefits. The instruction: Prefer a few substantive sections over many thin ones. So maybe we omit Schedule section and keep flexible work schedules under Benefits. However they explicitly said to include Schedule section only if posting actually states them. It does state flexible work schedules. But we could still include Schedule section with that info. But we already have flexible work arrangements in Benefits; duplicating might be redundant. Better to have Schedule section with flexible work schedules info, and Benefits section without that duplicate. But we need to preserve all info; we can mention flexible work schedules in Schedule section and still list other benefits in Benefits section (excluding flexible work arrangements). However the benefits list includes "Flexible work arrangements and schedules (e.g., 4x10)". If we move that to Schedule, we should remove from Benefits to avoid duplication. But we must preserve all substantive information; we can still include it in Schedule and not duplicate in Benefits. That's fine. Thus: - About the role: introductory paragraphs describing role, team, mission, what you will be doing (maybe up to "Your responsibilities will include:" but we separate responsibilities). So About the role includes first two paragraphs: "Job Description You will be the ASIC & FPGA Design Engineer..." and "What You Will Be Doing As the ASIC & FPGA Design Engineer you will own the end‑to‑end development..." plus maybe the "Why Join Us" culture paragraph? Actually "Why Join Us" is more about company culture; could be part of About the role or separate but we don't have a heading for culture. We'll include it in About the role as it's descriptive. - Responsibilities: list items from "Your responsibilities will include:" we need to split by the conjunctions. The text after colon: "Architecting complex FPGA designs, including specification, design, verification, and implementationDeveloping trade studies to select an FPGA solution optimized for device utilization, power and thermal requirementsCollaborating with cross-functional teams, including software, hardware, and systems engineering to develop an optimal architecture and develop FPGA requirementsCollaborating with the team through the Design Architecture development processLeading investigations to understand complex programmable logic problems and providing innovative and ingenious solutionsActing independently to uncover and resolve issues associated with the implementation of operational productsMentoring less experienced engineers on our team and collaborating with other engineering disciplinesWorking with technical and manufacturing support personnel to ensure successful product development and production" We need to separate each responsibility. They are separated by capital letters? Actually each starts with a verb: Architecting..., Developing..., Collaborating..., Collaborating..., Leading..., Acting..., Mentoring..., Working... There's a duplicate Collaborating phrase appears twice; but we should keep both as they are distinct? The first Collaborating: "Collaborating with cross-functional teams, including software, hardware, and systems engineering to develop an optimal architecture and develop FPGA requirements". Second: "Collaborating with the team through the Design Architecture development process". They are similar but distinct; we keep both. Thus we will create
- for each. - Requirements: Basic Qualifications list. Items: * Bachelor of Science or higher from an accredited college in Electrical Engineering or related discipline, or equivalent experience/combined education * HDL programming experience with VHDL, Verilog, and/or System Veril