FTC Launchpad · Practice & judging
Practice questions
- Open each question.
- Guess out loud, then reveal.
- Your answer can differ if it’s still correct.
What is the difference between autonomous and tele-op?
Sample:
- Autonomous — pre-written code runs by itself
- Tele-op — driver + gamepad during the match
Name two reasons a team might use sensors.
Sample (any two):
- Stop at a set distance
- Line up on a target
- Detect a game piece
- Know how far the robot turned
- Avoid hitting something
What is a drivetrain?
Sample: The system of wheels and motors that moves the robot around the field.
What does “gear ratio” affect?
Sample:
- Tradeoff: speed vs torque
- More torque → often less speed (same motor)
Why do teams keep an engineering notebook or portfolio?
Sample:
- Show: tried → iterated → changed → why
- Learn + explain the robot to judges
What is Gracious Professionalism in one sentence?
Sample: Competing seriously while staying respectful, honest, and helpful to others.
What is one safety habit in the shop?
Sample (any one):
- Tie hair back
- Safety glasses when required
- Hands off moving parts
- Ask before a new tool
What is CAD used for on an FTC team?
Sample:
- 3D design before metal / plastic
- Check fit
- Share ideas with the team
What is special about mecanum wheels?
Sample: They have rollers at an angle so the robot can strafe sideways on a flat floor if the code and driving are set up for it.
If you don’t know an answer during tryouts, what can you say?
Sample: “I’m not sure yet—could you explain it?” or “I’d like to learn that—here’s what I think so far…”
Bonus: write 3 questions for your team:
- Schedule / meetings
- Expectations for new members
- How beginners learn
Good questions = mature.
Engineering portfolio
The engineering portfolio is a written document you submit before competitions. Judges read it before your interview — a strong portfolio wins awards and impresses alliance partners.
What goes in the portfolio
- Team introduction — members, roles, how you communicate, team culture.
- Design process — how you identified what the robot needs to do; what constraints you faced (time, parts, skills).
- Mechanism design — sketches, CAD screenshots, or photos of each major mechanism with a short explanation of why you chose that approach over alternatives.
- Iteration log — what didn't work, what you changed, and why. Judges value honest iteration over a "perfect robot" story.
- Software & autonomous strategy — brief overview of your programming approach and auto path choices.
- Outreach & community — demos, workshops, team events, partnerships with STEM programs.
- Lessons learned / next steps — what would you do differently? What's on the backlog?
Format tips
- Typical length: 15–25 pages (no official max, but be concise).
- Use photos and diagrams — judges skim; pictures explain faster than paragraphs.
- Label every photo: "Front intake, iteration 3 — added compliant wheels to reduce jams."
- Consistent fonts, colors, and headers make it look professional and easy to navigate.
- Export as PDF before the submission deadline.
When to write it
- Don't write it the night before — engineers log each week as they build.
- Assign a "documentation lead" who takes photos at every practice and drafts a short paragraph per session.
- Use a shared Google Doc or Notion so all members can contribute.
- Lock and format the final PDF at least 2 days before the submission deadline.
- Think Award is primarily based on your portfolio — document every design decision now, not at the end of the season.
- Inspire Award (best overall) requires a great portfolio plus a great interview — start both early.
Judging & presentation (quick refs)
Formats vary by event—adapt with your coach.
Display & slides
- Many formats work: poster board, PowerPoint (bring extension cords/batteries), talking + demo; you can combine.
- Optional display board: team name/number, photo, robot design, strategy, outreach, sponsors—helps pit judges and alliance partners.
- Slides: lots of pictures/diagrams; most explanation is spoken; clear, not empty or overwhelming; use as many slides as you need.
Formal interview
- Often ~5 min presentation + ~5 min Q&A; judges may stop you at time; whole team present; 2–3 judges.
- Tips: everyone speaks briefly, know your key points well, practice as a team, point at the robot when describing parts. The judges are there to learn about your work, not to catch you out.
Q&A and pit
- Q&A can cover design, outreach, team dynamics, what you learned—practice answers; delegate by expertise (leads handle the hardest questions).
- Pit: judges walk the pit; more visits can mean award consideration; have a “runner” to fetch the right teammate; short highlights welcome.