Engineering Technologist, Electrical
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat job title as heading (already shown).
- Do NOT put Job ID / requisition numbers as headings.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- IMPORTANT: Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no `/`, no markdown code fences.
2. **Analyze the Input Text:**
Let me carefully go through the provided job posting text, identify sections, extract substantive content, and ignore/remove boilerplate/instructions.
Input text segments:
- "APPLICATION INSTRUCTIONS: CURRENT PENN STATE EMPLOYEE..." -> Remove (application instructions)
- "CURRENT PENN STATE STUDENT..." -> Remove
- "If you are NOT a current employee or student..." -> Remove
- "Approval of remote and hybrid work is not guaranteed..." -> Could be a short prose note, but maybe fold into location/notes. I'll consider if it's substantive enough. The rules say remove application instructions, but this is a note about remote work. I'll see.
- "POSITION SPECIFICS Your working location will be fully on-site in State College, PA. Questions related to flexible work should be directed to the hiring manager during the interview process. This role requires periodic travel to remote locations." -> Keep as prose or section. "POSITION SPECIFICS" isn't a heading I must use; I can create my own headings based on content. The rules say use `
` for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should map content to these meaningfully, or create relevant ones. I'll avoid using "POSITION SPECIFICS" as a heading if it's not one of the prescribed ones, but I can fold it into "About the role" or similar.
- "This role requires periodic travel to remote locations." -> Keep.
- "We are searching for an Engineering Technologist to join our Electronic Fabrication and Test Systems (EF&TS) Department at the Applied Research Laboratory (ARL) at Penn State. The mission for the EFTS Department is to support and contribute to cutting edge technologies and test systems through all design phases to implementation. In this role, you’ll work collaboratively with a multidisciplinary team to deliver innovative, reliable solutions that support ARL’s mission and strengthen the systems our customers depend on. ARL is an authorized DoD SkillBridge partner and welcomes all transitioning military members to apply." -> This is "About the role" content.
- "You will: Assist in the design and implementation of cutting edge electromechanical and software systems..." -> This is a list of duties/responsibilities. Should be `- `.
- "Additional responsibilities for higher-level position include: Recommend modifications or design changes based on testing and analysisEvaluate new engineering tools to aid in design and developmentUse and grow subject matter expertise to quickly grow higher level responsibilitiesManage testing efforts in the lab and field" -> Note: The text has them concatenated without proper separation. I'll parse them as separate items. These are additional responsibilities for higher-level. I'll include them under Responsibilities or as a separate note, but carefully.
- "Required skills/experience areas include: Electronics and/or electro-mechanicsOperating electronic test equipment, and the ability to assemble and test electronic circuitryEffective communication skills for internal audiencesPast success in writing test plans and reportsAbility and willingness to perform basic computer tasks or learn computer programsDemonstrated ability to work through a difficult problem, using proper steps to define and formulate ideas to reach a solution" -> These are skills/requirements. Should be `
- `.
- "Current eligibility for access to classified information at the Secret level or higher and may be subject to a government background investigation to upgrade clearance eligibility, if required" -> This is a requirement/qualification. Keep.
- "Minimum Education, Work Experience & Required Certifications" -> This is a section header in the original. I can map it to "Requirements" or "Qualifications". I'll use `
` for Requirements/Qualifications as needed.
- "If filled as Engineering Technologist, Electrical (ARL) - Intermediate Professional, this position requires: Bachelor's Degree 1+ years of relevant experience Required Certifications: None" -> Specifics.
- "If filled as Engineering Technologist, Electrical (ARL) - Professional, this position requires: Bachelor's Degree No prior relevant work experience required Required Certifications: None" -> Specifics.
- "ARL’s purpose is to research and develop innovative solutions to challenging scientific, engineering, and technology problems in support of the Navy, the Department of Defense (DoD), and the Intel Community (IC). FOR FURTHER INFORMATION on ARL, visit our website at www.arl.psu.edu." -> Could be part of About the role or a separate small section, but I'll fold into About the role or note. I'll keep it substantive.
- "BACKGROUND CHECKS/CLEARANCES Employment with the University will require successful completion of background check(s) in accordance with University policies. Notice regarding employment at the Applied Research Laboratory (ARL): Employees must be eligible to obtain a government security clearance, participate in the ARL drug testing program, and comply with electronic and physical monitoring requirements applicable to federal contractors. ARL operates in a secure information environment involving Unclassified, Controlled Unclassified Information (CUI), and Classified information. Personal electronic devices brought onsite must be registered and may be restricted from certain areas. You must be a U.S. citizen to apply." -> This is substantive about background/clearance. I'll include under Qualifications or a dedicated section if it has real content. The rules say include a section ONLY when the posting has real, specific content for it. This has specific content, so I can have a section, but I need to map to allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Qualifications" seems fitting, or I could fold into a general "Requirements" section. I'll see.
- "Salary & Benefits The salary range for this position, including all possible grades, is $68,604.00 - $113,100.00. Salary Structure - Information on Penn State's salary structure Penn State provides a competitive benefits package for full-time employees designed to support both personal and professional well-being. In addition to comprehensive medical, dental, and vision coverage, employees enjoy robust retirement plans and substantial paid time off which includes holidays, vacation and sick time. One of the standout benefits is the generous 75% tuition discount, available to employees as well as eligible spouses and children. For more detailed information, please visit our Benefits Page." -> Pay section: has specific salary range. Benefits section: has specific benefits. I must create Pay and Benefits sections only if the posting actually states them. It does. I should not put placeholder text. I'll include them with the actual content.
- "CAMPUS SECURITY CRIME STATISTICS..." -> Remove (boilerplate/legal).
- "EEO IS THE LAW..." -> Remove (EEO boilerplate).
- "Federal Contractors Labor Law Poster..." -> Remove.
- "Penn State Policies..." -> Remove.
- "Copyright Information..." -> Remove.
- "Hotlines" -> Remove.
Now, I need to structure into semantic HTML using `` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should not create sections that are thin/filler. I'll only include sections that have real specific content.
Let's map the extracted content:
- **About the role**: The paragraph about Engineering Technologist, EF&TS Dept, ARL, mission, multidisciplinary team, innovative solutions, DoD SkillBridge, etc. Also include the "ARL’s purpose" paragraph. I'll combine as "About the role" or maybe "Position Overview". I'll use `About the role
`.
- **Responsibilities**: The "You will:" list and "Additional responsibilities for higher-level position include:". I'll create a `- ` list combining both, but careful: the "Additional responsibilities" are for higher-level position. I'll include them as part of Responsibilities, noting the level distinction if needed, but keep substantive content. I'll just list all duties found.
- **Skills/Requirements**: The "Required skills/experience areas include:" list. I'll put under `
Skills
` or `Requirements
`. The rules list both "Requirements" and "Skills" as possible headings. I'll use `Skills
` for the skills list, and `Requirements
` for education/certifications/clearance.
- **Requirements/Qualifications**: The "Minimum Education, Work Experience & Required Certifications" section with the two tiered options (Intermediate Professional vs Professional). Also the clearance/background info. I'll structure as Requirements. I'll use `Requirements
`.
- **Pay**: Salary range $68,604.00 - $113,100.00. I'll use `Pay
`.
- **Benefits**: The benefits package description, 75% tuition discount, etc. I'll use `Benefits
`.
- **Schedule**: Not mentioned. I won't create a Schedule section.
- **Other notes**: "Your working location will be fully on-site in State College, PA. This role requires periodic travel to remote locations." I could fold into About the role or a short prose section. I'll maybe include as part of About the role or a brief note, but rules say use `` for prose. I'll fold into About the role or create a small section if needed, but to avoid thin sections, I'll integrate.
- Remove all application instructions, boilerplate, EEO, etc.
Let's re-read the rules carefully: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g.", so those are examples. I should use those or similar meaningful ones. I'll stick to those exact ones for consistency, but only include when there's real content.
"Do NOT repeat the job title as a heading (the page already shows it)" - I won't.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - No job ID in text, good.
"Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll keep all details.
"Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - I'll remove those.
` for prose. - Do NOT repeat job title as heading (already shown). - Do NOT put Job ID / requisition numbers as headings. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Input Text:** Let me carefully go through the provided job posting text, identify sections, extract substantive content, and ignore/remove boilerplate/instructions. Input text segments: - "APPLICATION INSTRUCTIONS: CURRENT PENN STATE EMPLOYEE..." -> Remove (application instructions) - "CURRENT PENN STATE STUDENT..." -> Remove - "If you are NOT a current employee or student..." -> Remove - "Approval of remote and hybrid work is not guaranteed..." -> Could be a short prose note, but maybe fold into location/notes. I'll consider if it's substantive enough. The rules say remove application instructions, but this is a note about remote work. I'll see. - "POSITION SPECIFICS Your working location will be fully on-site in State College, PA. Questions related to flexible work should be directed to the hiring manager during the interview process. This role requires periodic travel to remote locations." -> Keep as prose or section. "POSITION SPECIFICS" isn't a heading I must use; I can create my own headings based on content. The rules say use `
` for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should map content to these meaningfully, or create relevant ones. I'll avoid using "POSITION SPECIFICS" as a heading if it's not one of the prescribed ones, but I can fold it into "About the role" or similar.
- "This role requires periodic travel to remote locations." -> Keep.
- "We are searching for an Engineering Technologist to join our Electronic Fabrication and Test Systems (EF&TS) Department at the Applied Research Laboratory (ARL) at Penn State. The mission for the EFTS Department is to support and contribute to cutting edge technologies and test systems through all design phases to implementation. In this role, you’ll work collaboratively with a multidisciplinary team to deliver innovative, reliable solutions that support ARL’s mission and strengthen the systems our customers depend on. ARL is an authorized DoD SkillBridge partner and welcomes all transitioning military members to apply." -> This is "About the role" content.
- "You will: Assist in the design and implementation of cutting edge electromechanical and software systems..." -> This is a list of duties/responsibilities. Should be `- `.
- "Additional responsibilities for higher-level position include: Recommend modifications or design changes based on testing and analysisEvaluate new engineering tools to aid in design and developmentUse and grow subject matter expertise to quickly grow higher level responsibilitiesManage testing efforts in the lab and field" -> Note: The text has them concatenated without proper separation. I'll parse them as separate items. These are additional responsibilities for higher-level. I'll include them under Responsibilities or as a separate note, but carefully.
- "Required skills/experience areas include: Electronics and/or electro-mechanicsOperating electronic test equipment, and the ability to assemble and test electronic circuitryEffective communication skills for internal audiencesPast success in writing test plans and reportsAbility and willingness to perform basic computer tasks or learn computer programsDemonstrated ability to work through a difficult problem, using proper steps to define and formulate ideas to reach a solution" -> These are skills/requirements. Should be `
- `.
- "Current eligibility for access to classified information at the Secret level or higher and may be subject to a government background investigation to upgrade clearance eligibility, if required" -> This is a requirement/qualification. Keep.
- "Minimum Education, Work Experience & Required Certifications" -> This is a section header in the original. I can map it to "Requirements" or "Qualifications". I'll use `
` for Requirements/Qualifications as needed.
- "If filled as Engineering Technologist, Electrical (ARL) - Intermediate Professional, this position requires: Bachelor's Degree 1+ years of relevant experience Required Certifications: None" -> Specifics.
- "If filled as Engineering Technologist, Electrical (ARL) - Professional, this position requires: Bachelor's Degree No prior relevant work experience required Required Certifications: None" -> Specifics.
- "ARL’s purpose is to research and develop innovative solutions to challenging scientific, engineering, and technology problems in support of the Navy, the Department of Defense (DoD), and the Intel Community (IC). FOR FURTHER INFORMATION on ARL, visit our website at www.arl.psu.edu." -> Could be part of About the role or a separate small section, but I'll fold into About the role or note. I'll keep it substantive.
- "BACKGROUND CHECKS/CLEARANCES Employment with the University will require successful completion of background check(s) in accordance with University policies. Notice regarding employment at the Applied Research Laboratory (ARL): Employees must be eligible to obtain a government security clearance, participate in the ARL drug testing program, and comply with electronic and physical monitoring requirements applicable to federal contractors. ARL operates in a secure information environment involving Unclassified, Controlled Unclassified Information (CUI), and Classified information. Personal electronic devices brought onsite must be registered and may be restricted from certain areas. You must be a U.S. citizen to apply." -> This is substantive about background/clearance. I'll include under Qualifications or a dedicated section if it has real content. The rules say include a section ONLY when the posting has real, specific content for it. This has specific content, so I can have a section, but I need to map to allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Qualifications" seems fitting, or I could fold into a general "Requirements" section. I'll see.
- "Salary & Benefits The salary range for this position, including all possible grades, is $68,604.00 - $113,100.00. Salary Structure - Information on Penn State's salary structure Penn State provides a competitive benefits package for full-time employees designed to support both personal and professional well-being. In addition to comprehensive medical, dental, and vision coverage, employees enjoy robust retirement plans and substantial paid time off which includes holidays, vacation and sick time. One of the standout benefits is the generous 75% tuition discount, available to employees as well as eligible spouses and children. For more detailed information, please visit our Benefits Page." -> Pay section: has specific salary range. Benefits section: has specific benefits. I must create Pay and Benefits sections only if the posting actually states them. It does. I should not put placeholder text. I'll include them with the actual content.
- "CAMPUS SECURITY CRIME STATISTICS..." -> Remove (boilerplate/legal).
- "EEO IS THE LAW..." -> Remove (EEO boilerplate).
- "Federal Contractors Labor Law Poster..." -> Remove.
- "Penn State Policies..." -> Remove.
- "Copyright Information..." -> Remove.
- "Hotlines" -> Remove.
Now, I need to structure into semantic HTML using `` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should not create sections that are thin/filler. I'll only include sections that have real specific content.
Let's map the extracted content:
- **About the role**: The paragraph about Engineering Technologist, EF&TS Dept, ARL, mission, multidisciplinary team, innovative solutions, DoD SkillBridge, etc. Also include the "ARL’s purpose" paragraph. I'll combine as "About the role" or maybe "Position Overview". I'll use `About the role
`.
- **Responsibilities**: The "You will:" list and "Additional responsibilities for higher-level position include:". I'll create a `- ` list combining both, but careful: the "Additional responsibilities" are for higher-level position. I'll include them as part of Responsibilities, noting the level distinction if needed, but keep substantive content. I'll just list all duties found.
- **Skills/Requirements**: The "Required skills/experience areas include:" list. I'll put under `
Skills
` or `Requirements
`. The rules list both "Requirements" and "Skills" as possible headings. I'll use `Skills
` for the skills list, and `Requirements
` for education/certifications/clearance.
- **Requirements/Qualifications**: The "Minimum Education, Work Experience & Required Certifications" section with the two tiered options (Intermediate Professional vs Professional). Also the clearance/background info. I'll structure as Requirements. I'll use `Requirements
`.
- **Pay**: Salary range $68,604.00 - $113,100.00. I'll use `Pay
`.
- **Benefits**: The benefits package description, 75% tuition discount, etc. I'll use `Benefits
`.
- **Schedule**: Not mentioned. I won't create a Schedule section.
- **Other notes**: "Your working location will be fully on-site in State College, PA. This role requires periodic travel to remote locations." I could fold into About the role or a short prose section. I'll maybe include as part of About the role or a brief note, but rules say use `` for prose. I'll fold into About the role or create a small section if needed, but to avoid thin sections, I'll integrate.
- Remove all application instructions, boilerplate, EEO, etc.
Let's re-read the rules carefully: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g.", so those are examples. I should use those or similar meaningful ones. I'll stick to those exact ones for consistency, but only include when there's real content.
"Do NOT repeat the job title as a heading (the page already shows it)" - I won't.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - No job ID in text, good.
"Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll keep all details.
"Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - I'll remove those.
- `.
- "Current eligibility for access to classified information at the Secret level or higher and may be subject to a government background investigation to upgrade clearance eligibility, if required" -> This is a requirement/qualification. Keep.
- "Minimum Education, Work Experience & Required Certifications" -> This is a section header in the original. I can map it to "Requirements" or "Qualifications". I'll use `
` for Requirements/Qualifications as needed. - "If filled as Engineering Technologist, Electrical (ARL) - Intermediate Professional, this position requires: Bachelor's Degree 1+ years of relevant experience Required Certifications: None" -> Specifics. - "If filled as Engineering Technologist, Electrical (ARL) - Professional, this position requires: Bachelor's Degree No prior relevant work experience required Required Certifications: None" -> Specifics. - "ARL’s purpose is to research and develop innovative solutions to challenging scientific, engineering, and technology problems in support of the Navy, the Department of Defense (DoD), and the Intel Community (IC). FOR FURTHER INFORMATION on ARL, visit our website at www.arl.psu.edu." -> Could be part of About the role or a separate small section, but I'll fold into About the role or note. I'll keep it substantive. - "BACKGROUND CHECKS/CLEARANCES Employment with the University will require successful completion of background check(s) in accordance with University policies. Notice regarding employment at the Applied Research Laboratory (ARL): Employees must be eligible to obtain a government security clearance, participate in the ARL drug testing program, and comply with electronic and physical monitoring requirements applicable to federal contractors. ARL operates in a secure information environment involving Unclassified, Controlled Unclassified Information (CUI), and Classified information. Personal electronic devices brought onsite must be registered and may be restricted from certain areas. You must be a U.S. citizen to apply." -> This is substantive about background/clearance. I'll include under Qualifications or a dedicated section if it has real content. The rules say include a section ONLY when the posting has real, specific content for it. This has specific content, so I can have a section, but I need to map to allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Qualifications" seems fitting, or I could fold into a general "Requirements" section. I'll see. - "Salary & Benefits The salary range for this position, including all possible grades, is $68,604.00 - $113,100.00. Salary Structure - Information on Penn State's salary structure Penn State provides a competitive benefits package for full-time employees designed to support both personal and professional well-being. In addition to comprehensive medical, dental, and vision coverage, employees enjoy robust retirement plans and substantial paid time off which includes holidays, vacation and sick time. One of the standout benefits is the generous 75% tuition discount, available to employees as well as eligible spouses and children. For more detailed information, please visit our Benefits Page." -> Pay section: has specific salary range. Benefits section: has specific benefits. I must create Pay and Benefits sections only if the posting actually states them. It does. I should not put placeholder text. I'll include them with the actual content. - "CAMPUS SECURITY CRIME STATISTICS..." -> Remove (boilerplate/legal). - "EEO IS THE LAW..." -> Remove (EEO boilerplate). - "Federal Contractors Labor Law Poster..." -> Remove. - "Penn State Policies..." -> Remove. - "Copyright Information..." -> Remove. - "Hotlines" -> Remove. Now, I need to structure into semantic HTML using `
` for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should not create sections that are thin/filler. I'll only include sections that have real specific content. Let's map the extracted content: - **About the role**: The paragraph about Engineering Technologist, EF&TS Dept, ARL, mission, multidisciplinary team, innovative solutions, DoD SkillBridge, etc. Also include the "ARL’s purpose" paragraph. I'll combine as "About the role" or maybe "Position Overview". I'll use `
About the role
`. - **Responsibilities**: The "You will:" list and "Additional responsibilities for higher-level position include:". I'll create a `- ` list combining both, but careful: the "Additional responsibilities" are for higher-level position. I'll include them as part of Responsibilities, noting the level distinction if needed, but keep substantive content. I'll just list all duties found.
- **Skills/Requirements**: The "Required skills/experience areas include:" list. I'll put under `
Skills
` or `Requirements
`. The rules list both "Requirements" and "Skills" as possible headings. I'll use `Skills
` for the skills list, and `Requirements
` for education/certifications/clearance. - **Requirements/Qualifications**: The "Minimum Education, Work Experience & Required Certifications" section with the two tiered options (Intermediate Professional vs Professional). Also the clearance/background info. I'll structure as Requirements. I'll use `Requirements
`. - **Pay**: Salary range $68,604.00 - $113,100.00. I'll use `Pay
`. - **Benefits**: The benefits package description, 75% tuition discount, etc. I'll use `Benefits
`. - **Schedule**: Not mentioned. I won't create a Schedule section. - **Other notes**: "Your working location will be fully on-site in State College, PA. This role requires periodic travel to remote locations." I could fold into About the role or a short prose section. I'll maybe include as part of About the role or a brief note, but rules say use `` for prose. I'll fold into About the role or create a small section if needed, but to avoid thin sections, I'll integrate. - Remove all application instructions, boilerplate, EEO, etc. Let's re-read the rules carefully: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g.", so those are examples. I should use those or similar meaningful ones. I'll stick to those exact ones for consistency, but only include when there's real content. "Do NOT repeat the job title as a heading (the page already shows it)" - I won't. "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - No job ID in text, good. "Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll keep all details. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - I'll remove those.
- ` list combining both, but careful: the "Additional responsibilities" are for higher-level position. I'll include them as part of Responsibilities, noting the level distinction if needed, but keep substantive content. I'll just list all duties found.
- **Skills/Requirements**: The "Required skills/experience areas include:" list. I'll put under `