Mission Dev Engineer - Internship (Summer 2027)

We need to output HTML fragment with sections: About the role? Actually we have "About Nominal" description, then "The role", then bullet list of responsibilities (What you’ll do), then "Reach out if…" which is qualifications/requirements, then Benefits/Perks. Also maybe "ITAR Requirements" is a requirement but it's a legal requirement; we should include as part of Requirements? The instruction: remove EEO/equal-opportunity/boilerplate, but ITAR is a requirement, not boilerplate? It's a legal requirement for the role; we should keep it. It's not EEO; it's a specific eligibility requirement. So we should include it under Requirements or Qualifications. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have About Nominal (company description) - could be "About the role"? Actually "About Nominal" is about company, not role. The instruction says use headings like About the role, Responsibilities, etc. We could use "About the role" for the description of the role? But we have "The role" section describing what you'll do? Actually "The role" is a short paragraph: "We’re looking for students...". Then "What you’ll do" is responsibilities. Then "Reach out if…" is qualifications/requirements. Then "Benefits/Perks". Also there is ITAR requirement. We need to decide headings: Perhaps "About the role" for the paragraph describing the role (the "We’re looking for students..."). Then "Responsibilities" for the bullet list under "What you’ll do". Then "Requirements" for the "Reach out if…" bullet list plus ITAR requirement. Then "Benefits" for the benefits list. No Pay or Schedule info given, so omit those sections. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information. So include company description? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It didn't say to drop company description. The "About Nominal" is substantive; we could include it as a section maybe "About the company"? But headings list only includes About the role, Responsibilities, etc. Not About the company. However we could treat "About Nominal" as part of "About the role"? Might be okay to include as a

before headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to those. So we could add a heading like "About Nominal" if we want, but they gave examples; but we can still use other headings? Safer to stick to given examples. Could we put company description under a heading like "About the role"? That might be odd but acceptable. Or we could just put it as a

before any headings, as minor metadata? It's not minor; it's substantive. But we could treat it as part of the role description. Better: Use heading "About the role" and include the Nominal description plus the role overview paragraph. Then Responsibilities, Requirements, Benefits. Let's extract content: About Nominal paragraph: "Nominal is building the connected test and operations platform powering the world's most advanced hardware systems, from spacecraft and autonomous vehicles to next-generation defense programs. Our platform gives hardware engineering teams a single place to ingest data, analyze performance, automate test execution, and collaborate across every phase of development, so they can move faster without sacrificing safety or precision. We're a fast-moving team that owns problems end-to-end, works across disciplines, and thrives at the intersection of hardware and software. We serve top-tier commercial and defense customers, from autonomy leaders like Anduril and Shield AI to next-generation aerospace teams like Hermeus and REGENT, and performance engineering teams like Pratt Miller Motorsports, alongside mission partners within the U.S. Navy and U.S. Air Force on programs where failure isn’t an option. We’re backed by Sequoia, General Catalyst, Founders Fund, Lux Capital, and Lightspeed. Our team draws from SpaceX, Palantir, Anduril, Applied Intuition, and other leading companies, united by a common mission: giving hardware engineers the tools to build the future with speed, safety, and confidence." Then "The role" paragraph: "We’re looking for students with solid engineering fundamentals interested in a Summer 2027 internship and on track to graduate in Summer 2028 or sooner. As a Mission Dev (forward deployed software engineering) intern at Nominal, you’ll work directly with engineers building and testing complex hardware systems like nuclear reactors, rockets, and supersonic aircraft. You’ll learn how our customers work, understand what’s slowing them down, and build software that helps them move faster. The role combines hands-on software engineering with product judgment: figuring out what to build, shipping it, and working with users to make sure it solves their problem." Then bullet list under "🚀 What you’ll do": each line starts with an emoji? Actually bullet points preceded by emojis? The text: 🚀 What you’ll do Work directly with customer engineers to understand their testing and analysis workflows and identify problems you can solve with software Design and build integrations, data pipelines, and applications that connect Nominal to our customers’ systems and help them work with high-frequency, high-volume hardware data Own projects from understanding the problem through building, deploying, and supporting the solution, with mentorship from experienced engineers and domain experts Put working software in users’ hands early, learn from how they use it, and iterate quickly based on their feedback Bring what you learn back to our product and engineering teams, helping turn solutions for individual customers into capabilities that benefit many We need to turn into

• . Then "🎯 Reach out if…" bullet list: You’re on track to graduate by Summer 2028 and are open to a full-time role afterward You have strong core engineering skills and hands-on experience building software, whether through internships, personal projects, or academic work You want to work directly with the people using your software and understand whether what you’ve built is making a difference You’re excited to work through open-ended problems, learn unfamiliar systems, and figure out what’s needed to get a solution into use You have a personal passion for solving challenging problems and contributing to the future of critical infrastructure Your peers would describe you as ambitious, resourceful, and perseverant Then "✨ Benefits/Perks" list: Receive mentorship from our world-class team Trips to co-locate with the team across our different offices Free lunch, dinner, snacks, and drinks A beginning-of-internship swag bag and an end-of-internship intern gift In-office hardware lab with a $250 project stipend Then EEO statement: "All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, or national origin." This is boilerplate EEO; we should remove. Then ITAR Requirements paragraph: "To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. 1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State. Learn more about the ITAR here." We should keep ITAR requirement as part of Requirements. Thus sections:

  About the role

  containing Nominal description + role overview paragraph (maybe two

  s).

  Responsibilities

  with
  of the five items.

  Requirements

  with
  of the six bullet points plus ITAR requirement maybe as a

  after list or as another

  • . Could incorporate ITAR as a
  • within Requirements. We should not include Benefits heading if there is content; yes we have benefits. Thus

    Benefits

    with
    of five items. We must not add Pay or Schedule. Make sure to preserve all info, no extra. Let's craft HTML. We'll output:

    About the role

    Nominal is building the connected test and operations platform powering the world's most advanced hardware systems, from spacecraft and autonomous vehicles to next-generation defense programs. Our platform gives hardware engineering teams a single place to ingest data, analyze performance, automate test execution, and collaborate across every phase of development, so they can move faster without sacrificing safety or precision. We're a fast-moving team that owns problems end-to-end, works across disciplines, and thrives at the intersection of hardware and software. We serve top-tier commercial and defense customers, from autonomy leaders like Anduril and Shield AI to next-generation aerospace teams like Hermeus and REGENT, and performance engineering teams like Pratt Miller Motorsports, alongside mission partners within the U.S. Navy and U.S. Air Force on programs where failure isn’t an option. We’re backed by Sequoia, General Catalyst, Founders Fund, Lux Capital, and Lightspeed. Our team draws from SpaceX, Palantir, Anduril, Applied Intuition, and other leading companies, united by a common mission: giving hardware engineers the tools to build the future with speed, safety, and confidence.

    We’re looking for students with solid engineering fundamentals interested in a Summer 2027 internship and on track to graduate in Summer 2028 or sooner. As a Mission Dev (forward deployed software engineering) intern at Nominal, you’ll work directly with engineers building and testing complex hardware systems like nuclear reactors, rockets, and supersonic aircraft. You’ll learn how our customers work, understand what’s slowing them down, and build software that helps them move faster. The role combines hands-on software engineering with product judgment: figuring out what to build, shipping it, and working with users to make sure it solves their problem.

    Responsibilities

    • Work directly with customer engineers to understand their testing and analysis workflows and identify problems you can solve with software
    • Design and build integrations, data pipelines, and applications that connect Nominal to our customers’ systems and help them work with high-frequency, high-volume hardware data
    • Own projects from understanding the problem through building, deploying, and supporting the solution, with mentorship from experienced engineers and domain experts
    • Put working software in users’ hands early, learn from how they use it, and iterate quickly based on their feedback
    • Bring what you learn back to our product and engineering teams, helping turn solutions for individual customers into capabilities that benefit many

    Requirements

    • You’re on track to graduate by Summer 2028 and are open to a full-time role afterward
    • You have strong core engineering skills and hands-on experience building software, whether through internships, personal projects, or academic work
    • You want to work directly with the people using your software and understand whether what you’ve built is making a difference
    • You’re excited to work through open-ended problems, learn unfamiliar systems, and figure out what’s needed to get a solution into use
    • You have a personal passion for solving challenging problems and contributing to the future of critical infrastructure
    • Your peers would describe you as ambitious, resourceful, and perseverant