Senior Hardware Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like contact email, website, repeated lines, EEO, etc. Also remove duplicated lines. Preserve all substantive info. We need to parse the posting. Let's extract sections: - Job Functions (list of duties). That's responsibilities. - Requirements (list of requirements). - Qualifications (list of qualifications). - Employee Health & Safety Compliance (maybe not a standard heading; could be part of Requirements? It's about compliance; maybe we can put under Requirements or a separate section? The instruction says use headings for standard sections; we can include a section only if posting has real specific content. Health & Safety compliance is specific content; but not one of the standard headings list. However we could treat it as part of Requirements or maybe as a separate section like "Health & Safety". But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. ...). Likely they expect only those headings. But we could still include other headings if needed? Safer to stick to those. Health & Safety compliance could be placed under Requirements or maybe under About the role? Probably under Requirements as it's a requirement. - About HENSOLDT UK: that's about the company; could be "About the role"? Actually "About the role" is about the job, not company. But we have no explicit "About the role" content. Could we create an "About the role" section from the job functions? Might be redundant. Better to not create empty sections. We have Responsibilities (Job Functions), Requirements, Qualifications. Possibly Skills could be extracted from requirements (interpersonal skills, teamwork, organization, self-motivation, English, etc). But we already have Requirements covering those. Could separate Skills as a separate section but might duplicate. The instruction: prefer a few substantive sections over many thin ones. So we can combine skills into Requirements. Pay, Schedule, Benefits: not present. So omit those sections. Thus we will have sections: Responsibilities, Requirements, Qualifications. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to list each duty exactly as in posting. Let's extract duties from "Job Functions" paragraph: "Design high speed digital designs and simulate the analogue sections. Knowledge of Orcad and Altium schematic entry and layout would be advantageous. Knowledge of multilayer PCB design, layout and signal integrity Working experience of FPGAs using VHDL/Embedded C to bridge firmware/hardware design would be distinct advantageous Programming experience in MATLAB Experience using scripts to configure and test designs with a high Software content Experience interfacing and configuring RF and associated design would be advantageous Hardware Test and verification of new electronic assemblies and sub-assemblies. Use of Silicon Expert to pre-empt obsolescence and / or long lead item issues. Product support and troubleshooting of existing electronic assemblies and sub-assemblies. Acting as an interface between Engineering and manufacturing with respect to Introduction of hardware test solutions. Involvement in a product through its development lifecycle, including initial design, development, test, and report writing. Translates system requirement specifications into board-level designs; ensures robust verification, including writing of test specifications and circuit descriptions. Owns technical task breakdown and identification of key risks Participation in Design Reviews and appropriate use of Configuration Control. Travel within the UK may be required and is considered an occasional feature of this role. Requests could be made at short notice. Any other tasks associated with this role." We need to keep each as list items. Some sentences are fragments; we keep them as is. Now Requirements: "Sound inter-personal skills. Ability to work effectively within a team. Organisation and time management Self-motivational skills Evidence of producing high quality, right first-time designs on time and within budget Good command of written and verbal English Experience working on similar electronic equipment. Experience with CAD tools for circuit / PCB design and simulation" Also maybe "Employee Health & Safety Compliance" content: we need to incorporate that as part of Requirements? It's a separate paragraph about compliance. It includes: "The job holder will be expected to comply with any reasonable operational instruction or procedures relating to Company policies, reporting and controls. Section 7 of the Health and Safety at Work Act 1974 provides a duty on every employee, while at work, to take reasonable care for the health and safety of themselves and of other persons who may be affected by their acts or omissions at work. It also places a duty on employees to cooperate with their employer so far as is necessary to enable their duties to be complied with including the appropriate use of personal protective equipment (PPE). Failure to comply with this duty may result in the Company invoking the disciplinary procedure." We should preserve that as a requirement. Could be a list item or prose. Since it's a paragraph, we can put as

  under Requirements section. But the instruction says use

  • for any list of duties/requirements/benefits, and

    for prose. So we can treat the compliance as prose. Thus Requirements section will have a

    for the bullet list items, and a

    for the compliance paragraph. Now Qualifications: "A good quality degree or equivalent in electronics related subject" That's it. Now we need to ensure we don't include boilerplate: contact email, website, repeated lines, duplicated lines. The posting had repeated contact lines at start and end; we remove them. Also remove "About HENSOLDT UK" paragraph? That's company info; not required as a section. Could we include as "About the role"? Not exactly. The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have company description; but we don't have a standard heading for company. Could we treat as "About the role"? Not accurate. Better to omit it, as it's not a standard heading and we don't want to invent headings. The instruction says we can use headings for those examples; but doesn't forbid other headings. However to be safe, we could include an "About the company" section using

    About the company

    . But the instruction didn't list that as example; but they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we could add a section for company info. However they also said "Prefer a few substantive sections over many thin ones." Adding a company section would be another section; but it's substantive. Might be okay. However the user likely expects only the standard sections. The typical tasks: reformat job posting into clean HTML with those headings. They likely expect only those headings that have content. Company description might be considered "About the role"? Not exactly. But many job postings have an "About the company" section; they didn't list it but could be included. However they said "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." They didn't mention company info. I'd lean to include company info under a heading like "About HENSOLDT" or "About the company". But to be safe, maybe we can incorporate that into a brief

    under Responsibilities? Not appropriate. Given the instruction to prefer few substantive sections, we could omit company info as it's not essential to the role. But they said preserve ALL substantive information. Company description is substantive. So we should preserve it. We need to decide where to put it. Could create a section

    About the company

    . That seems reasonable. Thus sections: About the company, Responsibilities, Requirements, Qualifications. We must not include Pay, Schedule, Benefits. Now format. We need to output only HTML fragment, no /, no markdown. Let's craft:

    About the company

    HENSOLDT UK, a trading name of Kelvin Hughes Limited, is a world leader in the development, manufacture and supply of maritime navigation and surveillance radar systems. HENSOLDT UK employs over 170 employees and is headquartered in Enfield, North London. The company sets the international standard in solid state radar sensor technology with SharpEye and its market leading navigation and tactical radar display systems.

    Note: we need to preserve the info exactly; we can combine sentences. Now Responsibilities:

    Responsibilities

    • Design high speed digital designs and simulate the analogue sections.
    • Knowledge of Orcad and Altium schematic entry and layout would be advantageous.
    • Knowledge of multilayer PCB design, layout and signal integrity
    • Working experience of FPGAs using VHDL/Embedded C to bridge firmware/hardware design would be distinct advantageous
    • Programming experience in MATLAB
    • Experience using scripts to configure and test designs with a high Software content
    • Experience interfacing and configuring RF and associated design would be advantageous
    • Hardware Test and verification of new electronic assemblies and sub-assemblies.
    • Use of Silicon Expert to pre-empt obsolescence and / or long lead item issues.
    • Product support and troubleshooting of existing electronic assemblies and sub-assemblies.
    • Acting as an interface between Engineering and manufacturing with respect to Introduction of hardware test solutions.
    • Involvement in a product through its development lifecycle, including initial design, development, test, and report writing.
    • Translates system requirement specifications into board-level designs; ensures robust verification, including writing of test specifications and circuit descriptions.
    • Owns technical task breakdown and identification of key risks
    • Participation in Design Reviews and appropriate use of Configuration Control.
    • Travel within the UK may be required and is considered an occasional feature of this role.
    • Requests could be made at short notice.
    • Any other tasks associated with this role.
    Now Requirements:

    Requirements

    • Sound inter-personal skills.
    • Ability to work effectively within a team.
    • Organisation and time management
    • Self-motivational skills
    • Evidence of producing high quality, right first-time designs on time and within budget
    • Good command of written and verbal English
    • Experience working on similar electronic equipment.
    • Experience with CAD tools for circuit / PCB design and simulation

    The job holder will be expected to comply with any reasonable operational instruction or procedures relating to Company policies, reporting and controls. Section 7 of the Health and Safety at Work Act 1974 provides a duty on every employee, while at work, to take reasonable care for the health and safety of themselves and of other persons who may be affected by their acts or omissions at work. It also places a duty on employees to cooperate with their employer so far as is necessary to enable their duties to be complied with including the appropriate use of personal protective equipment (PPE). Failure to comply with this duty may result in the Company invoking the disciplinary procedure.

    Now Qualifications:

    Qualifications

    A good quality degree or equivalent in electronics related subject

    Check for any duplicated lines: we removed repeated contact lines and