01 · Main format
Internship
Join the complete 2–3-month engineering cycle, work within a group and take ownership of an agreed area.
OpenAMRobot 2.0 · Internship & Collaboration
Welcome to the next stage of building OpenAMRobot 2.0.
Join a focused engineering cycle as an intern, project collaborator or open-source contributor. Work on a real ROS 2 platform, produce visible results and help prepare OpenAMRobot 2.0.
See the current platform
Control the robot from one interface.
Navigation, Blockly, missions, robot monitoring and system information from a unified browser interface. Explore the UI repository →
Why open source matters
From a startup to global infrastructure.
Hugging Face shows how an open technology community can create visible, verifiable work and build lasting value. Open source does not guarantee success - but it gives contributors the opportunity to help shape a project from its early foundation.
OpenAMRobot is already gaining traction. A successful Release 2.0 will make the project more complete, valuable, visible and easier to adopt.
Read NVIDIA’s announcement →
Ways to participate
Choose the format that fits you.
02 · Optional
Project collaboration
Deliver a defined technical work package with agreed interfaces, reviews, tests and documentation.
03 · Optional
Open-source contributor
Contribute through GitHub at your own pace while following the same engineering, documentation and review standards.
The internship is our primary format. Project collaboration and open-source contribution are optional alternatives. All formats follow one shared plan and integrate into the same release.
Important information
Currently unpaid. Potentially a real beginning.
These opportunities are currently unpaid. They are intended for people who see clear professional value in public portfolio work, ROS 2 experience, visible GitHub contributions and international engineering collaboration.
Successful participation can create a real opportunity to continue with the project, become a regular contributor and potentially join the team. This is not a promise of employment or paid cooperation.
If you doubt your motivation or availability, it is better not to start. Once you accept a work package, you are expected to drive it to an agreed, tested and documented result. If exceptional circumstances intervene, communicate early and prepare a responsible handover.
Work on a real platform
Built in public. Tested on hardware.
We work documentation-first: understand the current system, define interfaces and acceptance criteria, build, test, review and document.
We value ownership, focused communication, independent research and constructive technical disagreement.
The robot and workshop are located at MotionLab Berlin . Remote contributors work with documented interfaces, simulation and reproducible environments. Hardware results are validated in the lab.
OpenAMRobot in motion
Navigate. Align. Dock.
The current platform supports autonomous movement and automatic docking. Release 2.0 will strengthen integration, testing and release quality around these capabilities.
Engineering directions
Choose one primary direction.
01
Robotics and simulation
ROS 2 Jazzy, Gazebo, Nav2, SLAM, docking and integration tests.
02
Arm and device integration
URDF/xacro, MoveIt 2, ros2_control, drivers, APIs and manipulation.
03
CI/CD and release engineering
GitHub Actions, builds, linting, automated tests, containers and release artifacts.
04
UI, Blockly and voice commands
React, Flask, missions, structured command validation, controls and diagnostics.
05
Hardware and embedded systems
Controllers, power distribution, sensors, motors, wiring, PCB design and commissioning.
06
Documentation and developer experience
GitHub Pages, onboarding, tutorials, architecture and reproducible instructions.
From task to release
One engineering process.
A task is complete when it works, is tested, documented, reviewed and reproducible by another person.
01 · Understand
Investigate the current implementation and requirements.
02 · Plan
Define the architecture, interfaces, risks and acceptance
criteria.
03 · Build and test
Implement and validate in code, simulation and, where
applicable, on physical hardware.
04 · Document and review
Make the result reproducible and complete the pull-request
process.
05 · Integrate and release
Prepare the completed work as part of OpenAMRobot 2.0.
Timeline and location
A focused release cycle.
The main engineering cycle is planned for approximately two months, followed where necessary by up to one additional month for physical testing, integration, documentation and release preparation.
Botshare Ltd is legally registered in Cyprus. Formal internship documents and recommendation letters will be issued by this entity.
The physical OpenAMRobot platform and workshop are located at MotionLab Berlin .
Next step
Prepare your proposal.
Review the engineering plan and send a concise, technically specific response showing how you understand and would approach the selected work.
A clear and honest proposal is more valuable than a long, generic or AI-generated response.
Submit before the deadline 15.09.2026.
Your response should include:
- Your preferred participation format and primary technical direction.
- Your assessment of the work, principal risks, missing information and proposed improvements.
- Your implementation approach, deliverables, testing strategy and estimated timeline.
- The concrete result you would aim to deliver during your first two weeks.
- Relevant projects, repositories, demonstrations or technical documentation.
- Weekly hours, timezone, usual working hours and earliest start date.
- Availability for short meetings on Monday and Friday, with Saturday as an alternative.
- Whether you can participate for the full 2–3 months or prefer a smaller independent task.
- Whether you can work physically in the Berlin lab or participate only remotely.
- Your interest in coordinating a group and an example of independent problem-solving.
OpenAMRobot 2.0 · Internship & Collaboration
Welcome to the next stage of building OpenAMRobot 2.0.
Join a focused engineering cycle as an intern, project collaborator or open-source contributor. Work on a real ROS 2 platform, produce visible results and help prepare OpenAMRobot 2.0.
See the current platform
Control the robot from one interface.
Navigation, Blockly, missions, robot monitoring and system information from a unified browser interface. Explore the UI repository →
Why open source matters
From a startup to global infrastructure.
Hugging Face shows how an open technology community can create visible, verifiable work and build lasting value. Open source does not guarantee success - but it gives contributors the opportunity to help shape a project from its early foundation.
OpenAMRobot is already gaining traction. A successful Release 2.0 will make the project more complete, valuable, visible and easier to adopt.
Read NVIDIA’s announcement →
Ways to participate
Choose the format that fits you.
01 · Main format
Internship
Join the complete 2–3-month engineering cycle, work within a group and take ownership of an agreed area.
02 · Optional
Project collaboration
Deliver a defined technical work package with agreed interfaces, reviews, tests and documentation.
03 · Optional
Open-source contributor
Contribute through GitHub at your own pace while following the same engineering, documentation and review standards.
The internship is our primary format. Project collaboration and open-source contribution are optional alternatives. All formats follow one shared plan and integrate into the same release.
Important information
Currently unpaid. Potentially a real beginning.
These opportunities are currently unpaid. They are intended for people who see clear professional value in public portfolio work, ROS 2 experience, visible GitHub contributions and international engineering collaboration.
Successful participation can create a real opportunity to continue with the project, become a regular contributor and potentially join the team. This is not a promise of employment or paid cooperation.
If you doubt your motivation or availability, it is better not to start. Once you accept a work package, you are expected to drive it to an agreed, tested and documented result. If exceptional circumstances intervene, communicate early and prepare a responsible handover.
Work on a real platform
Built in public. Tested on hardware.
We work documentation-first: understand the current system, define interfaces and acceptance criteria, build, test, review and document.
We value ownership, focused communication, independent research and constructive technical disagreement.
The robot and workshop are located at MotionLab Berlin . Remote contributors work with documented interfaces, simulation and reproducible environments. Hardware results are validated in the lab.
OpenAMRobot in motion
Navigate. Align. Dock.
The current platform supports autonomous movement and automatic docking. Release 2.0 will strengthen integration, testing and release quality around these capabilities.
Engineering directions
Choose one primary direction.
01
Robotics and simulation
ROS 2 Jazzy, Gazebo, Nav2, SLAM, docking and integration tests.
02
Arm and device integration
URDF/xacro, MoveIt 2, ros2_control, drivers, APIs and manipulation.
03
CI/CD and release engineering
GitHub Actions, builds, linting, automated tests, containers and release artifacts.
04
UI, Blockly and voice commands
React, Flask, missions, structured command validation, controls and diagnostics.
05
Hardware and embedded systems
Controllers, power distribution, sensors, motors, wiring, PCB design and commissioning.
06
Documentation and developer experience
GitHub Pages, onboarding, tutorials, architecture and reproducible instructions.
From task to release
One engineering process.
A task is complete when it works, is tested, documented, reviewed and reproducible by another person.
01 · Understand
Investigate the current implementation and requirements.
02 · Plan
Define the architecture, interfaces, risks and acceptance
criteria.
03 · Build and test
Implement and validate in code, simulation and, where
applicable, on physical hardware.
04 · Document and review
Make the result reproducible and complete the pull-request
process.
05 · Integrate and release
Prepare the completed work as part of OpenAMRobot 2.0.
Timeline and location
A focused release cycle.
The main engineering cycle is planned for approximately two months, followed where necessary by up to one additional month for physical testing, integration, documentation and release preparation.
Botshare Ltd is legally registered in Cyprus. Formal internship documents and recommendation letters will be issued by this entity.
The physical OpenAMRobot platform and workshop are located at MotionLab Berlin .
Next step
Prepare your proposal.
Review the engineering plan and send a concise, technically specific response showing how you understand and would approach the selected work.
A clear and honest proposal is more valuable than a long, generic or AI-generated response.
Submit before the deadline 15.09.2026.
Your response should include:
- Your preferred participation format and primary technical direction.
- Your assessment of the work, principal risks, missing information and proposed improvements.
- Your implementation approach, deliverables, testing strategy and estimated timeline.
- The concrete result you would aim to deliver during your first two weeks.
- Relevant projects, repositories, demonstrations or technical documentation.
- Weekly hours, timezone, usual working hours and earliest start date.
- Availability for short meetings on Monday and Friday, with Saturday as an alternative.
- Whether you can participate for the full 2–3 months or prefer a smaller independent task.
- Whether you can work physically in the Berlin lab or participate only remotely.
- Your interest in coordinating a group and an example of independent problem-solving.