Sr. Embedded Flight Software Engineer

We need to output HTML fragment with sections: About the role? The posting includes responsibilities, requirements (basic, preferred), pay, benefits. Also maybe "Qualifications" could be combined with requirements. We must not repeat job title as heading. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove pay transparency boilerplate? The pay details are substantive; we need to include Pay section with salary ranges. The posting includes multiple location-based ranges; we need to preserve all substantive info. Should we list each location? Probably yes. Benefits: mention comprehensive package including paid time off, health and welfare insurance, 401(k). Also incentive eligible. We'll include Benefits section. We need to avoid headings with filler like "commensurate with experience". Not present. We need to include sections only when posting has real specific content. We'll have sections: Responsibilities, Requirements (maybe split Basic and Preferred?), Pay, Benefits. Could also have "Qualifications" but we can combine Requirements. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which are appropriate. We have Responsibilities, Requirements (basic and preferred), Pay, Benefits. Could also have Skills but we can include under Requirements. We'll not create Schedule as not present. We need to not repeat job title as heading. So start with maybe

  About the role

  ? The posting includes a brief intro: "Lanteris Space is currently seeking a Sr. Embedded Flight Software Engineer to join our team in Palo Alto, CA or Houston, TX." That's about the role. Could be About the role section. We'll include that as prose

  . Then Responsibilities

  Responsibilities

  with
  . Then Requirements

  Requirements

  maybe split into Basic and Preferred as subheadings? But we only allowed headings from list; we could still use

  Basic Requirements

  and

  Preferred Requirements

  though not in list but maybe okay? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we can use those exact headings; but we could also use others? Safer to stick to those. We could combine Basic and Preferred under Requirements with sub-lists? Could do

  Requirements

  then within that have

  Basic Requirements:

  then
  etc. But we need to use
  • for any list of duties/requirements/benefits. So we can have separate lists for basic and preferred. Pay:

    Pay

    with prose describing ranges. Could also list each location as
    . Benefits:

    Benefits

    with
    . We must not include application instructions, EEO, etc. Let's extract content. Intro: "Lanteris Space is currently seeking a Sr. Embedded Flight Software Engineer to join our team in Palo Alto, CA or Houston, TX." That's about the role. Responsibilities list: - Design and implement software for embedded Real-time Operating Systems (RTOS). - Develop, document, and maintain architectures, requirements, algorithms, interfaces, and designs for flight software systems - Develop software verification plans, unit level and open loop test suites, and procedures, executing the test procedures and documenting test results to ensure that software systems requirements are met. - Perform software product life cycle management. - Develop, select, tailor, and deploy software processes, tools, and metrics. - Serve as a subject matter expert for software domains, processes, and system-specific issues. Basic Requirements: - Must be a U.S. citizen or permanent resident - Bachelor’s degree in software engineering, computer science, or related field. Four additional years of experience may be substituted for a degree. - Minimum of 8 years of software development experience - Embedded C++ programming skills - Basic understanding of Agile methodologies and the software development life cycle - Software version control Preferred Requirements: - RTOS experience (ex. FreeRTOS) - Familiar with NASA’s cFS/cFE - Experience with SPI - Development experience with Python - Basic understanding of spacecraft subsystems: power, ADCS, thermal, propulsion, communications - Familiar with Jira, Jama, Git, and Unit test tools Pay section: The posting includes multiple location-based ranges. We need to preserve all. The text: "In support of pay transparency at Lanteris Space Systems, we disclose salary ranges on all U.S. job postings. The successful candidate’s starting pay will fall within the salary range provided below and is determined based on job-related factors, including, but not limited to, the experience, qualifications, knowledge, skills, geographic work location, and market conditions. Candidates with the minimum necessary experience, qualifications, knowledge, and skillsets for the position should not expect to receive the upper end of the pay range. The base pay for this position within Colorado is: $124,000.00 - $206,000.00 annually.The base pay for this position within New Jersey is: $124,000.00 - $206,000.00 annually.The base pay for this position within Delaware is: $124,000.00 - $206,000.00 annually.The base pay for this position within the Washington, DC metropolitan area is: $137,000.00 - $228,000.00 annually.The base pay for this position within California is: $143,000.00 - $238,000.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." We should include that as prose maybe with a
    of each location. The instruction: Use
    • for any list of duties/requirements/benefits. Pay is not a list but we could still list. Might be okay to use

      for prose and

      for each location. We'll do

      Pay

      then

      ... explanation

      then
      • Colorado: $124,000 - $206,000 annually
      etc. Benefits: "We offer a comprehensive package of benefits including paid time off, health and welfare insurance, and 401(k) to eligible employees. More information on our benefits will be shared with candidates as they move forward in the recruitment process. 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." We'll include Benefits

      Benefits

      with
      • Paid time off
      • Health and welfare insurance
      • 401(k) (eligible employees)
      • Incentive eligible (target based on contribution, company performance, individual results)
      We should not include the "More information on our benefits will be shared..." as it's not substantive? It's somewhat procedural; maybe we can omit as it's not a benefit. Keep only substantive benefits. Now ensure we removed boilerplate: EEO, application instructions, etc. Now produce HTML fragment. Let's craft:

      About the role

      Lanteris Space is currently seeking a Sr. Embedded Flight Software Engineer to join our team in Palo Alto, CA or Houston, TX.

      Responsibilities

      • Design and implement software for embedded Real-time Operating Systems (RTOS).
      • Develop, document, and maintain architectures, requirements, algorithms, interfaces, and designs for flight software systems
      • Develop software verification plans, unit level and open loop test suites, and procedures, executing the test procedures and documenting test results to ensure that software systems requirements are met.
      • Perform software product life cycle management.
      • Develop, select, tailor, and deploy software processes, tools, and metrics.
      • Serve as a subject matter expert for software domains, processes, and system-specific issues.

      Requirements

      Basic Requirements

      • Must be a U.S. citizen or permanent resident
      • Bachelor’s degree in software engineering, computer science, or related field. Four additional years of experience may be substituted for a degree.
      • Minimum of 8 years of software development experience
      • Embedded C++ programming skills
      • Basic understanding of Agile methodologies and the software development life cycle
      • Software version control

      Preferred Requirements

      • RTOS experience (ex. FreeRTOS)
      • Familiar with NASA’s cFS/cFE
      • Experience with SPI
      • Development experience with Python
      • Basic understanding of spacecraft subsystems: power, ADCS, thermal, propulsion, communications
      • Familiar with Jira, Jama, Git, and Unit test tools
      But we used

      which is not allowed? The instruction only said use

      for section headings. It didn't forbid other headings, but to be safe we could avoid

      and instead use

      for Basic Requirements and Preferred Requirements headings. However they said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other heading levels, but to be safe we can stick to

      only. We could combine Basic and Preferred under Requirements with separate

      headings (bold? but we can't use markdown). We could use inside

      . That's acceptable. So:

      Requirements

      Basic Requirements:

      ...

      Preferred Requirements:

      ...
      That uses

      for headings, not

      . That's okay. Now Pay:

      Pay

      The successful candidate’s starting pay will fall within the salary range provided below and is determined based on job-related factors, including experience, qualifications, knowledge, skills, geographic work location, and market conditions. Candidates with the minimum necessary experience, qualifications, knowledge, and skillsets for the position should not expect to receive the upper end of the pay range.

      • Colorado: $124,000 - $206,000 annually
      • New Jersey: $124,000 - $206,000 annually
      • Delaware: $124,000 - $206,000 annually
      • Washington, DC metropolitan area: $137,000 - $228,000 annually
      • California: $143,000 - $238,000 annually
      • For all other states, ranges are developed using geographic cost of labor and may vary by location.
      Benefits:

      Benefits