AI/ML Software Engineer
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
Content includes:
- Intro about Vantor (mission) – could be "About the role" or maybe "About the company". But we have to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have:
- Responsibilities: bullet list of duties (What You'll Do). That's a list.
- Requirements: Minimum Qualifications (Bachelor's degree, 5+ years, Java, etc.) and maybe also "To be eligible for this position, you must be a U.S. Person" etc. That's eligibility requirement.
- Qualifications: Preferred Qualifications (additional degrees, experience with orbital mechanics, etc.)
- Skills: maybe we could combine some but we have "Strong Java programming skills" etc. Could be under Requirements or Skills. But we need to decide sections.
- Benefits: described.
- Pay: salary ranges given.
- Schedule: core in-office days (Tuesday, Wednesday, Thursday) and occasional other days.
Thus we have content for all sections except maybe Skills separate; but we can include Skills if we have specific skill list. The posting mentions "Strong Java programming skills, including working in a Spring-boot micro-service environment", "Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment", "Experience developing machine learning and/or optimization systems". Those could be considered skills. But we already have Requirements (minimum qualifications) and Preferred Qualifications. Could put skills under Requirements or separate. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But they ask to use headings from list; we can include multiple sections if they have substantive content. We have substantive content for Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. That's six sections. Could also include About the role (intro). That would be seven.
We need to avoid duplication: The posting repeats eligibility statements twice; we should include only once.
We need to remove boilerplate: EEO, application instructions, etc. Also remove duplicated lines like "To be eligible for this position, you must be a U.S. Person..." repeated, also "Please review the job details below." repeated. Also remove "The application window is three days..." etc. Also remove EEO policy.
We need to preserve all substantive information: mission description, responsibilities, minimum qualifications, preferred qualifications, benefits, pay, schedule.
We need to format as HTML: use
for each section heading. Under each heading, use
for prose,
- for lists.
We need to decide what goes where.
Section "About the role": could contain the introductory paragraph about Vantor mission and the role description: "We are seeking a Software Engineer with strong AI/ML experience to join a team that develops and maintains autonomous planning, scheduling, and optimization systems for advanced Earth Observation satellite operations. This role focuses on applying reinforcement learning (RL), operations research, and sequential decision-making techniques to optimize heterogenous satellite constellation collection plans. You will be joining an onsite team located in the Herndon, VA or Westminster, CO office with core in-office days on Tuesday, Wednesday, and Thursdays. Other days may occasionally be required to support customer or mission-related activities."
But note schedule info could go under Schedule section; but we could keep schedule details there. However the intro includes location and schedule; we could keep location in About the role, schedule in Schedule section.
Thus About the role: mission description and maybe location.
Responsibilities: bullet list of duties (What You'll Do). That's four bullet points.
Requirements: Minimum Qualifications bullet list? Could be prose. We'll use
- for list.
Qualifications: Preferred Qualifications bullet list.
Skills: maybe we could skip if we think it's thin; but we have some skill statements that could be considered under Requirements or Qualifications. However we already have Minimum Qualifications includes "Strong Java programming skills, including working in a Spring-boot micro-service environment" and "Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment". Those are skills. Could be part of Minimum Qualifications. So we may not need separate Skills section.
Benefits: paragraph about benefits plus link.
Pay: salary ranges.
Schedule: core in-office days and occasional other days.
We must not include filler like "commensurate with experience". Not present.
Now we need to ensure we don't include any boilerplate like EEO, application instructions, etc.
Let's extract substantive content:
Intro about Vantor: "Vantor is forging the new frontier of spatial intelligence, helping decision makers and operators navigate what’s happening now and shape what’s coming next. Vantor is a place for problem solvers, changemakers, and go-getters—where people are working together to help our customers see the world differently, and in doing so, be seen differently. Come be part of a mission, not just a job, where you can: Shape your own future, build the next big thing, and change the world."
Then eligibility: "To be eligible for this position, you must be a U.S. Person, defined as a U.S. citizen, permanent resident, Asylee, or Refugee. Export Control/ITAR: Certain roles may be subject to U.S. export control laws, requiring U.S. person status as defined by 8 U.S.C. 1324b(a)(3). Please review the job details below." Also later: "To be eligible for this position, you must be a U.S. Citizen." There's some conflict; but we need to preserve both statements? The posting repeats eligibility with slight variation. We should preserve the substantive info: must be a U.S. Person (citizen, permanent resident, asylee, refugee) and also must be a U.S. Citizen (maybe stricter). We could combine: must be a U.S. Citizen (or U.S. Person as defined). But we should not invent; we can include both statements as they appear, but we need to avoid duplication. The two statements are similar but not identical; we could keep the more specific: "To be eligible for this position, you must be a U.S. Citizen." However the first statement includes permanent resident, asylee, refugee. The second says must be a U.S. Citizen. Which is correct? The posting includes both; we need to preserve ALL substantive information; we cannot discard either if it's substantive. But we can combine them into a single statement that captures both: "To be eligible for this position, you must be a U.S. Person (U.S. citizen, permanent resident, asylee, or refugee); additionally, this role requires U.S. Citizen status." However that might be interpreting. Safer to include both statements as separate sentences, but ensure not duplicate exactly. They are not identical; we can keep both.
But we also have "Export Control/ITAR: Certain roles may be subject to U.S. export control laws, requiring U.S. person status as defined by 8 U.S.C. 1324b(a)(3). Please review the job details below." That's also substantive.
We also have "Please review the job details below." repeated; we can keep one.
We need to decide where to place eligibility. Could be under Requirements (maybe as a note). Or we could have a separate section like "Eligibility". But not in allowed headings. Could fold into Requirements or About the role. Probably under Requirements as a note.
Now responsibilities: list:
- Support the design and implement of scalable reinforcement learning (RL), optimization, and decision-making algorithms for satellite sensor and constellation tasking and planning
- Support building high-fidelity simulation and evaluation environments for training and validating autonomous planning strategies under real-world operational constraints
- Develop multi-objective optimization pipelines balancing coverage, revisit rate, latency, resource utilization, revenue, and mission success metrics
- Collaborate with aerospace engineers, mission operators, software engineers, and product teams to translate mission requirements into deployable AI systems
Note: first bullet says "Support the design and implement" maybe typo; keep as is.
Minimum Qualifications:
- Bachelor’s Degree in Computer Science or strongly related field
- 5+ years of software development experience with recent use of modern AI-assisted technologies (e.g., Augment, Codex, etc.)
- Strong Java programming skills, including working in a Spring-boot micro-service environment
- Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment
- Experience developing machine learning and/or optimization systems
Preferred Qualifications:
- Addition degrees or certifications in Data Science, Aerospace Engineering, Applied Mathematics, Physics, or related field
- Experience with orbital mechanics, satellite systems, remote sensing, mission operations, and collection planning
- Experience with probabilistic modeling, uncertainty estimation, and Bayesian optimization algorithms
- Familiarity with GPU acceleration and distributed training infrastructure
- Experience with autonomous systems or multi-agent planning architectures
Benefits:
- Vantor offers a competitive total rewards package that goes beyond the standard, including a robust 401(k) with company match, mental health resources, and unique perks like student loan repayment assistance, adoption reimbursement and pet insurance to support all aspects of your life.
- You can find more information on our benefits at: https://www.Vantor.com/careers
- Additionally, this position is incentive eligible with a target based on contribution, company performance, and/or individual results achieved; the specific incentive plan and target amount will be determined based on the role and breadth of contributions.
Pay:
- The base pay for this position within Colorado is: $105,000.00 - $140,000.00 - $154,000.00 annually.
- The base pay for this position within the Washington, DC metropolitan area is: $116,000.00 - $154,000.00 - $169,400.00 annually.
- For all other states, we use geographic cost of labor as an input to develop market-driven ranges for our roles, and as such, each location where we hire may have a different range.
Schedule:
- You will be joining an onsite team located in the Herndon, VA or Westminster, CO office with core in-office days on Tuesday, Wednesday, and Thursdays.
- Other days may occasionally be required to support customer or mission-related activities.
We also have location info in About the role maybe.
Now we need to ensure we don't include any boilerplate like "EEO Policy", "application window", "To apply", etc.
Now produce HTML.
Structure:
About the role
Vantor is forging the new frontier of spatial intelligence, helping decision makers and operators navigate what’s happening now and shape what’s coming next. Vantor is a place for problem solvers, changemakers, and go-getters—where people
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. Content includes: - Intro about Vantor (mission) – could be "About the role" or maybe "About the company". But we have to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - Responsibilities: bullet list of duties (What You'll Do). That's a list. - Requirements: Minimum Qualifications (Bachelor's degree, 5+ years, Java, etc.) and maybe also "To be eligible for this position, you must be a U.S. Person" etc. That's eligibility requirement. - Qualifications: Preferred Qualifications (additional degrees, experience with orbital mechanics, etc.) - Skills: maybe we could combine some but we have "Strong Java programming skills" etc. Could be under Requirements or Skills. But we need to decide sections. - Benefits: described. - Pay: salary ranges given. - Schedule: core in-office days (Tuesday, Wednesday, Thursday) and occasional other days. Thus we have content for all sections except maybe Skills separate; but we can include Skills if we have specific skill list. The posting mentions "Strong Java programming skills, including working in a Spring-boot micro-service environment", "Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment", "Experience developing machine learning and/or optimization systems". Those could be considered skills. But we already have Requirements (minimum qualifications) and Preferred Qualifications. Could put skills under Requirements or separate. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But they ask to use headings from list; we can include multiple sections if they have substantive content. We have substantive content for Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. That's six sections. Could also include About the role (intro). That would be seven. We need to avoid duplication: The posting repeats eligibility statements twice; we should include only once. We need to remove boilerplate: EEO, application instructions, etc. Also remove duplicated lines like "To be eligible for this position, you must be a U.S. Person..." repeated, also "Please review the job details below." repeated. Also remove "The application window is three days..." etc. Also remove EEO policy. We need to preserve all substantive information: mission description, responsibilities, minimum qualifications, preferred qualifications, benefits, pay, schedule. We need to format as HTML: use
for each section heading. Under each heading, use
for prose,
- for lists.
We need to decide what goes where.
Section "About the role": could contain the introductory paragraph about Vantor mission and the role description: "We are seeking a Software Engineer with strong AI/ML experience to join a team that develops and maintains autonomous planning, scheduling, and optimization systems for advanced Earth Observation satellite operations. This role focuses on applying reinforcement learning (RL), operations research, and sequential decision-making techniques to optimize heterogenous satellite constellation collection plans. You will be joining an onsite team located in the Herndon, VA or Westminster, CO office with core in-office days on Tuesday, Wednesday, and Thursdays. Other days may occasionally be required to support customer or mission-related activities."
But note schedule info could go under Schedule section; but we could keep schedule details there. However the intro includes location and schedule; we could keep location in About the role, schedule in Schedule section.
Thus About the role: mission description and maybe location.
Responsibilities: bullet list of duties (What You'll Do). That's four bullet points.
Requirements: Minimum Qualifications bullet list? Could be prose. We'll use
- for list.
Qualifications: Preferred Qualifications bullet list.
Skills: maybe we could skip if we think it's thin; but we have some skill statements that could be considered under Requirements or Qualifications. However we already have Minimum Qualifications includes "Strong Java programming skills, including working in a Spring-boot micro-service environment" and "Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment". Those are skills. Could be part of Minimum Qualifications. So we may not need separate Skills section.
Benefits: paragraph about benefits plus link.
Pay: salary ranges.
Schedule: core in-office days and occasional other days.
We must not include filler like "commensurate with experience". Not present.
Now we need to ensure we don't include any boilerplate like EEO, application instructions, etc.
Let's extract substantive content:
Intro about Vantor: "Vantor is forging the new frontier of spatial intelligence, helping decision makers and operators navigate what’s happening now and shape what’s coming next. Vantor is a place for problem solvers, changemakers, and go-getters—where people are working together to help our customers see the world differently, and in doing so, be seen differently. Come be part of a mission, not just a job, where you can: Shape your own future, build the next big thing, and change the world."
Then eligibility: "To be eligible for this position, you must be a U.S. Person, defined as a U.S. citizen, permanent resident, Asylee, or Refugee. Export Control/ITAR: Certain roles may be subject to U.S. export control laws, requiring U.S. person status as defined by 8 U.S.C. 1324b(a)(3). Please review the job details below." Also later: "To be eligible for this position, you must be a U.S. Citizen." There's some conflict; but we need to preserve both statements? The posting repeats eligibility with slight variation. We should preserve the substantive info: must be a U.S. Person (citizen, permanent resident, asylee, refugee) and also must be a U.S. Citizen (maybe stricter). We could combine: must be a U.S. Citizen (or U.S. Person as defined). But we should not invent; we can include both statements as they appear, but we need to avoid duplication. The two statements are similar but not identical; we could keep the more specific: "To be eligible for this position, you must be a U.S. Citizen." However the first statement includes permanent resident, asylee, refugee. The second says must be a U.S. Citizen. Which is correct? The posting includes both; we need to preserve ALL substantive information; we cannot discard either if it's substantive. But we can combine them into a single statement that captures both: "To be eligible for this position, you must be a U.S. Person (U.S. citizen, permanent resident, asylee, or refugee); additionally, this role requires U.S. Citizen status." However that might be interpreting. Safer to include both statements as separate sentences, but ensure not duplicate exactly. They are not identical; we can keep both.
But we also have "Export Control/ITAR: Certain roles may be subject to U.S. export control laws, requiring U.S. person status as defined by 8 U.S.C. 1324b(a)(3). Please review the job details below." That's also substantive.
We also have "Please review the job details below." repeated; we can keep one.
We need to decide where to place eligibility. Could be under Requirements (maybe as a note). Or we could have a separate section like "Eligibility". But not in allowed headings. Could fold into Requirements or About the role. Probably under Requirements as a note.
Now responsibilities: list:
- Support the design and implement of scalable reinforcement learning (RL), optimization, and decision-making algorithms for satellite sensor and constellation tasking and planning
- Support building high-fidelity simulation and evaluation environments for training and validating autonomous planning strategies under real-world operational constraints
- Develop multi-objective optimization pipelines balancing coverage, revisit rate, latency, resource utilization, revenue, and mission success metrics
- Collaborate with aerospace engineers, mission operators, software engineers, and product teams to translate mission requirements into deployable AI systems
Note: first bullet says "Support the design and implement" maybe typo; keep as is.
Minimum Qualifications:
- Bachelor’s Degree in Computer Science or strongly related field
- 5+ years of software development experience with recent use of modern AI-assisted technologies (e.g., Augment, Codex, etc.)
- Strong Java programming skills, including working in a Spring-boot micro-service environment
- Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment
- Experience developing machine learning and/or optimization systems
Preferred Qualifications:
- Addition degrees or certifications in Data Science, Aerospace Engineering, Applied Mathematics, Physics, or related field
- Experience with orbital mechanics, satellite systems, remote sensing, mission operations, and collection planning
- Experience with probabilistic modeling, uncertainty estimation, and Bayesian optimization algorithms
- Familiarity with GPU acceleration and distributed training infrastructure
- Experience with autonomous systems or multi-agent planning architectures
Benefits:
- Vantor offers a competitive total rewards package that goes beyond the standard, including a robust 401(k) with company match, mental health resources, and unique perks like student loan repayment assistance, adoption reimbursement and pet insurance to support all aspects of your life.
- You can find more information on our benefits at: https://www.Vantor.com/careers
- Additionally, this position is incentive eligible with a target based on contribution, company performance, and/or individual results achieved; the specific incentive plan and target amount will be determined based on the role and breadth of contributions.
Pay:
- The base pay for this position within Colorado is: $105,000.00 - $140,000.00 - $154,000.00 annually.
- The base pay for this position within the Washington, DC metropolitan area is: $116,000.00 - $154,000.00 - $169,400.00 annually.
- For all other states, we use geographic cost of labor as an input to develop market-driven ranges for our roles, and as such, each location where we hire may have a different range.
Schedule:
- You will be joining an onsite team located in the Herndon, VA or Westminster, CO office with core in-office days on Tuesday, Wednesday, and Thursdays.
- Other days may occasionally be required to support customer or mission-related activities.
We also have location info in About the role maybe.
Now we need to ensure we don't include any boilerplate like "EEO Policy", "application window", "To apply", etc.
Now produce HTML.
Structure:
About the role
Vantor is forging the new frontier of spatial intelligence, helping decision makers and operators navigate what’s happening now and shape what’s coming next. Vantor is a place for problem solvers, changemakers, and go-getters—where people
- for list.
Qualifications: Preferred Qualifications bullet list.
Skills: maybe we could skip if we think it's thin; but we have some skill statements that could be considered under Requirements or Qualifications. However we already have Minimum Qualifications includes "Strong Java programming skills, including working in a Spring-boot micro-service environment" and "Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment". Those are skills. Could be part of Minimum Qualifications. So we may not need separate Skills section.
Benefits: paragraph about benefits plus link.
Pay: salary ranges.
Schedule: core in-office days and occasional other days.
We must not include filler like "commensurate with experience". Not present.
Now we need to ensure we don't include any boilerplate like EEO, application instructions, etc.
Let's extract substantive content:
Intro about Vantor: "Vantor is forging the new frontier of spatial intelligence, helping decision makers and operators navigate what’s happening now and shape what’s coming next. Vantor is a place for problem solvers, changemakers, and go-getters—where people are working together to help our customers see the world differently, and in doing so, be seen differently. Come be part of a mission, not just a job, where you can: Shape your own future, build the next big thing, and change the world."
Then eligibility: "To be eligible for this position, you must be a U.S. Person, defined as a U.S. citizen, permanent resident, Asylee, or Refugee. Export Control/ITAR: Certain roles may be subject to U.S. export control laws, requiring U.S. person status as defined by 8 U.S.C. 1324b(a)(3). Please review the job details below." Also later: "To be eligible for this position, you must be a U.S. Citizen." There's some conflict; but we need to preserve both statements? The posting repeats eligibility with slight variation. We should preserve the substantive info: must be a U.S. Person (citizen, permanent resident, asylee, refugee) and also must be a U.S. Citizen (maybe stricter). We could combine: must be a U.S. Citizen (or U.S. Person as defined). But we should not invent; we can include both statements as they appear, but we need to avoid duplication. The two statements are similar but not identical; we could keep the more specific: "To be eligible for this position, you must be a U.S. Citizen." However the first statement includes permanent resident, asylee, refugee. The second says must be a U.S. Citizen. Which is correct? The posting includes both; we need to preserve ALL substantive information; we cannot discard either if it's substantive. But we can combine them into a single statement that captures both: "To be eligible for this position, you must be a U.S. Person (U.S. citizen, permanent resident, asylee, or refugee); additionally, this role requires U.S. Citizen status." However that might be interpreting. Safer to include both statements as separate sentences, but ensure not duplicate exactly. They are not identical; we can keep both.
But we also have "Export Control/ITAR: Certain roles may be subject to U.S. export control laws, requiring U.S. person status as defined by 8 U.S.C. 1324b(a)(3). Please review the job details below." That's also substantive.
We also have "Please review the job details below." repeated; we can keep one.
We need to decide where to place eligibility. Could be under Requirements (maybe as a note). Or we could have a separate section like "Eligibility". But not in allowed headings. Could fold into Requirements or About the role. Probably under Requirements as a note.
Now responsibilities: list:
- Support the design and implement of scalable reinforcement learning (RL), optimization, and decision-making algorithms for satellite sensor and constellation tasking and planning
- Support building high-fidelity simulation and evaluation environments for training and validating autonomous planning strategies under real-world operational constraints
- Develop multi-objective optimization pipelines balancing coverage, revisit rate, latency, resource utilization, revenue, and mission success metrics
- Collaborate with aerospace engineers, mission operators, software engineers, and product teams to translate mission requirements into deployable AI systems
Note: first bullet says "Support the design and implement" maybe typo; keep as is.
Minimum Qualifications:
- Bachelor’s Degree in Computer Science or strongly related field
- 5+ years of software development experience with recent use of modern AI-assisted technologies (e.g., Augment, Codex, etc.)
- Strong Java programming skills, including working in a Spring-boot micro-service environment
- Strong software engineering fundamentals including automated testing, CI/CD, version-control, and containerized deployment
- Experience developing machine learning and/or optimization systems
Preferred Qualifications:
- Addition degrees or certifications in Data Science, Aerospace Engineering, Applied Mathematics, Physics, or related field
- Experience with orbital mechanics, satellite systems, remote sensing, mission operations, and collection planning
- Experience with probabilistic modeling, uncertainty estimation, and Bayesian optimization algorithms
- Familiarity with GPU acceleration and distributed training infrastructure
- Experience with autonomous systems or multi-agent planning architectures
Benefits:
- Vantor offers a competitive total rewards package that goes beyond the standard, including a robust 401(k) with company match, mental health resources, and unique perks like student loan repayment assistance, adoption reimbursement and pet insurance to support all aspects of your life.
- You can find more information on our benefits at: https://www.Vantor.com/careers
- Additionally, this position is incentive eligible with a target based on contribution, company performance, and/or individual results achieved; the specific incentive plan and target amount will be determined based on the role and breadth of contributions.
Pay:
- The base pay for this position within Colorado is: $105,000.00 - $140,000.00 - $154,000.00 annually.
- The base pay for this position within the Washington, DC metropolitan area is: $116,000.00 - $154,000.00 - $169,400.00 annually.
- For all other states, we use geographic cost of labor as an input to develop market-driven ranges for our roles, and as such, each location where we hire may have a different range.
Schedule:
- You will be joining an onsite team located in the Herndon, VA or Westminster, CO office with core in-office days on Tuesday, Wednesday, and Thursdays.
- Other days may occasionally be required to support customer or mission-related activities.
We also have location info in About the role maybe.
Now we need to ensure we don't include any boilerplate like "EEO Policy", "application window", "To apply", etc.
Now produce HTML.
Structure: