Call For Proposals: Hackaday Superconference

Why the Hackaday Superconference Call for Proposals Matters

The Hackaday Superconference Call for Proposals is not your average “please submit a 300-word abstract and wait politely by your inbox” kind of conference announcement. It is more like a beacon flashing across the maker universe: hardware hackers, embedded developers, circuit whisperers, robot builders, firmware tinkerers, open-source engineers, and delightfully stubborn people with solder burns on their fingertipsthis is your moment.

Hackaday Superconference, often called Supercon, has built a reputation as one of the most beloved gatherings for the hardware hacking community. It is part technical conference, part hacker camp, part badge-hacking festival, and part “wait, did someone just turn that conference badge into a musical instrument?” The event brings together people who do not simply talk about technology. They build it, break it, repair it, improve it, document it, and then enthusiastically explain why version three will definitely not catch fire.

A call for proposals, or CFP, is the door through which many of the best talks and workshops enter the event. Instead of programming a conference from the top down, Hackaday invites the community to pitch ideas. Those ideas may become long-form technical talks, shorter presentations, hands-on workshops, demos, or experience-driven sessions about the messy and fascinating process of making hardware behave.

What Is Hackaday Superconference?

Hackaday Superconference is a three-day gathering centered on hardware, electronics, engineering, open-source projects, and the maker mindset. Recent editions have taken place in Pasadena, California, and have featured talks, workshops, badge hacking, demos, competitions, and informal conversations that are often as valuable as the official program.

Unlike huge trade shows where attendees may spend half the day looking for Ballroom 48B while carrying a tote bag full of brochures, Supercon is known for being more intimate. That smaller scale is part of its magic. People can meet speakers, ask questions, compare strange circuit decisions, and find themselves deep in a hallway conversation about FPGAs, LoRa radios, PCB art, retrocomputing, mechanical keyboards, robotics, or why debugging I2C at 2 a.m. builds character.

The event also has a legendary relationship with electronic conference badges. At many conferences, a badge is just a name tag. At Supercon, the badge is often a fully hackable hardware platform. Attendees explore its firmware, attach Simple Add-Ons, write games, modify graphics, build utilities, and occasionally create things that make everyone nearby ask, “How did you even think of that?”

The Community Is the Main Feature

The most important part of Supercon is not the stage, the badge, or even the soldering iron. It is the community. Hackaday’s CFP announcements consistently emphasize that Supercon is about bringing together the people who make the Hackaday world interesting: curious builders with big ideas, small ideas, weird ideas, and projects that began as “this should only take a weekend” before consuming six months and three workbenches.

What the Call for Proposals Usually Seeks

The Hackaday Superconference Call for Proposals typically invites submissions for talks and workshops. Recent calls have welcomed both longer and shorter talks, and they have encouraged submissions from first-time presenters as well as established names in the Hackaday community.

That is good news if you have never spoken at a technical conference before. Supercon is not only looking for polished corporate keynotes delivered by people with laser pointers and suspiciously perfect slide decks. It is also interested in builders who can share what they learned from a real project, including the failures, surprises, redesigns, bodges, and late-night victories.

Strong Proposal Topics

A strong Supercon proposal usually has one or more of these ingredients:

• A real build: A device, tool, robot, instrument, badge add-on, sensor system, wearable, art project, or hardware platform that actually exists.
• A technical lesson: Something the audience can learn and apply, such as debugging methods, design trade-offs, firmware patterns, manufacturing lessons, or testing strategies.
• A story: A clear beginning, middle, and end. The best talks often explain what problem you faced, what went wrong, what changed, and what finally worked.
• Community value: Open-source files, documentation, reusable ideas, or lessons that help other builders avoid your most educational mistakes.
• Originality: Supercon loves cleverness. If your project makes people grin and then immediately ask technical questions, you are on the right track.

Talks, Workshops, and the Difference Between Them

Before submitting to any conference CFP, it helps to understand the format. At Hackaday Superconference, a talk and a workshop are not the same animal. They may both be friendly, but one wants slides and the other wants parts bins.

Talk Proposals

A talk is usually a presentation. It may be technical, narrative, educational, funny, inspiring, or all of the above. A great talk proposal explains what the audience will learn, why the topic matters, and why you are the right person to present it. For example, “I built a low-cost environmental sensor network” is fine. But “I built a low-cost environmental sensor network, discovered why outdoor enclosures are tiny greenhouses of doom, redesigned the power system twice, and learned how to keep data flowing for six months” is much stronger.

Supercon audiences appreciate honesty. If your project failed before it worked, say so. If your clever idea was defeated by thermal drift, antenna placement, supply chain drama, or a connector installed upside down, that may be the best part of the story. Hardware people do not gather because everything works perfectly. They gather because it rarely does, and solving that puzzle is half the fun.

Workshop Proposals

A workshop is more hands-on. It should teach attendees how to do something, build something, test something, or understand a specific tool or technique. Good workshop proposals are practical and realistic. They should answer basic questions: What will participants make or learn? What materials are required? How much experience do they need? Can the activity fit into the available time? What could go wrong, and how will you keep the room from turning into a polite panic?

For hardware workshops, logistics matter. Parts must be available. Tools must be safe and appropriate. Instructions should be clear. Backup plans are essential because the universe enjoys watching live demos sweat. If your workshop depends on Wi-Fi, drivers, cloud accounts, rare components, or everyone bringing the exact same laptop configuration, simplify it before the demo gods notice.

How to Write a Strong Hackaday Superconference Proposal

A successful Hackaday Superconference proposal should be specific, useful, and memorable. The review team needs to understand the topic quickly, but they also need to feel why it belongs at Supercon.

Start With a Clear Title

Your title should tell people what the session is about without requiring a decoder ring. “An FPGA-Based Retro Display Pipeline for Weird Old Screens” is better than “Pixels Reimagined.” Creative is good. Mysterious is risky. The audience should know whether they are getting firmware, mechanical design, RF, robotics, art, manufacturing, repair, security research, or a tale of heroic debugging.

Explain the Takeaway

The strongest proposals answer this question: What will attendees know after this session that they did not know before? Maybe they will learn how to design a badge add-on, choose components for low-power sensing, avoid common PCB layout mistakes, revive vintage hardware, use a microcontroller in an unusual way, or document a project so other people can actually build it.

Show the Project’s Journey

Hackaday readers and Supercon attendees love process. They want to see the prototype that looked like a spaghetti monster. They want the board revision with the embarrassing bodge wire. They want the moment when the oscilloscope finally revealed the truth. A polished final result is nice, but the journey is often more educational than the destination.

Avoid the Sales Pitch Trap

Supercon is not the place for a disguised product commercial. If your project is connected to a company, tool, or platform, focus on the engineering lessons rather than the marketing brochure. Technical audiences can smell a sales pitch from across the room, even over the aroma of flux and coffee.

Examples of Proposal Angles That Fit the Supercon Spirit

Need inspiration? Here are proposal angles that would feel right at home in the Hackaday Superconference ecosystem:

• “Turning a Conference Badge Into a Mesh Communication Tool” a talk about radio design, firmware constraints, user interface decisions, and real-world testing.
• “Why My Robot Failed in Public and What I Fixed Next” a practical robotics talk with mechanical, electrical, and software lessons.
• “Making Simple Add-Ons That Are Actually Manufacturable” a workshop covering PCB size limits, connectors, documentation, and assembly planning.
• “Reverse Engineering a Forgotten Peripheral Without Losing Your Weekend” a session about signal analysis, documentation, and vintage hardware.
• “From Breadboard Chaos to Reliable Prototype” a beginner-friendly workshop about taking an idea from wires everywhere to a working board.

The common thread is usefulness. A great Supercon proposal is not just “look what I made.” It is “look what I made, here is what I learned, and here is how you can use those lessons in your own projects.”

Why First-Time Speakers Should Submit

Many technically brilliant people hesitate to submit conference proposals because they assume someone else is more qualified. Someone with a bigger lab. Someone with a cleaner GitHub repository. Someone whose project enclosure does not include hot glue, hope, and a suspiciously load-bearing zip tie.

But Hackaday culture has always celebrated curiosity and persistence. You do not need to be a celebrity engineer to have a valuable story. If you solved a hard problem, documented a useful build, or learned something the hard way, your experience may help others. First-time speakers can bring fresh energy and practical honesty that audiences love.

When writing your proposal, do not apologize for being new. Instead, make the value obvious. Explain the problem, the audience, the lesson, and the outcome. If your session is beginner-friendly, say so. If it goes deep, say that too. The goal is not to impress everyone equally; it is to help the right audience find your session.

What Attendees Gain From a Great CFP Program

A well-curated CFP program gives attendees variety. One hour might feature a deep dive into embedded Linux. The next might explore PCB art, wearable electronics, game hardware, modular laptops, radio communication, mechanical assemblies, or repair culture. That mix is part of what makes Supercon feel alive.

Good CFP selections also create hallway conversations. A talk about badge hacking leads to a table full of people comparing Simple Add-Ons. A workshop on microcontrollers turns into a dinner discussion about power management. A presentation about a failed prototype encourages someone else to submit their project next year. The program does not end when the speaker leaves the stage; it spills into the alley, the worktables, the soldering stations, and the online project pages that follow.

Practical Checklist Before You Submit

Before sending your Hackaday Superconference proposal, run through this quick checklist:

• Is the title clear and interesting?
• Does the description explain what attendees will learn?
• Have you identified the format: short talk, longer talk, or workshop?
• Does the session fit the hardware hacking, maker, engineering, or open-source spirit of Supercon?
• Are the technical details specific enough to show substance?
• Have you removed unnecessary hype?
• Can the session be delivered within the proposed time?
• For workshops, are parts, tools, skill level, and setup requirements realistic?

One more tip: read your proposal out loud. If it sounds like a human explaining a cool project to another human, good. If it sounds like a grant application written by a committee trapped in a filing cabinet, revise.

Experiences Related to the Hackaday Superconference Call for Proposals

The best way to understand the Call For Proposals: Hackaday Superconference topic is to imagine the experience from both sides: the person submitting the idea and the person sitting in the audience months later, watching that idea come alive.

For a presenter, the process often begins with a project that feels too weird, too niche, or too unfinished. Maybe you built a custom input device for a game that only six people have played. Maybe you designed an environmental monitor that survived rain, squirrels, and one deeply confused neighbor. Maybe you created a tiny PCB add-on that blinks in Morse code when someone nearby says “just one more feature.” At first, it may not feel like a conference talk. It feels like a messy personal obsession. But that is exactly why it may work.

Supercon-style audiences tend to appreciate projects with fingerprints on them. They want the real engineering story. They want to know why the first board failed, how you found the bug, what part of the design you would never repeat, and what tiny victory made the whole thing worthwhile. A CFP submission gives that story a shape. It asks you to move from “I built a thing” to “I can teach something through this thing.” That shift is powerful.

From the attendee side, a good accepted proposal can change the entire weekend. You might walk into a talk because the title mentions a chip you recognize and leave with a new approach to debugging. You might attend a workshop because it sounded fun and discover a toolchain that becomes part of your next project. You might see a speaker admit that their first prototype was a disaster and feel suddenly brave enough to show your own work.

There is also the social magic. At a smaller, hands-on gathering like Supercon, the speaker is not a distant figure on a giant stage. They may be standing next to you later, holding a soldering iron, helping someone troubleshoot a badge, or eating tacos while explaining why their enclosure design still bothers them. That closeness makes the CFP more important. It is not just filling a schedule; it is inviting people into a shared workshop of ideas.

For many makers, submitting a proposal is also an act of documentation. To explain a project clearly, you have to organize your thoughts. You find the missing photos. You clean up the repository. You write down the wiring notes that previously lived only in your head and on one napkin of questionable historical value. Even if the proposal is not accepted, the process can make the project stronger.

The biggest lesson is simple: do not wait until your project is perfect. Hardware is never perfect. Firmware is never finished. Documentation always needs one more diagram. The question is whether your experience can help, teach, entertain, or inspire the community. If the answer is yes, the proposal is worth writing.

In that sense, the Hackaday Superconference CFP is more than an announcement. It is a yearly invitation to turn private tinkering into public knowledge. It tells builders that their experiments matter, their failures are useful, and their strange little devices may belong on stage. And honestly, if a room full of hardware hackers cannot appreciate a strange little device, who can?

Conclusion

The Hackaday Superconference Call for Proposals is a reminder that great technical events are built by communities, not just organizers. Supercon thrives because people bring their projects, lessons, prototypes, questions, mistakes, and enthusiasm into the same physical space. A strong proposal does not need to be flashy. It needs to be clear, useful, honest, and rooted in real experience.

If you have a hardware story to tell, a workshop to teach, a tool to demonstrate, or a project that made you mutter at a logic analyzer until midnight, the CFP is your invitation. Write the proposal. Share the lesson. Bring the weird. The Hackaday community has always had room for people who learn by building, and Supercon is one of the best places to prove it.

SEO Tags