Systems Integration Engineer

We need to produce HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes Company Description, Clearance Required, Other Requirements, Description (role), Basic Qualifications, Recommended Qualifications. No explicit Benefits, Pay, Schedule. So we should not include those headings. We need to map content to appropriate sections. We have: - Company Description: could be "About the role"? Actually "About the role" is more about the job, not company. But we can use "About the role" heading for description of role. The company description could be placed maybe under "About the role" or maybe we could have a separate "About the company"? Not allowed headings list only those given. So we need to fit content into those headings. Likely we will have sections: About the role (description), Responsibilities (maybe from description), Requirements (clearance, citizenship, basic qualifications?), Qualifications (basic and recommended?), Skills (maybe from recommended qualifications). We need to avoid duplication. We must preserve all substantive information. Let's extract: Company Description: Synergy ECP is a Service Disabled Veteran-Owned Small Business SD(VOSB) formed July 2007 HQ Columbia MD, provides services to defense, intelligence, health care. etc. Also equal opportunity employer statement (but we must remove EEO boilerplate). The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should omit the equal opportunity employer sentence. Also we should keep the rest of company description? It's substantive about the company. Might be okay to keep under About the role? Might be considered company description not role. But we have no other heading for company. Could we put it under About the role? The heading "About the role" is for role description, but we could still include company info there as part of role context. Probably acceptable. Clearance Required: TS/SCI w/ Full Scope Polygraph Other Requirements: U.S. Citizenship Description: Provides expertise in integrating, installing, configuring, upgrading, compiling, and supporting COTS/GOTS software in a heterogeneous operating system environment. The Level III Software Integration Engineer (SIE) shall possess the following capabilities: list. Then Basic Qualifications: Bachelor's Degree in CS or related field and at least 8 years experience... OR alternatives. Then Experience as Linux System Administrator etc. Then Recommended Qualifications: list. We need to output HTML with headings

and

• for lists,

  for prose. We must not repeat job title as heading (the page already shows it). No Job ID. We must not include Pay/Benefits/Schedule sections unless present. Thus we can have sections: - About the role (maybe includes company description and role description) - Responsibilities (list of duties from description) - Requirements (clearance, citizenship, basic qualifications? maybe combine) - Qualifications (maybe basic and recommended? but we already have Requirements; maybe we split: Requirements = mandatory (clearance, citizenship, basic qualifications); Qualifications = recommended qualifications) - Skills (maybe from recommended qualifications like automation, monitoring, InfiniBand, Lustre, Atlassian) But we need to avoid duplication. Let's think. Better: Use sections: - About the role (company description + brief role overview) - Responsibilities (list of capabilities) - Requirements (clearance, citizenship, basic qualifications) - Qualifications (recommended qualifications) - Skills (maybe specific technical skills from recommended qualifications: automation, benchmarks, Linux cluster/node monitoring tools, InfiniBand, parallel file systems, Atlassian Suite) But recommended qualifications already include those; we could just put them under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements, Qualifications. That's four sections. We need to ensure we include all substantive info. Let's extract each piece. Company Description (keep except EEO): "Synergy ECP is a Service Disabled Veteran-Owned Small Business SD(VOSB) that was formed in July 2007 with Headquarters in Columbia, MD and is made up of talented, dedicated staff to provide a broad range of services to the defense, intelligence and health care industries. In an ultra-competitive environment, Synergy ECP has thrived by adhering to our name, making sure excellence is displayed by our Employees, to our Customers and by Improving Performance (ECP). It’s what sets us apart, enabling us to be an autonomous yet agile business that delivers huge results - showing we’re ready to meet our customers’ evolving demands. Synergy ECP has earned a client list that includes numerous Fortune 100 companies, in addition to multiple branches of the US government and military services." That's the company description. Role overview: "Provides expertise in integrating, installing, configuring, upgrading, compiling, and supporting COTS/GOTS software in a heterogeneous operating system environment. The Level III Software Integration Engineer (SIE) shall possess the following capabilities:" then list. We can combine company description and role overview under About the role. Responsibilities: the list of capabilities: - Ability to integrate, install, configure, upgrade, compile, and support COTS/GOTS software. - Generate documentation for the full software stack. - Update software for sustainment support. - Basic Linux system administration skills and shell scripting. - Execute test codes for characterization of software performance. - Provide software product ownership for HPC tools. - Working knowledge of CM tools, web documentation, and issue tracking. - Ability to work in a fast paced environment and switch between various architectural paradigms. That's from description. Requirements: Clearance Required: TS/SCI w/ Full Scope Polygraph; Other Requirements: U.S. Citizenship; Basic Qualifications (education/experience) and Linux sysadmin experience etc. Let's list Basic Qualifications: - Bachelor's Degree in Computer Science or related field and have at least eight (8) years of demonstrable experience with integrating, installing, configuring, upgrading, compiling, and supporting COTS/GOTS software in a heterogeneous operating system environment. - OR The individual shall have five (5) years full time Computer Science directly related work that can be substituted for a degree and have at least eight (8) years of demonstrable experience. - OR An industry recognized professional certification, as defined in the TT0s, may substitute as one (1) year experience. - A Master's Degree in Computer Science or related field may substitute for two (2) years' experience - Experience as a Linux System Administrator with technical knowledge regarding compute, network, memory, and storage components - Experience writing scripts using Bash - Experience diagnosing system issues on Linux-based clusters - Experience with SLURM Workload Manager - Experience with HPC open source parallel programming methods such as OpenSHMEM, pthreads, Open MPI, and UPC We need to keep all. Qualifications (Recommended): - Experience with automating system procedures/tasks and using benchmarks to confirm subsystem health - Experience with Linux cluster/node monitoring tools such as NHC (Node Health Check) - Familiar with InfiniBand network communications - Familiar with parallel file systems such as Lustre - Experience with the Atlassian Suite of Tools (Jira, Confluence, Bitbucket) We could also include any other recommended qualifications. Now we need to output HTML. Structure:

  About the role

  Company description paragraph(s) + role overview sentence.

  Then

  Responsibilities

  • ... each
  Then

  Requirements

  Clearance Required: TS/SCI w/ Full Scope Polygraph

  Other Requirements: U.S. Citizenship

  Then maybe a
  for Basic Qualifications. But we need to avoid duplication: The basic qualifications include education/experience and Linux sysadmin etc. We'll list them as
  . Then

  Qualifications

  for recommended qualifications. We must not include Benefits/Pay/Schedule. Check that we didn't include any placeholder text like "commensurate with experience". Not present. Now ensure we preserve all substantive info. Did we miss anything? The company description includes "Synergy ECP is an equal opportunity employer..." we removed that as per instruction. Good. Also note "Clearance Required: TS/SCI w/ Full Scope Polygraph" and "Other Requirements: U.S. Citizenship". We kept those. Now format. We need to output only HTML fragment, no markdown fences. Let's craft. Potential issues: The Basic Qualifications includes OR statements; we need to preserve them exactly. We'll keep as list items. Potential duplication: The responsibilities list includes "Basic Linux system administration skills and shell scripting." which also appears in Basic Qualifications as "Experience writing scripts using Bash" and "Experience as a Linux System Administrator...". It's okay to have some overlap; we must preserve all info, not deduplicate. Now produce HTML. Let's write:

  About the role

  Synergy ECP is a Service Disabled Veteran-Owned Small Business SD(VOSB) that was formed in July 2007 with Headquarters in Columbia, MD and is made up of talented, dedicated staff to provide a broad range of services to the defense, intelligence and health care industries. In an ultra-competitive environment, Synergy ECP has thrived by adhering to our name, making sure excellence is displayed by our Employees, to our Customers and by Improving Performance (ECP). It’s what sets us apart, enabling us to be an autonomous yet agile business that delivers huge results - showing we’re ready to meet our customers’ evolving demands. Synergy ECP has earned a client list that includes numerous Fortune 100 companies, in addition to multiple branches of the US government and military services. Provides expertise in integrating, installing, configuring, upgrading, compiling, and supporting COTS/GOTS software in a heterogeneous operating system environment. The Level III Software Integration Engineer (SIE) shall possess the following capabilities:

  But note we already have Responsibilities section listing capabilities; we might not need to repeat the sentence "The Level III Software Integration Engineer (SIE) shall possess the following capabilities:" in About the role; we could just end with that sentence and then list in Responsibilities. However we need to preserve all substantive info; that sentence is part of description. We could keep it in About the role as introductory sentence before the list. That's fine. Now Responsibilities: list each capability. Let's extract each bullet exactly as in description: - Ability to integrate, install, configure, upgrade, compile, and support COTS/GOTS software. - Generate documentation for the full software stack. - Update software for sustainment support. - Basic Linux system administration skills and shell scripting. - Execute test codes for characterization of software performance. - Provide software product ownership for HPC tools. - Working knowledge of CM tools, web documentation, and issue tracking. - Ability to work in a fast paced environment and switch between various architectural paradigms. Now Requirements: We'll have paragraphs for clearance and citizenship, then a list for Basic Qualifications. Basic Qualifications list items: - Bachelor's Degree in Computer Science or related field and have at least eight (8) years of demonstrable experience with integrating, installing, configuring, upgrading, compiling, and supporting COTS/GOTS software in a heterogeneous operating system environment. - OR The individual shall have five (5) years full time Computer Science directly related work that can be substituted for a degree and have at least eight (8) years of demonstrable experience. - OR An industry recognized professional certification, as defined in the TT0s, may substitute as one (1) year experience. - A Master's Degree in Computer Science or related field may substitute for two (2) years' experience - Experience as a Linux System Administrator with technical knowledge regarding compute, network, memory, and storage components - Experience writing scripts using Bash - Experience diagnosing system issues on Linux-based clusters -