System Integration 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 need to parse the job posting. Key content: - About the role: description of role, position description, responsibilities. - Responsibilities: essential duties and responsibilities. - Requirements: required knowledge, skills, abilities. - Qualifications: maybe preferred knowledge, skills, abilities. - Skills: maybe combine required and preferred? But we can separate. - Benefits: mention Brookhaven National Laboratory benefits program, comprehensive employee benefits program. - Pay: salary range $71,600 - $100,000 per year. - Schedule: on-site position (maybe schedule not specified). Not given explicit schedule like full-time, but we can infer it's full-time on-site. However we should not create Schedule section unless posting actually states them. It says "This is an on-site position supporting NSLS-II beamline programs." That's about location, not schedule. No explicit schedule like "full-time", "part-time", "shift". So we should not create Schedule section. - Also maybe "Environmental, Health & Safety Requirements" could be a section but not in list of allowed headings; we should not create new headings beyond allowed list. Could fold into Responsibilities or Requirements? Probably better to include under Responsibilities or maybe a separate section not allowed; we should drop it. - Also "Other Information" includes cover letter recommendation, REAL-ID, UPIV credential etc. Those are minor metadata; we can fold into a short

or drop. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info from the posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. Likely we need to keep the details but can be concise? It says do not summarize away detail. So we need to keep the specifics, maybe bullet points. We need to use

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

  for prose. Thus we will create sections:

  About the role

  with prose describing role.

  Responsibilities

  with
  • each duty.

    Requirements

    with
    • each required knowledge/skill/ability.

      Qualifications

      with
      • each preferred knowledge/skill/ability.

        Benefits

        with

        describing benefits program.

        Pay

        with

        salary range. We should not repeat job title. We need to exclude boilerplate: EEO, legal, navigation, cookie, etc. Also exclude duplicated lines. We need to include all substantive info: The description of DSSI, DAD group, role interface, etc. Also mention that it's on-site, cover letter recommendation, REAL-ID, UPIV credential, etc. Those are "Other Information". Should we include them? They are substantive but not fitting into allowed headings. Could we put them under a generic

        after sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside sections. It said use

        for section headings,

        • for any list,

          for prose. So we can have prose paragraphs outside sections as needed. So we can include a

          for other information like cover letter recommendation, REAL-ID, UPIV, etc. We must not include duplicated lines. Let's extract substantive info: From first paragraph: The National Synchrotron Light Source-II (NSLS-II) at Brookhaven National Laboratory is a U.S. Department of Energy Office of Science User Facility, operating about 30 state-of-the-art X-ray beamlines (link). The Data Science and Systems Integration (DSSI) Division of NSLS-II innovates, integrates, and supports critical hardware for experimental stations and develops and stewards essential software for applications for data acquisition and analysis. DSSI focuses its research and development in data science and advanced instrumentation and operation of the critical underlying controls and data infrastructure within NSLS-II. Learn more about DSSI at link. That's about the organization; could be part of About the role. Position Description: This role resides in the Data Acquisition and Detectors (DAD) group of DSSI and works directly with NSLS-II beamline programs to integrate solutions spanning data acquisition, data access, and data analysis. The System Integration Engineer serves at the interface between beamline science and DAD technical capabilities, helping translate scientific and operational requirements into reliable deployed solutions. The role includes configuration, deployment, testing, troubleshooting, and support of end-to-end beamline data workflows and associated software and computing infrastructure. The successful candidate will collaborate with beamline scientists, software engineers, detector and controls experts, and data specialists, while developing broad expertise in scientific instrumentation, distributed computing, and data-intensive science. Essential Duties And Responsibilities list: - Work with beamline programs to understand scientific, operational, and technical requirements for data acquisition, data access, processing, and analysis. - Integrate, configure, deploy, test, and troubleshoot DAD software, services, and infrastructure in beamline environments. - Support end-to-end beamline data workflows from experimental data acquisition through data movement, storage, access, processing, and analysis. Required Knowledge, Skills, And Abilities: - Requires a bachelor's degree in computer science, computer engineering, electrical engineering, physics, or a related scientific or engineering discipline. - Foundational software development or scripting experience, preferably using Python and/or similar languages. - Familiarity with Linux/Unix computing environments and basic networked or distributed computing concepts. - Ability to troubleshoot technical problems systematically across multiple components of an integrated system. - Strong interpersonal and communication skills, including the ability to work effectively with scientists and engineers from different technical backgrounds. - Self-motivated, with a strong ability to learn unfamiliar software, hardware, scientific instrumentation, and computing technologies. Preferred Knowledge, Skills, And Abilities: - Requires a bachelor's degree in computer science, computer engineering, electrical engineering, physics, or a related scientific or engineering discipline with 3+ years of experience supporting scientific research programs. - Master’s degree preferred. - Hands-on experience with scientific data acquisition, experimental control systems, or computing workflows at a synchrotron, beamline, accelerator, or similar scientific user facility. - Proficient in Python and scientific data-analysis tools; C/C++ a plus. - Familiarity with EPICS, Bluesky, areaDetector, or similar controls/orchestration platforms preferred. - Experience with HTTP APIs, databases, messaging systems, microservices, or distributed services. - Experience with containers (Docker, Podman, Kubernetes), CI/CD, and deployment/configuration automation. - Experience with high-throughput or streaming data storage, movement, and access technologies, plus monitoring/logging of integrated systems. - Proven ability to collaborate on multidisciplinary or distributed development teams, including contributions to open-source projects (scientific software a plus). - Skilled at translating scientific and user requirements into clear technical solutions and documentation. Environmental, Health & Safety Requirements: - Ergonomic considerations associated with regular computer use. - Occasional requirement to lift moderately sized items such as desktop computers, servers, or related beamline computing equipment. Other Information: - This is an on-site position supporting NSLS-II beamline programs. - A cover letter is strongly recommended for candidates to be considered for this position. - Brookhaven National Laboratory is committed to providing fair, equitable and competitive compensation. - This is a multi-level role and the full salary range for this position is $71,600.00 - $100,000.00 / year. - You will be placed at the level and salary commensurate with your experience. - Salary offers will be commensurate with the final candidate’s qualification, education and experience and considered with the internal peer group. - Brookhaven National Laboratory is committed to employee success and we believe that a comprehensive employee benefits program is an important and meaningful part of the compensation employees receive. - Review more information at BNL | Benefits Program - Brookhaven National Laboratory requires all non-badged personnel including visitors to produce a REAL-ID or REAL-ID compliant documentation to access Brookhaven National Laboratory – view more information at www.bnl.gov/real-id. - This is due to nationwide identification requirements for federal site access as required by the federal REAL ID Act. - Those not in possession of a REAL ID-compliant document will not be permitted to access the site which includes access to the Laboratory for interviews. - As a U.S. Department of Energy laboratory, Brookhaven National Laboratory requires employees to obtain and maintain a DOE Uncleared Personal Identity Verification (UPIV) credential in accordance with Homeland Security Presidential Directive 12 (HSPD-12) requirements. - The credentialing process is completed as part of onboarding and enables access to DOE facilities and information systems. - As a condition of employment, the selected candidate must be able to obtain and maintain a UPIV credential. - These requirements are established under DOE Order 206.2 Chg. 2, Identity, Credential, and Access Management (ICAM- Identity, Credential, and Access Management (ICAM)), and DOE Order 473.1A- Physical Protection Program- Physical Protection Program. - About Us ... (maybe we can drop as boilerplate? It's about the lab; could be considered substantive but maybe not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Us" paragraph is not exactly boilerplate but could be considered generic info about the lab. Might be okay to keep? It's not specifically about the role. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "About Us" is not those. However it's generic description of the lab; could be considered not essential to the role. But we need to preserve ALL substantive information; does that include the About Us? It's substantive about the employer. Might be okay to keep but we could fold into About the role section. However we already have a lot. We need to avoid duplication: The salary range appears multiple times; we should include once. We need to avoid repeating the same bullet points. Now craft HTML. We'll start with

          About the role

          ... combine org description and position description.

          Then

          Responsibilities

          • ... three items. Then

            Requirements

            • ... six items. Then

              Qualifications

              • ... many items (preferred). We'll list each. Then

                Benefits

                ... mention comprehensive employee benefits program, link to BNL Benefits Program.

                Then

                Pay

                ... salary range $71,600 - $100,000 per year.

                Then maybe a

                for Other Information: on-site, cover letter recommendation, REAL-ID, UPIV credential, etc. We must not include duplicated lines like "Brookhaven National Laboratory is committed to providing fair, equitable and competitive compensation." and later "Brookhaven National Laboratory is committed to employee success..." both are substantive; we can keep both but maybe combine? The instruction says preserve ALL substantive information; we can keep both but avoid duplication. They are not duplicates; they are separate statements. We'll keep both. We need to ensure we don't include any boilerplate like EEO, etc. The posting includes a long EEO statement at the end; we must remove that. Also remove "Equal Opportunity/Affirmative Action Employer" etc. Also remove "VEVRAA Federal