Control System Software Engineer

We need to output HTML fragment with sections: About the role? The posting includes Overview, Major Duties And Responsibilities, Basic Qualifications, Preferred Qualifications, Special Requirements (Physical Requirements, Security...), Benefits. Also maybe "Overview" could be considered About the role. We'll include sections: About the role (overview), Responsibilities (Major Duties...), Requirements (Basic Qualifications), Preferred Qualifications (maybe as part of Requirements? but we can have separate Skills? The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have content for Overview (About the role), Responsibilities, Basic Qualifications, Preferred Qualifications (could be Skills or Qualifications), Benefits. No explicit Pay or Schedule info (only mention occasional off-hours/weekend support but not schedule specifics). So we should not create Pay or Schedule sections. Benefits we have content. Also we have Special Requirements (Physical Requirements, Security...). Could be part of Requirements or maybe a separate section like Requirements. We can combine Basic Qualifications and Special Requirements under Requirements? But we need to preserve all substantive info. Could create a section "Requirements" containing Basic Qualifications and Special Requirements (Physical, Security). Or we could have separate sections: Requirements (Basic Qualifications) and Special Requirements (maybe under Requirements). The instruction: prefer a few substantive sections over many thin ones. So maybe combine Basic Qualifications and Special Requirements into a single "Requirements" section. Preferred Qualifications could be under "Skills" or "Qualifications". We have "Preferred Qualifications" heading; we could put that under "Skills". Or we could have a "Qualifications" section containing both Basic and Preferred? But we need to preserve headings? Not required to keep original headings, just need to use h3 for section headings. We can decide our own headings as per allowed list. So we can have:

About the role

(overview)

Responsibilities

(Major Duties...)

Requirements

(Basic Qualifications + Special Requirements)

Skills

(Preferred Qualifications)

Benefits

(Benefits) We must not repeat job title. No metadata like Requisition Id. We can fold minor metadata into short p or drop it. The Requisition Id is minor metadata; we can drop it or include in a short p. Probably drop it. We need to preserve all substantive information: ensure we include all details from overview, duties, responsibilities, qualifications, special requirements, benefits. We must not include boilerplate like EEO, scam-warning, application instructions, cookie/navigation/legal. Remove lines about equal opportunity, etc. Also remove "This position will remain open for a minimum of 5 days..." etc. Also remove "We accept Word ..." etc. Also remove "Relocation Assistance is available..." maybe that's part of benefits? It mentions Relocation Assistance is available for certain positions. Could be considered benefit but it's not detailed; we could include under Benefits if we want but it's not specific. Might be considered boilerplate? It's a benefit mention but vague. Safer to include only the benefits listed: medical, retirement plans, flexible work hours, on-site fitness, banking, cafeteria, prescription drug plan, dental, vision, 401(k), contributory pension plan, life insurance, disability benefits, generous vacation and holidays, parental leave, legal insurance with identity theft protection, employee assistance plan, flexible spending accounts, health savings accounts, wellness programs, educational assistance, employee discounts. Also mention "Relocation Assistance is available for certain positions." Could include as a benefit line. We must not include "If you have difficulty using the online application system..." etc. That's application instructions; remove. We must not include "ORNL is an equal opportunity employer..." etc. Remove. Now craft HTML. We'll use

for each section. Use

for prose. Use

• for lists. We need to decide what to list as bullet points. Overview: "The Controls Integration Group at the Spallation Neutron Source (SNS) is seeking an entry level Control System Software Engineer who will focus on control system applications, system development and operations support. This position is part of the Controls Integration Group within the Control Systems Section, Research Accelerator Division of the Neutron Sciences Directorate at Oak Ridge National Laboratory (ORNL). The group is responsible for maintaining and improving fully integrated control systems for the SNS Accelerator to ensure safe, high-reliability beam delivery to the target. These systems typically utilize PLC, VME, or MicroTCA hardware, integrated using the Experimental Physics and Industrial Control System (EPICS) framework. This position reports to the Controls Integration Group Leader. The group is currently focused on modernizing the control system environment. Ongoing upgrade projects include replacing legacy equipment with modern solutions, expanding those associated applications, and enhancing the control room operator experience using the latest software tools." We can put that as prose in

  . Responsibilities: list bullet points from "Major Duties And Responsibilities". Let's extract each sentence as bullet. - Support modernization efforts by developing EPICS applications to support embedded and FPGA based systems. - Help upgrade existing EPICS applications and user interfaces. - Complete verification, deployment, and system integration of EPICS applications for production use. - Support the scientific mission of SNS by developing reliable, maintainable software for accelerator and target control systems as part of a multidisciplinary team. - Collaborate with group members, scientific staff and operations personnel to design, develop, maintain, and improve EPICS-based control systems. - Maintain and support existing production software, including performing troubleshooting and resolving bugs. - Create and maintain software documentation and accompanying training materials. - Adhere to Software Quality Assurance procedures, including managing source code in a central repository with version control systems and developing comprehensive software testing procedures. - Provide operational support, troubleshooting, and system improvements for accelerator and target control systems. - While typical work hours are office-based, occasional off-hours or weekend support may be required to meet user facility needs. - Ensure compliance with environmental, safety, health, and quality procedures and programs. - As a member of the ORNL scientific community, commit to ORNL’s Research Code of Conduct. (maybe we can keep as bullet) - Deliver ORNL’s mission by aligning behaviors, priorities, and interactions with our core values of Impact, Integrity, Teamwork, Safety, and Service. - Promote equal opportunity by fostering a respectful workplace – in how we treat one another, work together, and measure success. But note: the last two bullet points about core values and equal opportunity might be considered boilerplate? They are part of the responsibilities section though. The instruction says remove EEO/equal-opportunity boilerplate. However those lines are about ORNL's values and equal opportunity; might be considered boilerplate. Safer to remove them? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The equal opportunity statement is likely boilerplate. The core values statement maybe also boilerplate but it's part of ORNL's mission. Might be considered boilerplate? Not sure. Safer to keep only substantive technical duties. I'd keep the technical duties and maybe keep the compliance with environmental, safety, health, and quality procedures (that's substantive). The core values and equal opportunity could be considered boilerplate; I'd remove them. Thus responsibilities bullets: first 10 items (up to Provide operational support...). Also include "While typical work hours are office-based, occasional off-hours or weekend support may be required to meet user facility needs." That's about schedule but we are not making a Schedule section; we can keep it as a bullet under Responsibilities. Now Requirements: combine Basic Qualifications and Special Requirements (Physical Requirements, Security...). Basic Qualifications: - A BS degree in engineering, computer science or related field - Demonstrated programming experience in modern object-oriented programming languages, preferably C++ - Proficiency with collaborative software development tools and practices, such as software debugger, version control, issue tracking, documentation Special Requirements: - Physical Requirements: Work involves some physical requirements and working conditions. As such, a pre-hire physical will be required after offer. - Visa sponsorship is not available. - Security, Credentialing, And Eligibility Requirements: This position requires the ability to obtain and maintain an HSPD-12 PIV badge. For employment at ORNL, a Real ID compliant form of identification will be required. Additionally, ORNL is subject to Department of Energy (DOE) access restrictions. All employees must also be able to obtain and maintain a federal Personal Identity Verification (PIV) card as mandated by Homeland Security Presidential Directive 12 (HSPD-12) and Department of Energy (DOE) Order 473.1A, which requires a favorable post-employment background investigation. To obtain this credential, new employees must successfully complete and pass a Federal Tier 1 background check investigation. This investigation includes a declaration of illegal drug activities, including use, supply, possession, or manufacture within the last year. This includes marijuana and cannabis derivatives, which are still considered illegal under federal law, regardless of state laws. We need to preserve all that. Could be multiple paragraphs. We can put as

  • for each bullet, but some are longer sentences. Could still be list items. We'll list: - A BS degree in engineering, computer science or related field - Demonstrated programming experience in modern object-oriented programming languages, preferably C++ - Proficiency with collaborative software development tools and practices, such as software debugger, version control, issue tracking, documentation - Physical requirements: work involves some physical requirements and working conditions; a pre-hire physical will be required after offer. - Visa sponsorship is not available. - Must be able to obtain and maintain an HSPD-12 PIV badge; Real ID compliant identification required. - Must be able to obtain and maintain a federal PIV card per HSPD-12 and DOE Order 473.1A, requiring a favorable Tier 1 background check (including declaration of illegal drug activities in the past year, including marijuana/cannabis derivatives). We need to keep the detail about DOE access restrictions etc. Could condense but preserve substance. Now Skills (Preferred Qualifications): - Experience developing applications or systems programming in a Linux environment - Demonstrated experience with embedded systems and/or systems programming - Experience with EPICS or a similar toolkit for developing distributed control systems - Exposure to additional programming languages, such as C, Python, Java or similar - Familiarity with real-time operating systems and software practices - Prior experience working in a scientific user facility - Experience with GitLab and CI/CD pipelines - Hands-on experience with in-field troubleshooting of software and hardware interfaces Now Benefits: list bullet points from benefits paragraph. Benefits list: - Competitive pay and benefits programs (but we avoid Pay section; we can mention competitive pay as part of benefits? The instruction says do not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits section is okay because posting states benefits. It mentions competitive pay but we can include as part of benefits bullet. - Medical and retirement plans - Flexible work hours - On-site fitness, banking, and cafeteria facilities - Prescription Drug Plan - Dental Plan - Vision Plan - 401(k) Retirement Plan - Contributory Pension Plan - Life Insurance - Disability Benefits - Generous Vacation and Holidays - Parental Leave - Legal Insurance with Identity Theft Protection - Employee Assistance Plan - Flexible Spending Accounts - Health Savings Accounts - Wellness Programs - Educational Assistance - Employee Discounts - Relocation Assistance is available for certain positions. We should not include "The laboratory offers many employee benefits, including medical and retirement plans and flexible work hours, to help you and your family live happy and healthy." That's prose; we can keep as a brief paragraph before list. Now ensure we don't include any boilerplate like EEO etc. We