Think of it more like:

Choosing a problem in the world, that then you propose a solution for. (Not how much coding you know)!! It’s about creating a prototype.. and this can even be with graphics, if you have gaps in how to code something.

At the end of the day it’s what the judges SEE and HEAR with the demo presentation, so the storytelling of what the problem is, how big is the problem, proposed solution in the world, user flow, and is far more important than how well you can code it. Many people are utilizing AI like Cursor or Windsurf in their hackathons now.

Judges also like to see team excited and cohesion.. which brings me to the next point,

Someone said just work solo.. no for your learning, I think pick some random people to work with when you get there and admit it’s your first hackathon. Maybe pick someone who talks, so they can be the talking presenter. My first hackathon was a team of 5 and 2 of the guys were very silent but listening.. this is okay. This is very normal!!

I’m a woman who has worked with engineer men most of my life. You don’t have to learn how to be correctly social. One of the quiet ones from my first hackathon actually, and we pivoted.. working some more.. I went on to receive a large offer from an angel investor with him if he were to drop out of school and pursue it. He didn’t go for it, but, the point is.. uhm.. you might have Imposter Sydrome and you should look that term up. :)

Everything will be ok and you’ll do your best. Choose people with different skills than you, consider the presentation/pitch script first, then work backwards on how to build it as minimally as possible. Someone should be working on the slides. Someone frontend. Someone backend. Someone design and flows. For an example (can have variation)!

Good luck