Systems Engineer
Galapagos Federal Systems · Arlington, VA · 1 mo ago
Information Technology$165k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes Job Summary, Key Responsibilities, Skills And Experience, Education and Certifications, Benefits, Security Clearance, Physical Requirements, Company Summary, Company Employment Statement, Salary range.
We must not repeat job title as heading. Use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. The posting has "Job Summary" (could be About the role). "Key Responsibilities" -> Responsibilities. "Skills And Experience" -> Skills (or Requirements?). "Education and Certifications" -> Qualifications. "Benefits" -> Benefits. Salary range -> Pay. No schedule info. Physical Requirements maybe not needed? Could be part of Requirements? But we should only include sections when posting has real specific content. Physical Requirements is specific; but we don't have we a heading for that? Not in list. Could we put under Requirements? Probably better to include a section "Requirements" for physical? But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. The posting has "Job Summary" (could be About the role). "Key Responsibilities" -> Responsibilities. "Skills And Experience" -> Skills (or Requirements?). "Education and Certifications" -> Qualifications. "Benefits" -> Benefits. Salary range -> Pay. No schedule info. Physical Requirements maybe not needed? Could be part of Requirements? But we should only include sections when posting has real specific content. Physical Requirements is specific; but we don't have we a heading for that? Not in list. Could we put under Requirements? Probably better to include a section "Requirements" for physical? But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those. Physical Requirements could go under Requirements? Or maybe we omit if not fitting. But we should preserve ALL substantive information; we cannot drop physical requirements. Could we include it under Requirements as a list? Yes.
Security Clearance also could be under Requirements? Or maybe under Qualifications? Probably Requirements.
Company Summary maybe not needed? Could be omitted? But it's substantive. Could be under About the role? Might be okay to include as a paragraph under About the role.
Company Employment Statement is boilerplate EEO etc; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should drop that.
Security Clearance: "Must be a U.S. Citizen. A high-level Department of Defense active security clearance is/may be required. Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to government information." This is substantive; we can include under Requirements.
Now produce HTML.
Structure:
About the role
About the role
Job Summary ...
Company Summary ...
Responsibilities
- ... each bullet from Key Responsibilities
Requirements
- Active DoD Top Secret clearance with SCI eligibility
- 5+ years of relevant DoD experience supporting systems engineering, acquisition, RDT&E, or related technical programs
- Experience supporting System Program Offices (SPOs), Program Management Offices (PMOs), or the delivery of systems and capabilities to SPOs/PMOs
- Demonstrated experience with Research, Development, Test, and Evaluation (RDT&E) and test and training materiel systems
- Experience supporting the deployment, integration, operation, and sustainment of space test and training materiel systems
- Strong knowledge of Systems Engineering (SE) principles and processes, including practical application to system RDT&E, integration, and fielding
- Experience with Cameo Systems Modeler and Systems Modeling Language (SysML)
- Working knowledge of the Joint Capabilities Integration and Development System (JCIDS) and DoD Architecture Framework (DoDAF) processes and artifacts
- Experience in one or more relevant space technology domains, such as space system architectures, satellite and ground segment design, electro-optical/infrared (EO/IR) and radio frequency (RF) sensors, astrodynamics, propulsion, Guidance, Navigation and Control (GNC), space data communications, or Space Battle Management and Control
- Ability to work full-time on-site and travel up to 25%, as required to support program needs
- Must be a U.S. Citizen. A high-level Department of Defense active security clearance is/may be required. Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to government information.
- Physical requirements: Work may involve sitting or standing for extended periods of time and typing and reading from a computer screen. The candidate must have enough mobility, including bending, reaching, and kneeling, to complete daily duties in a prompt and efficient manner, and that may include lifting up to thirty pounds, as necessary.
Qualifications
- Required Bachelor of Science (BS) degree in Systems Engineering or a related engineering field (e.g., Mechanical, Electrical, Software, etc.)
- Degrees in other Science, Technology, Engineering, or Mathematics (STEM) fields may be considered with substantial, relevant professional experience
- Degrees in other STEM fields may also be considered with significant, relevant professional experience
Skills
But we already listed skills in Requirements; maybe we should separate Skills from Requirements. However the instruction says we can have Skills section. The posting has "Skills And Experience". We could put that under Skills. But we already put experience under Requirements. Might duplicate. Better to follow: Skills And Experience -> Skills section. Requirements maybe for education/qualifications? But we have Qualifications for education. Let's restructure: - About the role: Job Summary + Company Summary - Responsibilities: Key Responsibilities - Skills: Skills And Experience (list) - Qualifications: Education and Certifications - Benefits: Benefits - Pay: Salary range - Requirements: Security Clearance, Physical Requirements, Citizenship? Could be under Requirements. But we must not invent sections without content. All have content. Let's do:About the role
Job Summary ...
Company Summary ...
Responsibilities
- ... list from Key Responsibilities
Skills
- ... list from Skills And Experience (excluding education? Actually Skills And Experience includes experience items; we can list them)
Qualifications
- ... Education and Certifications
Benefits
- ... Benefits list
Pay
USD $165,000.00 - USD $175,000.00 /Yr.
We might also include Requirements for security clearance and physical requirements. Could add a section Requirements. But we already used Skills for experience; maybe Requirements for security clearance and physical. Let's add:Requirements
- ... security clearance, citizenship, physical requirements
Similar jobs
Systems Engineer
Information Technologyapply on grnh.se
Systems Engineer
apply on macu.wd5.myworkdayjobs.com
Systems Engineer
Information Technology$110k–$135k/yrapply on jobs.lever.co
Systems Engineer
Information Technology$55–$60/hrapply on ars2.equest.com
Systems Engineer
Information Technologyapply on apexsystems.com
Systems Engineer
Information Technologyapply on bowheadcareers-uicalaska.icims.com