Robotics Engineer (New Grad): Government Projects
GrayMatter Robotics · Los Angeles Metropolitan Area · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse.
The posting includes:
- Summary (intro) about company and role. Could be "About the role" section.
- Responsibilities: bullet list.
- Export Control Requirements: that's a requirement (citizenship). Could be part of Requirements.
- Minimum Qualifications: list.
- Preferred Qualifications: list.
- Benefits: mention comprehensive benefits and perks: medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, discretionary fund for enhancing productivity and so much more! Also mention compensation may include base salary range, bonus/commission, equity. However they say "Depending on the position and if listed, compensation may include the base salary range, bonus or commission, and equity." No specific numbers given. So we cannot create Pay section because no specific salary range. The phrase "The range listed on job postings reflect the minimum and maximum new hire salary across levels in Los Angeles, CA." But they didn't actually list a range. So we cannot include Pay.
- Schedule: not mentioned.
- Benefits: we have specific benefits listed: medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, discretionary fund for enhancing productivity. So we can include Benefits section.
- Skills: maybe we can extract from qualifications: hands-on experience with physical robotic or mechanical systems, scripting Python, documentation, analytical skills, etc. Could be a Skills section. But we already have Minimum Qualifications and Preferred Qualifications. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples; we can choose which sections to include. We need to avoid thin sections. We could combine Requirements and Qualifications into one "Requirements" section that includes both minimum and preferred? Or separate "Minimum Qualifications" and "Preferred Qualifications"? The examples include "Qualifications". Probably we should have a "Qualifications" section that includes both minimum and preferred. But we also have "Skills" maybe separate. However we can decide to have sections: About the role, Responsibilities, Qualifications, Benefits. That's substantive.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, export control, benefits, etc.
We must not include boilerplate like EEO, accommodations, etc. Remove those.
We must not include duplicated lines.
We need to output only HTML fragment.
Let's extract content.
About the role: The summary paragraphs before responsibilities: "GrayMatter Robotics is a well-capitalized Physical AI company headquartered in Los Angeles, building Factory SuperIntelligence (FSI) through systems that learn, adapt, and develop genuine process intelligence across every part they touch. Our robots take on the tedious, hazardous, and ergonomically demanding work that has kept manufacturing dependent on a shrinking skilled workforce, delivering superhuman performance. Robotics has a demo problem. GMR doesn't. Our systems are in active production today, adapting autonomously to real geometries, real materials, and real process variation without reprogramming. We deliver our system through a Robots-as-a-Service (RaaS) model that converts capital expenditure into an operating subscription, making Physical AI accessible to the manufacturers who need it most. We hire people who want to solve hard physical problems at an industrial scale. As a Robotics Engineer (New Grad): Government Projects, you'll work at the boundary of software and hardware: helping stand up new robotic manufacturing cells, configuring GMR-AI to generate the toolpaths that make a new application work, and getting hands-on with the tooling and controls of the system."
We can put that as About the role.
Responsibilities: bullet list from "Support proof-of-concept work..." through "Travel to project sites as needed...". Let's capture each bullet.
List:
- Support proof-of-concept work that demonstrates what GMR's robotic systems can do for a new application or customer
- Learn the manufacturing processes, requirements, and constraints for each project, and help gather the data (measurements, CAD, documentation) that shapes a new robotic cell
- Assist in robotic manufacturing cell design, working alongside software and mechatronics engineers to reason about reachability, cycle time, and efficiency
- Help design, build, and test custom end-of-arm tooling and work-holding fixtures, from early concept through validation
- Configure GMR-AI to generate toolpaths and trajectories for new applications, with guidance from senior engineers
- Help test and prototype new inspection sensors and tools, including hands-on evaluation of emerging vendor technology
- Install, troubleshoot, and maintain controls components: sensors, PCs, and third-party device controllers
- Contribute to new process recipes as GMR's systems take on different materials and geometries
- Partner with GMR software engineers to prototype new ideas and methods, building toward taking on more of this independently
- Rotate across process engineering, mechanical/tooling, and software workstreams early on, to build the same full-stack fluency senior engineers on this team rely on
- Travel to project sites as needed to support installs, proof-of-concepts, or on-site troubleshooting
Export Control Requirements: This is a requirement: must be US citizen/national, lawful permanent resident, refugee, or asylee. We'll include under Qualifications or Requirements.
Minimum Qualifications:
- Bachelor's degree (or in-progress remotely/completed Master's) in Robotics, Mechanical Engineering, Systems Engineering, Computer Science, or a related engineering discipline
- Hands-on experience with physical robotic or mechanical systems through coursework, internships, co-ops, capstone projects, or research (0-2 years total experience expected)
- Demonstrated ability to follow and execute a structured experiment or process with high attention to detail
- Working familiarity with basic scripting and data analysis (Python or similar)
- Strong written communication skills; comfortable documenting technical findings and procedures clearly
- Excellent analytical skills and genuine curiosity to understand how and why a process works
Preferred Qualifications:
- Exposure to Design of Experiments (DOE) methodology or statistical process analysis
- Coursework or project experience with ROS/ROS2
- Experience with point cloud, force, or other 3D sensor data
- Experience with 6DOF robot arms
- CAD experience (SolidWorks or similar) or hands-on manufacturing/shop experience
Benefits: list:
- medical, dental, vision
- unlimited PTO
- 401(k) plan + employer match
- regular offsite events
- discretionary fund for enhancing productivity
- (and so much more) but we keep listed.
Also mention compensation may include base salary range, bonus/commission, equity but no specifics; we should not create Pay section.
We should not include EEO etc.
Now produce HTML.
Structure:
for section headings; we could have nested
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples; we can choose which sections to include. We need to avoid thin sections. We could combine Requirements and Qualifications into one "Requirements" section that includes both minimum and preferred? Or separate "Minimum Qualifications" and "Preferred Qualifications"? The examples include "Qualifications". Probably we should have a "Qualifications" section that includes both minimum and preferred. But we also have "Skills" maybe separate. However we can decide to have sections: About the role, Responsibilities, Qualifications, Benefits. That's substantive.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, export control, benefits, etc.
We must not include boilerplate like EEO, accommodations, etc. Remove those.
We must not include duplicated lines.
We need to output only HTML fragment.
Let's extract content.
About the role: The summary paragraphs before responsibilities: "GrayMatter Robotics is a well-capitalized Physical AI company headquartered in Los Angeles, building Factory SuperIntelligence (FSI) through systems that learn, adapt, and develop genuine process intelligence across every part they touch. Our robots take on the tedious, hazardous, and ergonomically demanding work that has kept manufacturing dependent on a shrinking skilled workforce, delivering superhuman performance. Robotics has a demo problem. GMR doesn't. Our systems are in active production today, adapting autonomously to real geometries, real materials, and real process variation without reprogramming. We deliver our system through a Robots-as-a-Service (RaaS) model that converts capital expenditure into an operating subscription, making Physical AI accessible to the manufacturers who need it most. We hire people who want to solve hard physical problems at an industrial scale. As a Robotics Engineer (New Grad): Government Projects, you'll work at the boundary of software and hardware: helping stand up new robotic manufacturing cells, configuring GMR-AI to generate the toolpaths that make a new application work, and getting hands-on with the tooling and controls of the system."
We can put that as About the role.
Responsibilities: bullet list from "Support proof-of-concept work..." through "Travel to project sites as needed...". Let's capture each bullet.
List:
- Support proof-of-concept work that demonstrates what GMR's robotic systems can do for a new application or customer
- Learn the manufacturing processes, requirements, and constraints for each project, and help gather the data (measurements, CAD, documentation) that shapes a new robotic cell
- Assist in robotic manufacturing cell design, working alongside software and mechatronics engineers to reason about reachability, cycle time, and efficiency
- Help design, build, and test custom end-of-arm tooling and work-holding fixtures, from early concept through validation
- Configure GMR-AI to generate toolpaths and trajectories for new applications, with guidance from senior engineers
- Help test and prototype new inspection sensors and tools, including hands-on evaluation of emerging vendor technology
- Install, troubleshoot, and maintain controls components: sensors, PCs, and third-party device controllers
- Contribute to new process recipes as GMR's systems take on different materials and geometries
- Partner with GMR software engineers to prototype new ideas and methods, building toward taking on more of this independently
- Rotate across process engineering, mechanical/tooling, and software workstreams early on, to build the same full-stack fluency senior engineers on this team rely on
- Travel to project sites as needed to support installs, proof-of-concepts, or on-site troubleshooting
Export Control Requirements: This is a requirement: must be US citizen/national, lawful permanent resident, refugee, or asylee. We'll include under Qualifications or Requirements.
Minimum Qualifications:
- Bachelor's degree (or in-progress remotely/completed Master's) in Robotics, Mechanical Engineering, Systems Engineering, Computer Science, or a related engineering discipline
- Hands-on experience with physical robotic or mechanical systems through coursework, internships, co-ops, capstone projects, or research (0-2 years total experience expected)
- Demonstrated ability to follow and execute a structured experiment or process with high attention to detail
- Working familiarity with basic scripting and data analysis (Python or similar)
- Strong written communication skills; comfortable documenting technical findings and procedures clearly
- Excellent analytical skills and genuine curiosity to understand how and why a process works
Preferred Qualifications:
- Exposure to Design of Experiments (DOE) methodology or statistical process analysis
- Coursework or project experience with ROS/ROS2
- Experience with point cloud, force, or other 3D sensor data
- Experience with 6DOF robot arms
- CAD experience (SolidWorks or similar) or hands-on manufacturing/shop experience
Benefits: list:
- medical, dental, vision
- unlimited PTO
- 401(k) plan + employer match
- regular offsite events
- discretionary fund for enhancing productivity
- (and so much more) but we keep listed.
Also mention compensation may include base salary range, bonus/commission, equity but no specifics; we should not create Pay section.
We should not include EEO etc.
Now produce HTML.
Structure:
About the role
... (the summary paragraph(s) )
Responsibilities
- ... each
Qualifications
We could split into Minimum and Preferred but maybe combine under Qualifications with subheadings? The instruction only says use for section headings; we could have nested ? Not specified. Safer to have one Qualifications section and include both minimum and preferred as lists, maybe with headings inside like Minimum Qualifications etc. But that might be considered adding extra headings not allowed? Not prohibited. We can just list all qualifications in one list, but we need to preserve distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we combine minimum and preferred into a single list, we lose the distinction between minimum and preferred. That's summarizing away detail. So we should keep them separate. We could have two subsections: maybe Minimum Qualifications
and Preferred Qualifications
. The instruction only mentions using for section headings, but doesn't forbid other headings. However to be safe, we could keep them as sections: Minimum Qualifications and Preferred Qualifications. That would be more sections but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." Having both Minimum and Preferred may be okay; they are substantive. Could also combine them under Qualifications with two headings. I think using is acceptable as it's not prohibited. But to be safe, we can use for each: Minimum Qualifications and Preferred Qualifications. That yields sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits. That's 5 sections, each substantive.
We must not create Pay or Schedule.
Now craft HTML.
Need to ensure we don't include any boilerplate like "We celebrate diversity..." etc. Remove EEO paragraph.
Also remove "Depending on the position and if listed, compensation may include the base salary range, bonus or commission, and equity." That's not specific; we can omit because it's not concrete benefit? It's about compensation but vague. Since we are not making Pay section, we can omit that sentence. Also remove "We also provide comprehensive benefits and perks which include but are not limited to medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, a discretionary fund for enhancing productivity and so much more!" We already captured benefits; we can keep that sentence as part of Benefits but we need to preserve all substantive information. The sentence includes "and so much more!" which is vague but still part of benefits description. We can include it as part of benefits description.
Thus Benefits section:
Minimum Qualifications
andPreferred Qualifications
. The instruction only mentions using for section headings, but doesn't forbid other headings. However to be safe, we could keep them as sections: Minimum Qualifications and Preferred Qualifications. That would be more sections but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." Having both Minimum and Preferred may be okay; they are substantive. Could also combine them under Qualifications with two headings. I think using is acceptable as it's not prohibited. But to be safe, we can use for each: Minimum Qualifications and Preferred Qualifications. That yields sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits. That's 5 sections, each substantive.
We must not create Pay or Schedule.
Now craft HTML.
Need to ensure we don't include any boilerplate like "We celebrate diversity..." etc. Remove EEO paragraph.
Also remove "Depending on the position and if listed, compensation may include the base salary range, bonus or commission, and equity." That's not specific; we can omit because it's not concrete benefit? It's about compensation but vague. Since we are not making Pay section, we can omit that sentence. Also remove "We also provide comprehensive benefits and perks which include but are not limited to medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, a discretionary fund for enhancing productivity and so much more!" We already captured benefits; we can keep that sentence as part of Benefits but we need to preserve all substantive information. The sentence includes "and so much more!" which is vague but still part of benefits description. We can include it as part of benefits description.
Thus Benefits section:
headings. I think using is acceptable as it's not prohibited. But to be safe, we can use for each: Minimum Qualifications and Preferred Qualifications. That yields sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits. That's 5 sections, each substantive.
We must not create Pay or Schedule.
Now craft HTML.
Need to ensure we don't include any boilerplate like "We celebrate diversity..." etc. Remove EEO paragraph.
Also remove "Depending on the position and if listed, compensation may include the base salary range, bonus or commission, and equity." That's not specific; we can omit because it's not concrete benefit? It's about compensation but vague. Since we are not making Pay section, we can omit that sentence. Also remove "We also provide comprehensive benefits and perks which include but are not limited to medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, a discretionary fund for enhancing productivity and so much more!" We already captured benefits; we can keep that sentence as part of Benefits but we need to preserve all substantive information. The sentence includes "and so much more!" which is vague but still part of benefits description. We can include it as part of benefits description.
Thus Benefits section:
for each: Minimum Qualifications and Preferred Qualifications. That yields sections: About the role, Responsibilities, Minimum Qualifications, Preferred Qualifications, Benefits. That's 5 sections, each substantive. We must not create Pay or Schedule. Now craft HTML. Need to ensure we don't include any boilerplate like "We celebrate diversity..." etc. Remove EEO paragraph. Also remove "Depending on the position and if listed, compensation may include the base salary range, bonus or commission, and equity." That's not specific; we can omit because it's not concrete benefit? It's about compensation but vague. Since we are not making Pay section, we can omit that sentence. Also remove "We also provide comprehensive benefits and perks which include but are not limited to medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, a discretionary fund for enhancing productivity and so much more!" We already captured benefits; we can keep that sentence as part of Benefits but we need to preserve all substantive information. The sentence includes "and so much more!" which is vague but still part of benefits description. We can include it as part of benefits description. Thus Benefits section:
We provide comprehensive benefits and perks which include but are not limited to medical, dental, vision, unlimited PTO, 401(k) plan + employer match, regular offsite events, a discretionary fund for enhancing productivity and so much more!
Now ensure we didn't miss any substantive info: The Export Control Requirements must be included. Where to place? Could be under Minimum Qualifications as a bullet? It's a requirement separate from qualifications. Could be its own section "Requirements". But we already have Minimum Qualifications and Preferred Qualifications. Perhaps better to have a section "Requirements" that includes Export Control plus Minimum Qualifications? But then we lose Preferred. Could have Requirements (Export Control) and Qualifications (minimum+preferred). Let's think. The instruction examples include "Requirements, Qualifications". So we can have both. Requirements could be export control. Qualifications could be minimum and preferred. That seems logical. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to include Export Control under Requirements as a paragraph or list. Let's craft:Requirements
In order to comply with the export regulations of the United States Government, applicants must fall under one of the following categories:
- U.S. citizen or national
- U.S. lawful permanent resident (current green card holder)
- Refugee under 8 U.S.C. 1157
- Asylee under 8 U.S.C. 1158
Minimum Qualifications
andPreferred Qualifications
inside the Qualifications section. Or we could make separate sections Minimum Qualifications and Preferred Qualifications. Since we already have Requirements, we could have Qualifications with subheadings. I'll do that. Thus:Qualifications
Minimum Qualifications
- Bachelor's degree (or in-progress remotely/completed Master's) in Robotics, Mechanical Engineering, Systems Engineering, Computer Science, or