Non-technical
The half of FTC that judges actually score: the engineering portfolio, outreach, sponsors, and how the team explains itself in a ten-minute interview. Frequently the difference between a good robot and a winning team.
FTC #38345 · Craiova, România
A FIRST Tech Challenge team in Craiova. We design, build, code and compete with a real robot every season — and we hand screwdrivers to people who have never held one.
01 — Who we are
Rookie Raccoons is a FIRST Tech Challenge team in Craiova. Every September we get the same game, the same rulebook and the same deadline as every other team on the planet, and a few months later we turn up at a qualifier with a robot we drew, cut, wired and programmed ourselves.
What's unusual is the front door. Most of us joined knowing nothing — the first weeks are tools, safety, and somebody standing next to you saying "no, the other way round". Nobody gets benched for being new. The bracket a rookie makes in October is the bracket that goes to the competition in December, and it either holds or it doesn't.
We are not a class and there is no exam. It's a room, a deadline, a budget that's always slightly too small, and a group of people who would rather be in there than anywhere else after school.
We share a city, a workshop and a raccoon with Soft Hoarders #12560 — the team our founders came out of. We run our own season, our own build and our own robot.
Colegiul Național „Frații Buzești", Craiova. Sessions run through the school year.
02 — What you'd do
Everyone starts with the same two weeks of basics, then drifts toward whichever part of the team they can't stop thinking about. Changing your mind in November is completely normal — most of us have.
The half of FTC that judges actually score: the engineering portfolio, outreach, sponsors, and how the team explains itself in a ten-minute interview. Frequently the difference between a good robot and a winning team.
Drawing the part before anyone cuts metal. You model in CAD, watch it print overnight, then find out in the morning whether it fits — and iterate until it does. Half the parts on our robot started here.
Cutting, drilling, tapping, assembling. You learn the workshop properly — hand tools first, then power tools, then the parts of the robot that have to survive a match without falling apart.
Java, on a robot that actually moves. Start with making a motor spin on command and work up to autonomous routines that score without a driver touching anything.
Some members later move across to Soft Hoarders #12560, some stay and lead here, some do both. All three are a great outcome.
03 — The season
An FTC season has a shape. Here's ours, so you know what you're signing up for before you sign up for it.
The game drops worldwide on one day and everybody reads the same rulebook at the same time. Two weeks of arguing at a whiteboard, sketching, and printing things we fully intend to throw away.
A month of cutting, drilling and re-drilling. Chassis, subsystems, wiring. This is where rookies stop asking permission to use the drill.
Autonomous routines, driver practice, and finding out what falls off — on our own floor, rather than in front of a referee.
Qualifier weekends. Matches, judging interviews, frantic pit repairs between rounds, and the entire team crowded around one field.
The half of the year nobody photographs. Teaching new people, rebuilding what annoyed us, outreach, and trying ideas that were too risky to attempt in December.
04 — Milestones
We're early. This list is short on purpose and gets updated when something actually happens — not padded to look bigger.
First members, first workshop sessions, first tools handed out.
A complete competition robot, built start to finish by this roster.
Our first official FTC event as a team — matches and judging.
Running a workshop for other students instead of attending one.
05 — Straight answers
Usually whispered to whoever seems least intimidating. Asking here saves you the trouble.
No. That's the whole premise. People arrive having never written a line of Java, and the first sessions exist precisely to fix that. If you already code, you'll just get bored slower.
Less than you think. Most of a season is measuring twice, noticing that a bracket is 2mm off, and deciding what to try next. Plenty of the job is patience and stubbornness rather than mathematics.
Yes, and people do. It's a different experience — you'll walk into a half-built robot rather than a whiteboard — but there is always something that needs doing, and mid-season is when we most need extra hands.
No. The workshop's tools are the team's tools. Bring a laptop if you have one and want to write code on something familiar, but nobody is turned away for not owning one.
Then you leave, having lost an afternoon and learned to use a drill. Come to one session before deciding anything — that's what the invitation is for.
It swings with the season — the weeks before a qualifier ask a lot more than March does. Rather than quote you a number we'd have to keep correcting, ask us and we'll tell you what this term genuinely looks like.
06 — The roster
Students from Craiova who mostly started this year.
07 — Join
No application, no test, no robotics background. Write to us and come look at what we're building — bring a parent if you'd like, they usually have questions too.