Robotics Research Internship, Humanoid Manipulation (Spring 2027) | PhD Internship
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. We need to preserve substantive info.
Let's parse the posting.
First paragraph: description of company, location Boston, R&D team, etc. That's about the role? Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have sections: "What You Will Get To Do" with bullet points (Advance Humanoid Manipulation Research..., Contribute to the Research Community..., Contribute to Robotics Foundation Model Development..., Collaborate Across Disciplines...). That's responsibilities.
Then "What You Have" lists qualifications: Current PhD student..., Research experience..., Strong foundation..., Proficiency..., Experience designing..., Curiosity..., Publications... That's qualifications/requirements.
Then "The Extras That Set You Apart": prior experience..., background..., hands-on..., familiarity..., publications..., interest... That's maybe "Skills" or "Preferred Qualifications". Could be "Skills". We'll treat as Skills.
Then "Why Join Field AI?" includes description of mission, team, location, etc. That could be "About the role" or maybe "About the company". We have already "About the role" maybe for company description. But we need to decide.
We also have "Equal Opportunity" etc which is boilerplate to remove.
We also have mention of location Boston, also headquarters Irvine. That could be part of About the role.
We need to avoid filler sections like Pay, Schedule, Benefits unless posting actually states them. The posting does not mention pay, benefits, schedule. So we should NOT include those headings.
Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe combine Requirements and Qualifications? The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "What You Have" which includes requirements and qualifications. Could split into Requirements (mandatory) and Qualifications (preferred). But we have also "The Extras That Set You Apart" which are preferred. So we could map:
- About the role: company description, mission, location, internship focus.
- Responsibilities: "What You Will Get To Do" bullet points.
- Requirements: mandatory qualifications from "What You Have" (PhD student, research experience, foundation, proficiency, experience designing experiments, curiosity, initiative, publications). Actually publications are listed there as mandatory? It says "Publications in leading robotics journals/conferences (ICRA, IROS, CORL, RA-L, T-RO, etc.)" under What You Have. That seems a requirement.
- Qualifications: maybe "The Extras That Set You Apart" as preferred qualifications.
- Skills: maybe we could also include technical skills like Python/C++, ROS, etc. But those are already in Requirements. Could combine.
But we need to avoid thin sections. Perhaps better to have About the role, Responsibilities, Requirements (including both mandatory and preferred), and Skills (maybe technical skills). However we have both Requirements and Qualifications headings available; we can use both if we have distinct content.
Let's extract content:
About the role:
- FieldAI transforming how robots interact with real world.
- Growing R&D team based in Boston, develop risk-aware, reliable, field-ready AI systems for robotics.
- Pragmatic approach beyond off-the-shelf, combining research with real-world deployment.
- Solutions deployed globally, improve model performance via rapid iteration driven by real field use.
- Offering Fall 2026 internship focused on humanoid manipulation for PhD students interested in advancing embodied intelligence on humanoids.
- As a research intern, work at intersection of robotics research and applied engineering, contributing to manipulation capabilities that support FieldAI’s autonomy and robot learning efforts while advancing field via academic research with goal of publishing a paper to leading journal or conference.
- Headquarters in Irvine, Southern California, teammates across US and worldwide.
- R&D organization growing, anchored in Boston, with collaboration across teams in Southern California and globally.
- Mission: tackling deploying robots in unstructured, previously unknown environments; Field Foundational Models advance perception, planning, localization, manipulation with emphasis on explainability and safety.
- Work alongside world-class team valuing creativity, resilience, bold thinking.
- Decade-long track record of real-world deployments, strong performance in DARPA challenges, experience from organizations such as DeepMind, NASA JPL, Boston Dynamics, NVIDIA, Amazon, Tesla Autopilot, Cruise, Zoox, Toyota Research Institute, SpaceX.
- Looking for people who push beyond conventional approaches, enjoy tackling tough ambiguous questions, bring interdisciplinary perspective.
- Success depends on exceptional AI researchers and engineers, strong software developers, product designers, field deployment experts, communicators who turn breakthroughs into real capability.
- Join us to shape future of embodied intelligence as part of fun, close-knit team building systems that work in real world.
That's a lot; we can condense but must preserve all substantive information, not invent or summarize away detail. However we must not create filler. We can keep as paragraphs.
Responsibilities: bullet list from "What You Will Get To Do":
- Advance Humanoid Manipulation Research: Design, implement, and evaluate manipulation strategies for humanoid robots across diverse tasks. Explore loco-manipulation problems that integrate perception, planning, and control. Work towards super-human dexterity, developing systems that outperform human teleoperation.
- Contribute to the Research Community: Work towards publishing a paper in a leading robotics conference/journal. Work closely with other researchers, both internal and external. Present your work at Field at robotic conferences (maybe "Present your work at Field at robotic conferences" seems typo; keep as is).
- Contribute to Robotics Foundation Model Development: Support data collection pipelines used to train robotics foundation models. Work with embodiment-agnostic representations to enable transfer across robot platforms. Collaborate with researchers to integrate manipulation data into scalable learning frameworks.
- Collaborate Across Disciplines: Work with teleoperators and field teams to refine interfaces and improve manipulation outcomes. Partner closely with researchers and engineers to align experiments with broader autonomy goals. Engage with mechanical and electrical engineers on hardware integration and system bring-up.
We need to preserve all details; we can keep as - each bullet maybe with sub-bullets? The instruction says use
- for any list of duties/requirements/benefits. So we can have top-level
with each responsibility as - . Inside each li we can have sentences; we could also embed further
for subpoints but not required. We'll keep as single li with sentences.
Requirements: from "What You Have":
- Current PhD student in Robotics, Computer Science, Mechanical Engineering, Electrical Engineering, AI/ML, or a closely related field
- Research experience in robotic manipulation, loco-manipulation, or related robotics domains
- Strong foundation in robot kinematics, dynamics, and control
- Proficiency in Python and/or C++, with experience using robotics or ML tooling
- Experience designing experiments and evaluating results on robotic systems (simulation or hardware)
- Curiosity, initiative, and a strong interest in embodied intelligence and real-world robotics
- Publications in leading robotics journals/conferences (ICRA, IROS, CORL, RA-L, T-RO, etc.)
We'll put each as - .
Qualifications: maybe "The Extras That Set You Apart":
- Prior experience working with humanoid robots or dexterous robotic hands
- Background in learning-based manipulation, including imitation learning or reinforcement learning
- Hands-on experience running experiments on real robot hardware
- Familiarity with ROS or ROS 2
- Publications, preprints, or open-source contributions in robotics or AI
- Interest in bridging cutting-edge research with practical, field-ready robotic systems
We'll put as
- .
Skills: maybe we could include technical skills like Python/C++, ROS, etc but those already in requirements. Could skip Skills section to avoid thin. But we have to use headings only when posting has real specific content. We have content for Skills? Not explicitly separate; but we could argue that the technical proficiencies are skills. However we already placed them under Requirements. Might be okay to omit Skills heading.
We must not include Benefits, Pay, Schedule.
Now we need to output only HTML fragment, no markdown fences.
We'll produce:
About the role
... paragraphs ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
We need to ensure we don't include any boilerplate like Equal Opportunity, etc.
Let's craft the About the role paragraph(s). We need to preserve all substantive information; we can split into multiple if needed but not required. We'll combine into maybe two paragraphs to avoid overly long but still preserve info.
We must not invent or summarize away detail. So we need to keep all details; we can keep them as sentences.
Let's draft:
FieldAI is transforming how robots interact with the real world. Our growing R&D team is based in Boston, where we develop risk-aware, reliable, field-ready AI systems that tackle the hardest problems in robotics and unlock the potential of embodied intelligence. We take a pragmatic approach that goes beyond off-the-shelf, purely data-driven methods or transformer-only architectures, combining cutting-edge research with real-world deployment. Our solutions are already deployed globally, and we continuously improve model performance through rapid iteration driven by real field use. We are offering a Fall 2026 internship focused on humanoid manipulation for PhD students interested in advancing embodied intelligence on humanoids. As a research intern, you will work at the intersection of robotics research and applied engineering, contributing to manipulation capabilities that directly support FieldAI’s autonomy and robot learning efforts while advancing the field of robotics through academic research with the goal of publishing a paper to a leading journal or conference. FieldAI is headquartered in Irvine, Southern California, with teammates across the US and around the world. Our R&D organization is growing and anchored in Boston, with close collaboration across our teams in Southern California and with colleagues around the US and globally. We are tackling one of robotics’ hardest problems: deploying robots in unstructured, previously unknown environments. Our Field Foundational Models™ advance perception, planning, localization, and manipulation with an emphasis on explainability and safety, so our systems can be trusted where it matters most. You will work alongside a world-class team that values creativity, resilience, and bold thinking. We bring a decade-long track record of real-world deployments, strong performance in DARPA challenges, and experience from organizations such as DeepMind, NASA JPL, Boston Dynamics, NVIDIA, Amazon, Tesla Autopilot, Cruise, Zoox, Toyota Research Institute, and SpaceX. We are looking for people who push beyond conventional approaches, enjoy tackling tough and ambiguous questions, and bring interdisciplinary perspective. Our success depends on exceptional AI researchers and engineers, as well as strong software developers, product designers, field deployment experts, and communicators who can turn breakthroughs into real capability. Join us to shape the future of embodied intelligence as part of a fun, close-knit team building systems that work in the real world.
That seems to capture all.
Now Responsibilities
with four - each containing the sentences.
We need to keep the exact phrasing? Not required but preserve substance.
Let's write each li:
- Advance Humanoid Manipulation Research: Design, implement, and evaluate manipulation strategies for humanoid robots across diverse tasks. Explore loco-manipulation problems that integrate perception, planning, and control. Work
- for any list of duties/requirements/benefits. So we can have top-level
- with each responsibility as
- . Inside each li we can have sentences; we could also embed further
- for subpoints but not required. We'll keep as single li with sentences.
Requirements: from "What You Have":
- Current PhD student in Robotics, Computer Science, Mechanical Engineering, Electrical Engineering, AI/ML, or a closely related field
- Research experience in robotic manipulation, loco-manipulation, or related robotics domains
- Strong foundation in robot kinematics, dynamics, and control
- Proficiency in Python and/or C++, with experience using robotics or ML tooling
- Experience designing experiments and evaluating results on robotic systems (simulation or hardware)
- Curiosity, initiative, and a strong interest in embodied intelligence and real-world robotics
- Publications in leading robotics journals/conferences (ICRA, IROS, CORL, RA-L, T-RO, etc.)
We'll put each as
- . Qualifications: maybe "The Extras That Set You Apart": - Prior experience working with humanoid robots or dexterous robotic hands - Background in learning-based manipulation, including imitation learning or reinforcement learning - Hands-on experience running experiments on real robot hardware - Familiarity with ROS or ROS 2 - Publications, preprints, or open-source contributions in robotics or AI - Interest in bridging cutting-edge research with practical, field-ready robotic systems We'll put as
- .
Skills: maybe we could include technical skills like Python/C++, ROS, etc but those already in requirements. Could skip Skills section to avoid thin. But we have to use headings only when posting has real specific content. We have content for Skills? Not explicitly separate; but we could argue that the technical proficiencies are skills. However we already placed them under Requirements. Might be okay to omit Skills heading.
We must not include Benefits, Pay, Schedule.
Now we need to output only HTML fragment, no markdown fences.
We'll produce:
About the role
... paragraphs ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
if needed but not required. We'll combine into maybe two paragraphs to avoid overly long but still preserve info. We must not invent or summarize away detail. So we need to keep all details; we can keep them as sentences. Let's draft: FieldAI is transforming how robots interact with the real world. Our growing R&D team is based in Boston, where we develop risk-aware, reliable, field-ready AI systems that tackle the hardest problems in robotics and unlock the potential of embodied intelligence. We take a pragmatic approach that goes beyond off-the-shelf, purely data-driven methods or transformer-only architectures, combining cutting-edge research with real-world deployment. Our solutions are already deployed globally, and we continuously improve model performance through rapid iteration driven by real field use. We are offering a Fall 2026 internship focused on humanoid manipulation for PhD students interested in advancing embodied intelligence on humanoids. As a research intern, you will work at the intersection of robotics research and applied engineering, contributing to manipulation capabilities that directly support FieldAI’s autonomy and robot learning efforts while advancing the field of robotics through academic research with the goal of publishing a paper to a leading journal or conference. FieldAI is headquartered in Irvine, Southern California, with teammates across the US and around the world. Our R&D organization is growing and anchored in Boston, with close collaboration across our teams in Southern California and with colleagues around the US and globally. We are tackling one of robotics’ hardest problems: deploying robots in unstructured, previously unknown environments. Our Field Foundational Models™ advance perception, planning, localization, and manipulation with an emphasis on explainability and safety, so our systems can be trusted where it matters most. You will work alongside a world-class team that values creativity, resilience, and bold thinking. We bring a decade-long track record of real-world deployments, strong performance in DARPA challenges, and experience from organizations such as DeepMind, NASA JPL, Boston Dynamics, NVIDIA, Amazon, Tesla Autopilot, Cruise, Zoox, Toyota Research Institute, and SpaceX. We are looking for people who push beyond conventional approaches, enjoy tackling tough and ambiguous questions, and bring interdisciplinary perspective. Our success depends on exceptional AI researchers and engineers, as well as strong software developers, product designers, field deployment experts, and communicators who can turn breakthroughs into real capability. Join us to shape the future of embodied intelligence as part of a fun, close-knit team building systems that work in the real world. That seems to capture all. Now Responsibilities
- with four
- each containing the sentences. We need to keep the exact phrasing? Not required but preserve substance. Let's write each li:
- Advance Humanoid Manipulation Research: Design, implement, and evaluate manipulation strategies for humanoid robots across diverse tasks. Explore loco-manipulation problems that integrate perception, planning, and control. Work
- . Inside each li we can have sentences; we could also embed further