Jobs · Information Technology · Virginia

Satellite Systems Operations Engineer

Elveo · Chantilly, VA · 3 wk ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: About the role? Actually we have "About Elveo" description, then "Job Summary". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not repeat job title as heading. We need to include sections only when posting has real specific content. We have content: About Elveo (company description). Could map to "About the role"? Actually "About the role" is typical heading for role description. But we have "About Elveo" which is about company. Could treat as "About the role"? Might be better to use "About the role" heading and put the company description there? But the instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when we have content. We have content about the role: Job Summary and Core Responsibilities etc. So we could have sections: About the role (maybe combine Job Summary?), Responsibilities (Core Responsibilities), Requirements (Helpful Qualifications), Qualifications (maybe ITAR Requirements?), Skills (maybe not separate), Benefits (none), Pay (none), Schedule (none). We should not create sections with placeholder text. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none except maybe ITAR Requirements is substantive. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... company description and job summary ...

But we need to ensure we don't repeat job title as heading. The job title is "Satellite Operations Engineer". Not to be used as heading. We need to include "Job Summary" content inside About the role maybe. Let's extract: About Elveo paragraph: "Elveo is what happens when two pioneers in direct-to-device (D2D) communications join forces. Elveo brings together a combined 20 years of expertise to close the coverage gap for more than 50 mobile network operators (MNOs) and major distribution partners operating in 60+ countries worldwide. That heritage and our technology powers what we call ‘elevated intelligence’ — a new approach that processes and adapts on orbit, delivering voice and data services straight to mobile users, IoT devices and machines across enterprise, government and humanitarian sectors worldwide. As a team, we’re on a mission to deliver powerful compute and connectivity directly to individuals and objects everywhere on Earth. Join us, and become part of a globally inclusive company that is transforming satellite communications from a niche service to an essential global infrastructure, and democratizing connectivity for billions worldwide. Ready to take the next step? Join us." Job Summary: "The Satellite Operations Engineer at Elveo is a technical systems engineering position pivotal to ensuring the operational integrity and safety of the constellation of LEO satellites. Your primary responsibilities will encompass technical review and assessment of satellite telemetry, analyzing trends, leading investigations, conducting technical trades affecting satellite fleet operation, developing and evaluating concepts of operations, overseeing launch and early operations. Additionally, this role involves providing inputs and requirements to data analysis tools and operations workflows. This role works closely with the Principal Satellite Operations Systems Engineer, contributing to and executing against system-level investigations, operational strategies, and technical direction. This position is deeply technical. The ideal candidate is comfortable working through ambiguity to develop a clear, technically sound understanding of system behavior and operational approaches." Core Responsibilities list bullet points. In The First 12 Months list bullet points. Helpful Qualifications list bullet points. ITAR Requirements paragraph. Location: Chantilly. VA We need to decide sections. We could have:

About the role

About Elveo ... Job Summary ...

Responsibilities

  • Daily Telemetry Review: ...
  • ... etc. But we also have "In The First 12 Months" which could be part of Responsibilities or maybe separate section like "First 12 Months Expectations". Not in allowed headings list. Could incorporate into Responsibilities or maybe under "Responsibilities" as additional bullets. Helpful Qualifications could be under "Requirements" or "Qualifications". The allowed headings include Requirements, Qualifications, Skills. We need to decide. We have "Helpful Qualifications" which is a list of qualifications. Could map to "Qualifications". Also we have ITAR Requirements which is a requirement (citizenship). Could be under "Requirements". Could also include location maybe as a short p. We should not create sections with placeholder text. So we will create sections only for content we have. Thus:

    About the role

    About Elveo ... Job Summary ...

    Responsibilities

    • Daily Telemetry Review: Conduct thorough daily reviews of satellite telemetry data and alarms to monitor the health and performance of the satellite constellation.
    • Anomaly Investigation: Independently drive anomaly investigations end-to-end, from initial detection through root cause, corrective action, and verification, while developing a deep understanding of system behavior and implementing durable, long-term solutions.
    • Technical Trades: Engage in technical trades to optimize satellite operations, considering factors such as power consumption, communication bandwidth, and orbital dynamics.
    • Concepts of Operations and Automation Development: Collaborate with stakeholders to develop and evaluate concepts of operations, and automations, aimed at maximizing the productivity and efficiency of the satellite constellation. Effectively document and communicate new and existing operational concepts and automations.
    • Launch and Early Operations (LEOP): Provide technical oversight and support during satellite launch and early operations phases, ensuring smooth transitions into operational status.
    • Data Analysis Tools and Operations Workflows: Define and drive improvements to data analysis tools, operational workflows, and telemetry interpretation methods to enhance efficiency and effectiveness.
    Maybe also include "In The First 12 Months" as part of Responsibilities? Could add another
      but maybe better to add a separate section "First 12 Months" but not allowed heading. Could incorporate as part of Responsibilities with a heading? Not allowed. Could add a

      First 12 Months

      but not in allowed list; risk of violating instruction? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

      for section headings (e.g. ...)". It implies we should use those headings for sections. It might be okay to add other headings but better to stick to allowed ones. We could treat "In The First 12 Months" as part of Responsibilities or maybe as a subsection under Responsibilities using

      or

        with a leading bold text? But we need to preserve all substantive information; we can include it as a

        with a bold lead-in. Simplify: after Responsibilities

          , add a

          In the first 12 months:

          then a
            with those items. That preserves info without extra heading. Next, Requirements: we have ITAR Requirements and Location. Could also include "Helpful Qualifications" as Qualifications. We could have:

            Requirements

            ITAR Requirements: To comply with U.S. Government export control regulations (ITAR), applicants must be one of the following: (i) a U.S. citizen or national, (ii) a lawful permanent resident (green card holder), (iii) a refugee under 8 U.S.C. 1157, or (iv) an asylee under 8 U.S.C.1158. Individuals who do not meet these criteria must be eligible to obtain the necessary authorizations from the U.S. Department of State. For more information, please refer to the ITAR guidelines. Learn about ITAR here.

            Location: Chantilly, VA

            Then Qualifications:

            Qualifications

            • Proven experience in satellite operations, telemetry analysis, and anomaly resolution.
            • Proficiency in data analysis and systems analysis tools and techniques, such as STK, Matlab, python scripting, etc.
            • Typically 5–10 years of experience, with demonstrated ownership of spacecraft operations or system-level investigations.
            • Strong understanding and experience working with satellite flight software, attitude control algorithms, and space-to-ground interfaces.
            • Experience working with or interfacing closely with satellite flight software and onboard autonomy.
            • Experience in orbital dynamics, attitude control, or related disciplines is a plus, particularly when combined with spacecraft operations experience.
            • Familiarity with relevant industry standards and best practices in satellite operations and safety.
            We could also have Skills section but not needed. We should not include Benefits, Pay, Schedule as they are not present. We need to ensure we preserve all substantive information: we included About Elveo, Job Summary, Core Responsibilities, In The First 12 Months, Helpful Qualifications, ITAR Requirements, Location. Check for duplication: we didn't repeat any lines. We need to ensure we didn't include boilerplate like "Learn about ITAR here." That's part of the ITAR Requirements paragraph; it's substantive? It's a link reference; we can keep as text. We need to output only HTML fragment. Thus final output:

            About the role

            Elveo is what happens when two pioneers in direct-to-device (D2D) communications join forces. Elveo brings together a combined 20 years of expertise to close the coverage gap for more than 50 mobile network operators (MNOs) and major distribution partners operating in 60+ countries worldwide. That heritage and our technology powers what we call ‘elevated intelligence’ — a new approach that processes and adapts on orbit, delivering voice and data services straight to mobile users, IoT devices and machines across enterprise, government and humanitarian sectors worldwide. As a team, we’re on a mission to deliver powerful compute and connectivity directly to individuals and objects everywhere on Earth. Join us, and become part of a globally inclusive company that is transforming satellite communications from a niche service to an essential global infrastructure, and democratizing connectivity for billions worldwide. Ready to take the next step? Join us. The Satellite Operations Engineer at Elveo is a technical systems engineering position pivotal to ensuring the operational integrity and safety of the constellation of LEO satellites. Your primary responsibilities will encompass technical review and assessment of satellite telemetry, analyzing trends, leading investigations, conducting technical trades affecting satellite fleet operation, developing and evaluating concepts of operations, overseeing launch and early operations. Additionally, this role involves providing inputs and requirements to data analysis tools and operations workflows. This role works closely with the Principal Satellite Operations Systems Engineer, contributing to and executing against system-level investigations, operational strategies, and technical direction. This position is deeply technical. The ideal candidate is comfortable working through ambiguity to develop a clear, technically sound understanding of system behavior and operational approaches.

            Responsibilities

            • Daily Telemetry Review: Conduct thorough daily reviews of satellite telemetry data and alarms to monitor the health and performance of the satellite constellation.
            • Anomaly Investigation: Independently drive anomaly investigations end-to-end, from initial detection through root cause, corrective action, and verification, while developing a deep understanding of system behavior and implementing durable, long-term solutions.
            • Technical Trades: Engage in technical trades to optimize satellite operations, considering factors such as power consumption, communication bandwidth, and

Similar jobs