Jobs · Engineering · Florida

Senior Civil Engineer / Facilities Subject Matter Expert

Galapagos Federal Systems · Melbourne, FL · 1 mo ago
Engineering$150k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections that have real content. Use
  • for lists. Use

    for prose. No job title heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines. Keep all substantive info. We need to parse the job posting. Job Summary: paragraph about role. Key Responsibilities: list of bullet points (each line starts with something). Should be

    • . Skills And Experience: list of bullet points (some lines maybe not bullet but we can treat as list). Also includes "Active DoD Secret security clearance" etc. Education and Certifications: bullet list? It says "The Civil Engineering & Facilities, SME must meet the following Required Bachelor's degree...". Could be a list. Benefits: list of benefits. Pay: there is a line "USD $150,000.00 - USD $180,000.00 /Yr." That's pay info. Should be a Pay section. Schedule: not mentioned, so omit. Security Clearance: mention "Must be a U.S. Citizen. A high-level Department of Defense active security clearance is/may be required." Could be part of Skills or separate? It appears after Benefits. Could be its own section? The instruction: include a section ONLY when posting has real, specific content. So we could have a Security Clearance section. But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Security Clearance as a standard heading, but we could still use a heading if content exists? The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." Might be better to incorporate security clearance into Skills or Requirements. However they gave a separate "Security Clearance" line after Benefits. Could treat as part of Skills? But it's a requirement. Could create a "Requirements" section for security clearance and citizenship. But we already have Skills And Experience which includes clearance. Actually Skills And Experience includes "Active DoD Secret security clearance". So we can keep that there. The later "Security Clearance Must be a U.S. Citizen..." is redundant; we can drop duplicated lines. So we can omit that later line as duplicate. Company Summary and Company Employment Statement: boilerplate? It's about company, maybe not needed? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company summary might be considered boilerplate? It's not exactly legal/EEO, but it's generic company description. Might be considered not substantive for the job? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Company summary could be considered substantive? It's about the employer, but not required for the job. Usually they'd keep it? The instruction didn't explicitly say to remove company summary. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company summary is not those. So we could keep it as a section maybe "About the company" but they didn't list that as a heading example. Could use "About the role" for job summary, and maybe "Company Overview" as a heading? Not in examples but could be okay. However they said prefer few substantive sections over many thin ones. Adding a company overview adds a section. Might be okay but we could incorporate into job summary? The job summary already includes description of role and location. Company summary is separate. Might be okay to keep as a

      under a heading like "About Galapagos Federal Systems, LLC". But they didn't forbid other headings. However they gave examples; we could still use other headings if needed. Safer to follow examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content: - About the role: Job Summary paragraph. - Responsibilities: Key Responsibilities list. - Requirements: maybe Security clearance and citizenship? But we have Skills And Experience which includes many items; could be Skills section. - Qualifications: Education and Certifications. - Skills: Skills And Experience (maybe combine with Requirements?). But we need to avoid duplication. Could treat Skills And Experience as Skills section. Then Requirements could be security clearance and citizenship (but those are already in Skills). Might be redundant. Better to follow: About the role (Job Summary), Responsibilities (Key Responsibilities), Skills (Skills And Experience), Qualifications (Education and Certifications), Benefits (Benefits), Pay (salary). Omit Requirements if not needed. We must not repeat job title as heading. Good. We need to output only HTML fragment. Let's extract content precisely. Job Summary paragraph: "Galapagos Federal Systems, LLC requires a dedicated Civil Engineering and Facilities Support Subject Matter Expert (SME) at Patrick Space Force Base (PSFB) and Cape Canaveral Space Force Station (CCSFS) to support the expanding portfolio of advanced space capability programs across the Eastern Range. This position provides critical expertise in civil engineering, facilities planning, and infrastructure coordination to ensure installation and program requirements are effectively integrated throughout the life-cycle of mission-critical projects. This senior-level role delivers direct, on-site support to the government's program office by providing strategic guidance on facility development, infrastructure investment planning, construction coordination, and program-driven space requirements. The position addresses a critical gap in Florida-based infrastructure support while ensuring continuity of planning and execution as programs transition from development and testing into fielded and operational capabilities at CCSFS and PSFB." That's one paragraph. Responsibilities list (Key Responsibilities). Each bullet starts with a verb. We'll capture each line. List: - Serve as the primary Civil Engineering and Facilities Subject Matter Expert (SME) supporting the government program office at Patrick Space Force Base (PSFB) and Cape Canaveral Space Force Station (CCSFS) - Provide strategic guidance on facility planning, infrastructure development, and installation support for advanced space capability programs across the Eastern Range - Coordinate with the Civil Engineer Squadron (CES), installation Public Works, and other installation stakeholders on facility requirements, space allocation, real property actions, and infrastructure planning - Support the planning, development, and review of facility investment documentation, including DD Form 1391 project justifications, for Military Construction (MILCON), facility sustainment, restoration, modernization, and renovation projects - Assist with infrastructure planning and facility integration activities supporting launch operations, test events, and mission-critical space systems - Coordinate Environmental, Safety, and Occupational Health (ESOH) requirements associated with facility construction, modification, and operational use - Conduct and support facility condition assessments, site surveys, space utilization studies, and infrastructure evaluations to identify current and future program requirements - Collaborate with Space Systems Command (SSC), installation organizations, and tenant units to resolve shared infrastructure and facility issues impacting supported programs - Track facility projects, infrastructure initiatives, and real property actions, providing regular status updates and recommendations to government leadership - Prepare reports, briefings, and documentation supporting program management, facility planning, infrastructure investments, and executive decision-making - Identify infrastructure risks, recommend mitigation strategies, and ensure facility planning aligns with mission objectives, installation priorities, and program schedules - Support cross-functional coordination between engineering, acquisition, construction, environmental, and operational stakeholders throughout the project life-cycle Skills And Experience list: - Active DoD Secret security clearance - 10+ years of experience supporting Department of Defense (DoD), U.S. Space Force (USSF), U.S. Air Force, or other federal civil engineering, facilities management, military construction, or infrastructure planning programs - Extensive knowledge of Air Force or Space Force Civil Engineer Squadron (CES) processes, facility management, real property administration, and installation support functions - Experience developing, reviewing, or supporting Military Construction (MILCON) documentation, including DD Form 1391 project programming packages - Strong understanding of facility planning, infrastructure investment planning, space utilization, and installation master planning - Experience coordinating with government organizations, installation leadership, engineers, architects, contractors, and program management offices - Direct experience supporting Eastern Range, launch infrastructure, Cape Canaveral Space Force Station, Patrick Space Force Base, or other mission-critical space facilities is highly preferred - Familiarity with Space Systems Command (SSC), DoD space acquisition programs, and infrastructure supporting space system development, integration, testing, and operations - Knowledge of Environmental, Safety, and Occupational Health (ESOH) requirements as they relate to facility construction and modification projects - Experience with Microsoft Office Suite (Word, Excel, PowerPoint, and Outlook) - Professional Engineer (PE) license or Engineer-in-Training (EIT) certification - Project Management Professional (PMP) certification - Experience supporting U.S. Space Force, Space Systems Command (SSC), Space Launch Delta 45, or other Eastern Range organizations - Experience with installation planning, facilities sustainment, restoration and modernization (FSRM), or installation development planning - Familiarity with Unified Facilities Criteria (UFC), DoD facility planning guidance, and Air Force Civil Engineer policies and procedures Education and Certifications: - Required Bachelor's degree in Civil Engineering, Architecture, Facilities Management, or related technical field (advanced degree desirable) Benefits list: - Medical, dental, vision, disability, and life insurance - Flexible Spending Accounts - 401(k) - PTO - Paid Parental Leave - Tuition reimbursement - Paid federal holidays Pay: "USD $150,000.00 - USD $180,000.00 /Yr." We should output as a

      maybe under Pay heading. Now ensure we don't include boilerplate: Company Summary, Company Employment Statement, Security Clearance duplicate, Physical Requirements? Actually Physical Requirements is present: "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." This is substantive; should we include? It's not in the example headings but could be a section like "Physical Requirements". However they said prefer few substantive sections over many thin ones. Could incorporate into About the role or Responsibilities? Might be better to have a "Requirements" section for physical requirements. But we already have Skills etc. Could add a "Requirements" section for physical requirements and maybe security clearance? But security clearance already in Skills. However we could keep Skills as is and add a separate "Requirements" for physical requirements. But that adds a thin section. Could we incorporate physical requirements into Skills? Not really a skill. Could add a "Requirements" section with physical requirements and maybe citizenship? But citizenship is duplicate. Given instruction to prefer few substantive sections, maybe we can omit physical requirements? But that would lose substantive info. However maybe it's considered boilerplate? It's not legal/EEO, it's job requirement. I'd keep it. We could add a section "Requirements" with physical requirements as a

      or

        . But we already have Skills section; maybe we can rename Skills to "Skills & Experience" and add another section "Requirements" for physical requirements. That's two sections. Alternatively, we could incorporate physical requirements into the About the role paragraph as an extra sentence? But that would be altering content (adding). Not allowed to invent or summarize away detail, but we could incorporate as a

        after About the role? Actually we could add a

        under About the role that includes the physical requirements? That would be adding content not originally there; but we could just keep it as a separate

        after About the role without a heading? The instruction: use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qual

Similar jobs

Senior Engineer

Tata Consultancy ServicesMonrovia, MD· 1 mo ago
Engineering$100k–$125k/yrapply on ibegin.tcsapps.com

Senior Engineer

RaftSan Antonio, TX· 1 mo ago
RemoteEngineering$140k–$160k/yrapply on grnh.se

Senior Engineer

Thompson EngineeringDaphne, AL· 1 mo ago
Engineeringapply on jobs.brassring.com

Senior Engineer

Thompson EngineeringMobile, AL· 1 mo ago
Engineeringapply on jobs.brassring.com

Senior Engineer

Thompson EngineeringPensacola, FL· 1 mo ago
Engineeringapply on jobs.brassring.com

Senior Engineer

Johnson & Johnson MedTechJacksonville, FL· 1 mo ago
Engineeringapply on careers.jnj.com