Robotics Society: Technical Officer

As technical officer, I'll aim to:

• Improve the website design (e.g. adding videos of robots in action) and regularly update it during the year
• Help out with organising and running any workshops and ensuring all attendees have a fun time 
• Construct a winning team for any competitions in a fair manner
• Organise fun, creative and challenging tasks for hackathons & contests
  
   

Here's a draft:

I'm standing for technical officer because I genuinely care about making robotics more accessible at UCL. When I first joined the society, I remember feeling a bit lost — there's so much to learn and it's hard to know where to start. I want to be the person that helps bridge that gap for newer members.

I've spent a lot of time tinkering with projects on my own, picking up skills the hard way through broken circuits and code that refused to compile at 2am. That experience taught me a lot, but it also showed me how much faster you learn when someone's willing to sit down and walk you through things. That's the kind of environment I want to build.

Practically, I want to make our workshops more hands-on and structured so people actually walk away having built something, not just watched a demo. I also want to improve how we document our projects — so knowledge doesn't just disappear when people graduate. And I'd love to push for more ambitious team projects where people across different skill levels can contribute meaningfully.

I'm not standing because it looks good on a CV. I'm standing because this society has given me a lot, and I want to put the work in to make it better for everyone

That comes in under 1500 characters. Feel free to tweak the details — for instance, you could swap  a specific project you've worked on, a particular workshop idea, or a real moment from your time in the society. Adding one or two personal specifics will make it feel even more like you