- Pick this if you already have some reps and want stronger, more role-relevant proof with measurable evidence.
- This level is usually the sweet spot for students who want something credible without taking on too much system complexity too early.
This matters because strong projects do not just fill space on a profile. They help you build depth in one or two strategic tracks that can later connect to research, internships, and hiring.
WHY THIS IDEA IS STRONG
Shows that you can connect hardware, control, and software in a messy real-world system.
WHAT TO BUILD
- Integrate sensors and actuators
- Create a software node graph or system diagram
- Log failures during integration
- Revise mounting, wiring, or control interfaces after testing
KEY SKILLS
ROS / ROS2sensor integrationsystems thinkingdebugging across boundaries
SUGGESTED MILESTONES
- Get the base platform moving reliably
- Integrate sensing and telemetry
- Document at least one integration failure and fix
- Capture a stable demo plus system architecture
EVIDENCE TO SHOW
- system diagrams
- integration logs
- debug videos
- revision history
HOW TO DOCUMENT THIS ON SYQNAL
Use these prompts when you write the STORY step in the guided project builder. They help keep the page factual, specific, and evidence-backed.
- What system capability were you trying to demonstrate?
- What packaging, compute, or power constraints shaped the robot?
- What integration trade-off was most painful?
- What logs or videos best prove the system became more reliable over time?
AI-ASSISTED BUILDING STANDARD
It is fine to use AI to help scope, scaffold, review, and debug this idea. But the final project should still reflect your own understanding, validation, trade-offs, and documentation. If you cannot explain the design or reproduce the build, the project is not ready yet.
