Principal Electrical Engineer, AI Satellites (Starmind)
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove ITAR? ITAR is a requirement; it's substantive. Should we keep? It's a requirement about citizenship. It's part of Additional Requirements. So keep.
We need to avoid repeating job title as heading. The title is "PRINCIPAL ELECTRICAL HARDWARE ENGINEER, AI SATELLITES (STARMIND)". We should not put that as heading.
We need to decide sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine Basic Qualifications and Preferred Skills? The instruction: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. Likely:
- About the role: introductory paragraph describing SpaceX, Starmind, role.
- Responsibilities: the bullet list under "Responsibilities".
- Requirements: maybe Basic Qualifications? Or could be "Requirements" for mandatory items (Basic Qualifications + Additional Requirements like ITAR, ability to work extended hours, travel). We'll include.
- Qualifications: maybe Preferred Skills And Experience (preferred qualifications). Or could split: Qualifications for education, Skills for technical skills. But we have both Basic Qualifications and Preferred Skills And Experience. We could treat Basic Qualifications as "Requirements" and Preferred Skills And Experience as "Qualifications". Or we could put Basic Qualifications under "Requirements" and Preferred Skills under "Skills". However the instruction list includes both Qualifications and Skills sections. We need to decide mapping.
We have:
- Basic Qualifications: Bachelor’s degree, 10+ years experience.
- Preferred Skills And Experience: Master’s degree, 2+ years rapid design, 2+ years electronic product experience, 2+ years mixed-signal circuit boards, testing/troubleshooting, understanding of computers and programming languages, ability to work cross-functional, 2+ years aerospace systems.
- Additional Requirements: ability to work extended hours or weekends, some travel, ITAR requirements.
Thus we could map:
- Requirements: Basic Qualifications + Additional Requirements (mandatory). Could also include ITAR etc.
- Qualifications: Preferred Skills And Experience (preferred qualifications). Or maybe Qualifications for education/degree, Skills for technical skills. But we have both degree and experience in Preferred Skills. Could split: Qualifications for education (Master's degree) and Skills for technical skills (mixed-signal, programming, etc). However the instruction says prefer a few substantive sections over many thin ones. So maybe combine Preferred Skills And Experience into a single "Qualifications" section (since they are qualifications/preferred). And maybe we don't need a separate "Skills" section if we already covered skills in Qualifications. But we have a separate "Skills" heading in the list; we could omit if no specific skills content beyond what's in Qualifications. However we have technical skills like mixed-signal, FPGAs, Ethernet, etc. Those could go under Skills. But we can also include them under Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. We'll include About the role, Responsibilities, Requirements, Qualifications. Skip Skills, Benefits, Pay, Schedule if not present.
Thus output:
About the role
SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. PRINCIPAL ELECTRICAL HARDWARE ENGINEER, AI SATELLITES (STARMIND) SpaceX is leveraging its experience deploying and operating the world’s largest satellite constellation to develop Starmind, a new constellation of satellites capturing solar energy in space to power low-cost, high-performance AI compute for Earth. Realizing this vision demands highly reliable, high performance electrical hardware ranging from power electronics, high speed digital systems, mixed signal designs, robust avionics, networking, and custom compute electronics. These systems must operate in the extreme environment of space while delivering the connectivity, control, power distribution, and processing needed for orbital AI inference. The Starmind team designs, builds, and operates the orbital compute fabric of the future. We develop nearly every key piece of technology in house – from the satellites’ flight computers and power systems to the fully custom compute electronics, memory, and networking that form the brain of our on-orbit data centers. As an engineer on the Starmind Payload Engineering team, you’ll have ownership over the entire life-cycle of the hardware that enables advanced on-orbit AI processing and data center workloads. Your work sits at the intersection of electrical, mechanical, thermal, and software engineering. The Payload team is responsible for the design of industry-leading compute electronics, memory, and networking in order to achieve required domain sizes and processing workloads.
Responsibilities
- Rapidly develop high-reliability electronics for satellites and spacecraft.
- Drive system trades, requirements capture, component selection, analysis, schematic capture, PCB layout, prototyping, hardware bring-up, debugging, documentation, manufacturing, test, and on-orbit performance of complex electrical designs
- Get hands-on and support hardware through production, satellite integration, and flight
- Determine layer stackup, perform component package selection, component placement, routing feasibility studies, and signal routing of digital, analog, RF, and power conversion of PCBs
- Library creation and maintenance
- Create and release documentation for fabrication of PCBs
- Collaborate with internal teams and PCB vendors to continually improve design rules, constraints and design for test and manufacture guidelines
- Work closely with engineers from adjacent disciplines (mechanical, thermal, software, test engineering, supply chain, silicon design, etc.) to deliver tightly integrated, high-performance hardware
- Challenge assumptions, question requirements, learn from your mistakes, and approach problems with an open mind
Requirements
- Bachelor’s degree in electrical engineering, computer engineering, or physics
- 10+ years of industry experience designing circuits, electronic products, or hardware
- Ability to work extended hours or weekends as needed for mission critical deadlines
- Some travel may occasionally be required
- ITAR Requirements: 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.
Qualifications
- Master’s degree in electrical engineering, computer engineering, or similar engineering degree
- 2+ years of professional experience rapidly designing and delivering highly reliable products
- 2+ years of electronic product experience designing hardware from concept through production; strong emphasis on full life-cycle development of new hardware products and not small incremental updates to legacy hardware
- 2+ years of experience designing and implementing mixed-signal circuit boards from concept through production using processors, FPGAs, Ethernet, multi-GHz Serdes, DRAM interfaces (DDR4), I2C, SPI, operational amplifiers, analog to digital and digital to analog converters, and power supply components
- 2+ years of professional experience testing, troubleshooting, and debugging electronics
- Strong understanding of computers and programming languages (Python, C/C++)
- Demonstrated ability to work in a highly cross-functional role
- 2+ years working on aerospace systems
We should not include any boilerplate like EEO statement. Ensure no duplicate lines. Ensure we didn't include job title as heading. Good.
Check that we preserved all substantive info: The intro paragraph includes the description about SpaceX, Starmind, role. Did we lose any detail? The original intro includes: "SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. PRINCIPAL ELECTRICAL HARDWARE ENGINEER, AI SATELLITES (STARMIND) SpaceX is leveraging its experience deploying and operating the world’s largest satellite constellation to develop Starmind, a new constellation of satellites capturing solar energy in space to power low-cost, high-performance AI compute for Earth. Realizing this vision demands highly reliable, high performance electrical hardware ranging from power electronics, high speed digital systems, mixed signal designs, robust avionics, networking, and custom compute electronics. These systems must operate in the extreme environment of space while delivering the connectivity, control, power distribution, and processing needed for orbital AI inference. The Starmind team designs, builds, and operates the orbital compute fabric of the future. We develop nearly every key piece of technology in house – from the satellites’ flight computers and power systems to the fully custom compute electronics, memory, and networking that form the brain of our on-orbit data centers. As an engineer on the Starmind Payload Engineering team, you’ll have ownership over the entire life-cycle of the hardware that enables advanced on-orbit AI processing and data center workloads. Your work sits at the intersection of electrical, mechanical, thermal, and software engineering. The Payload team is responsible for the design of industry-leading compute electronics, memory, and networking in order to achieve required domain sizes and processing workloads."
We included all that. Good.
Responsibilities: we captured all bullet points. Check each:
- Rapidly develop high-reliability electronics for satellites and spacecraft. (yes)
- Drive system trades, requirements capture, component selection, analysis, schematic capture, PCB layout, prototyping, hardware bring-up, debugging, documentation, manufacturing, test, and on-orbit performance of complex electrical designs (yes)
- Get hands-on and support hardware through production, satellite integration, and flight (yes)
- Determine layer stackup, perform component package selection, component placement, routing feasibility studies, and signal routing of digital, analog, RF, and power conversion of PCBs (yes)
- Library creation and maintenance (yes)
- Create and release documentation for fabrication of PCBs (yes)
- Collaborate with internal teams and PCB vendors to continually improve design rules, constraints and design for test and manufacture guidelines (yes)
- Work closely with engineers from adjacent disciplines (mechanical, thermal, software, test engineering, supply chain, silicon design, etc.) to deliver tightly integrated, high-performance hardware (yes)
- Challenge assumptions, question requirements, learn from your mistakes, and approach problems with an open mind (yes)
Requirements: we included Bachelor's degree, 10+ years experience, ability to work extended
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove ITAR? ITAR is a requirement; it's substantive. Should we keep? It's a requirement about citizenship. It's part of Additional Requirements. So keep. We need to avoid repeating job title as heading. The title is "PRINCIPAL ELECTRICAL HARDWARE ENGINEER, AI SATELLITES (STARMIND)". We should not put that as heading. We need to decide sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine Basic Qualifications and Preferred Skills? The instruction: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. Likely: - About the role: introductory paragraph describing SpaceX, Starmind, role. - Responsibilities: the bullet list under "Responsibilities". - Requirements: maybe Basic Qualifications? Or could be "Requirements" for mandatory items (Basic Qualifications + Additional Requirements like ITAR, ability to work extended hours, travel). We'll include. - Qualifications: maybe Preferred Skills And Experience (preferred qualifications). Or could split: Qualifications for education, Skills for technical skills. But we have both Basic Qualifications and Preferred Skills And Experience. We could treat Basic Qualifications as "Requirements" and Preferred Skills And Experience as "Qualifications". Or we could put Basic Qualifications under "Requirements" and Preferred Skills under "Skills". However the instruction list includes both Qualifications and Skills sections. We need to decide mapping. We have: - Basic Qualifications: Bachelor’s degree, 10+ years experience. - Preferred Skills And Experience: Master’s degree, 2+ years rapid design, 2+ years electronic product experience, 2+ years mixed-signal circuit boards, testing/troubleshooting, understanding of computers and programming languages, ability to work cross-functional, 2+ years aerospace systems. - Additional Requirements: ability to work extended hours or weekends, some travel, ITAR requirements. Thus we could map: - Requirements: Basic Qualifications + Additional Requirements (mandatory). Could also include ITAR etc. - Qualifications: Preferred Skills And Experience (preferred qualifications). Or maybe Qualifications for education/degree, Skills for technical skills. But we have both degree and experience in Preferred Skills. Could split: Qualifications for education (Master's degree) and Skills for technical skills (mixed-signal, programming, etc). However the instruction says prefer a few substantive sections over many thin ones. So maybe combine Preferred Skills And Experience into a single "Qualifications" section (since they are qualifications/preferred). And maybe we don't need a separate "Skills" section if we already covered skills in Qualifications. But we have a separate "Skills" heading in the list; we could omit if no specific skills content beyond what's in Qualifications. However we have technical skills like mixed-signal, FPGAs, Ethernet, etc. Those could go under Skills. But we can also include them under Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. We'll include About the role, Responsibilities, Requirements, Qualifications. Skip Skills, Benefits, Pay, Schedule if not present. Thus output:
About the role
SpaceX was founded under the belief that a future where humanity is out exploring the stars is fundamentally more exciting than one where we are not. Today SpaceX is actively developing the technologies to make this possible, with the ultimate goal of enabling human life on Mars. PRINCIPAL ELECTRICAL HARDWARE ENGINEER, AI SATELLITES (STARMIND) SpaceX is leveraging its experience deploying and operating the world’s largest satellite constellation to develop Starmind, a new constellation of satellites capturing solar energy in space to power low-cost, high-performance AI compute for Earth. Realizing this vision demands highly reliable, high performance electrical hardware ranging from power electronics, high speed digital systems, mixed signal designs, robust avionics, networking, and custom compute electronics. These systems must operate in the extreme environment of space while delivering the connectivity, control, power distribution, and processing needed for orbital AI inference. The Starmind team designs, builds, and operates the orbital compute fabric of the future. We develop nearly every key piece of technology in house – from the satellites’ flight computers and power systems to the fully custom compute electronics, memory, and networking that form the brain of our on-orbit data centers. As an engineer on the Starmind Payload Engineering team, you’ll have ownership over the entire life-cycle of the hardware that enables advanced on-orbit AI processing and data center workloads. Your work sits at the intersection of electrical, mechanical, thermal, and software engineering. The Payload team is responsible for the design of industry-leading compute electronics, memory, and networking in order to achieve required domain sizes and processing workloads.
Responsibilities
- Rapidly develop high-reliability electronics for satellites and spacecraft.
- Drive system trades, requirements capture, component selection, analysis, schematic capture, PCB layout, prototyping, hardware bring-up, debugging, documentation, manufacturing, test, and on-orbit performance of complex electrical designs
- Get hands-on and support hardware through production, satellite integration, and flight
- Determine layer stackup, perform component package selection, component placement, routing feasibility studies, and signal routing of digital, analog, RF, and power conversion of PCBs
- Library creation and maintenance
- Create and release documentation for fabrication of PCBs
- Collaborate with internal teams and PCB vendors to continually improve design rules, constraints and design for test and manufacture guidelines
- Work closely with engineers from adjacent disciplines (mechanical, thermal, software, test engineering, supply chain, silicon design, etc.) to deliver tightly integrated, high-performance hardware
- Challenge assumptions, question requirements, learn from your mistakes, and approach problems with an open mind
Requirements
- Bachelor’s degree in electrical engineering, computer engineering, or physics
- 10+ years of industry experience designing circuits, electronic products, or hardware
- Ability to work extended hours or weekends as needed for mission critical deadlines
- Some travel may occasionally be required
- ITAR Requirements: 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.
Qualifications
- Master’s degree in electrical engineering, computer engineering, or similar engineering degree
- 2+ years of professional experience rapidly designing and delivering highly reliable products
- 2+ years of electronic product experience designing hardware from concept through production; strong emphasis on full life-cycle development of new hardware products and not small incremental updates to legacy hardware
- 2+ years of experience designing and implementing mixed-signal circuit boards from concept through production using processors, FPGAs, Ethernet, multi-GHz Serdes, DRAM interfaces (DDR4), I2C, SPI, operational amplifiers, analog to digital and digital to analog converters, and power supply components
- 2+ years of professional experience testing, troubleshooting, and debugging electronics
- Strong understanding of computers and programming languages (Python, C/C++)
- Demonstrated ability to work in a highly cross-functional role
- 2+ years working on aerospace systems