RF Test Technician III

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections where there is real specific content. We need to parse the posting. First, there is an introductory paragraph: "Mercury Systems is seeking the best and brightest talent to help us bring cutting-edge technology to mission-critical aerospace and defense applications, advancing innovation where it matters most. We bridge commercial innovation with defense-grade security to ensure our warfighters and allies have the technological advantage." That could be "About the role" or maybe a summary. We'll put under

About the role

with that paragraph. Then "Job Responsibilities" heading. The responsibilities list includes many bullet-like sentences. We need to extract them into

• . The responsibilities text: "Participating in continuous improvement and team building activities. Maintains productive working relationships with all team membersApplying RF fundamentals including but not limited to RF Gain, Gain Flatness, Gain Matching , Return Loss, P1 dB Compression, phase/phase trackingBeing proficient in RF theory and principalsTesting for gain, gain flatness, noise figure, VSWR, P1dB, IP3 and phaseCalibration of test equipmentTuning and troubleshootingOperating test equipment like PNA-X, MXA, DC power supplies, RF signal generators, scalar analyzer Read , interpret, and follow Customer Specifications and Acceptance Test Procedures Understanding DC theory (Ohm's Law)Following ESD procedures" We need to split into separate items. Likely each sentence separated by period. Let's list: - Participating in continuous improvement and team building activities. - Maintains productive working relationships with all team members - Applying RF fundamentals including but not limited to RF Gain, Gain Flatness, Gain Matching, Return Loss, P1 dB Compression, phase/phase tracking - Being proficient in RF theory and principals - Testing for gain, gain flatness, noise figure, VSWR, P1dB, IP3 and phase - Calibration of test equipment - Tuning and troubleshooting - Operating test equipment like PNA-X, MXA, DC power supplies, RF signal generators, scalar analyzer - Read, interpret, and follow Customer Specifications and Acceptance Test Procedures - Understanding DC theory (Ohm's Law) - Following ESD procedures We'll output as
  • each. Next "Required Qualifications": list: - High School Diploma - Typically 3-5 years testing and tuning RF electronic devices - Familiar with computers (Microsoft Office Suite) - Ability to clearly communicate in written and spoken English We'll put under

    Required Qualifications

    with
    . Then "Preferred Qualifications": list: - Preferred experience in tuning RF micorstrip circuits - Preferred experience in troubleshooting complex DC circuit boards We'll put under

    Preferred Qualifications

    . Then "Physical Demands": This is a section but not in the allowed headings list? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands is not listed; we could possibly map to "Requirements"? But the instruction says use those headings for section headings. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says "use

    for section headings (e.g. ...)" implying those are the allowed headings. Probably we should only use those headings. Physical Demands could be considered part of Requirements or Qualifications? Might be better to omit if not matching allowed headings. However we need to preserve ALL substantive information; we cannot drop Physical Demands if it's substantive. But we could incorporate it under "Requirements" or "Qualifications". The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to map Physical Demands to "Requirements" maybe as a subsection? But we cannot create subheadings; we could just include the physical demands content under Requirements as a list. However the Required Qualifications already separate. Could combine? Might be better to create a section "Requirements" and put both Required Qualifications and Physical Demands there? But the instruction says "include a section ONLY when the posting has real, specific content for it". We have content for Physical Demands, so we need a section. If we don't have a matching heading, we could still use

    Physical Demands

    though not in the examples. The examples are not exhaustive; they say e.g. So we can use Physical Demands as a heading. Likely acceptable. Thus we will include

    Physical Demands

    with list. Then we have security clearance statement: "This position requires you to have a government security clearance. Security clearances may only be granted to U.S. citizens. This position requires you to access information that is subject to U.S. export regulations. You may only access such information if you are a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. government." This is substantive; could be part of Requirements or Qualifications. Could be its own section maybe "Requirements". But we already have Required Qualifications. Could add as another bullet under Required Qualifications? Might be better to include under "Requirements" as a separate bullet list. However we already used Required Qualifications heading. Could we add another heading "Requirements" and put both Required Qualifications and Physical Demands there? But we already used Required Qualifications heading; maybe we should rename to "Requirements" and include both qualifications and physical demands. However the instruction says use headings like Requirements, Qualifications, etc. So we could have separate sections: Requirements (maybe for mandatory qualifications) and Qualifications (maybe for preferred?). But the posting already distinguishes Required Qualifications and Preferred Qualifications. So we could map Required Qualifications to "Requirements" and Preferred Qualifications to "Qualifications". That seems logical. Thus: -

    About the role

    with intro paragraph. -

    Responsibilities

    with list. -

    Requirements

    with Required Qualifications list plus security clearance statements maybe as separate items. -

    Qualifications

    with Preferred Qualifications list. -

    Physical Demands

    with list. -

    Benefits

    with benefits list. -

    Pay

    with salary range details. -

    Schedule

    with mention of 9/80 alternative work schedule. We need to ensure we don't create sections with placeholder text. All have content. Now extract Benefits: "In addition to base salary, Mercury provides a variety of benefits for team members including: bonus opportunities (or special incentives for sales positions); health, life and disability insurance; company-paid holidays and time off; 401(k) retirement plan; discounted employee stock purchase plan; tuition reimbursement; and access to professional development and personal wellness platforms including LinkedIn Learning, Headspace, Aaptiv and Virgin Pulse. Team members at the Director or Vice President level are also eligible to receive annual stock-based awards." We'll list each benefit as
    • . Pay: The posting includes salary ranges: "Fulltime Equivalent Job Grade Salary Range for this position " $44,000.00 - $88,000.00 annual salary for in-office or hybrid employees in FL, GA, IN, AZ, AL, MD or TX, and all remote employees $49,300.00 - $98,600.00 annual salary for in-office or hybrid employees in VA, CA, NH or MA $51,900.00 - $103,800.00 annual salary for in-office or hybrid employees in NJ", Mercury considers a variety of factors to determine individual base salary offers to candidates, including: the role and related responsibilities; prior work experience; education, training, skills and certifications; internal equity with others employed by Mercury in similar roles; geographic location; and alignment with market data." We need to preserve all substantive info. So we will put that as a paragraph under Pay heading. Schedule: "Mercury offers a 9/80 alternative work schedule that provides employees more opportunity for work/ life balance (available based off location)". We'll put as paragraph. Now ensure we remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc. We'll drop that. Also drop "Why should you join Mercury Systems?" etc? That's promotional but maybe considered boilerplate? It's not a standard boilerplate but could be considered marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why should you join Mercury Systems?" and following paragraphs about culture etc might be considered not boilerplate but could be kept? It's not explicitly prohibited. However it's not a standard section heading; we could include under About the role maybe. But we already have About the role intro; we could add more. However to keep concise, we could keep it as part of About the role. But the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that content. However we already used About the role for the first paragraph; we could extend it to include the "Why should you join Mercury Systems?" and "Our Culture" paragraphs. That would be substantive. Thus About the role will contain multiple paragraphs: the initial mission statement, then the "Why should you join Mercury Systems?" paragraph, then "Our Culture" paragraph(s). We'll keep them as separate

      under same heading. Now check for duplicated lines: there may be duplicates like "Mercury Systems is an equal opportunity employer..." which we will drop as EEO boilerplate. Now produce HTML. Structure:

      About the role

      Mercury Systems is seeking the best and brightest talent to help us bring cutting-edge technology to mission-critical aerospace and defense applications, advancing innovation where it matters most. We bridge commercial innovation with defense-grade security to ensure our warfighters and allies have the technological advantage.

      Why should you join Mercury Systems? Mercury Systems is a technology company that makes the world a safer, more secure place. We push processing power to the tactical edge, making the latest commercial technologies profoundly more accessible for today's most challenging aerospace and defense missions. From silicon to system scale, Mercury enables customers to accelerate innovation and turn data into decision superiority. Headquartered in Andover, Massachusetts, Mercury employs more than 2,300 people in 24 locations worldwide. To learn more, visit mrcy.com

      Our Culture We are committed to making Mercury a great place to work, no matter where our employees are located. We offer a casual and enjoyable atmosphere that allows employees to learn and grow. We help and care for one another and work as one to achieve results for us and for our customers. We value communication and transparency, and strive to foster two-way dialogue at all levels of the organization. We are committed to lifelong learning, offering comprehensive skills training and tuition reimbursement. Whether you're just starting out on your career journey or you are an experienced professional, it's important to us that you feel recognized and rewarded for your contributions. To find out more about Why Mercury?, or visit the Mercury Community or find answers to general questions at Mercury FAQs

      Note: The "Our Culture" paragraph seems to have missing punct