Applications open Berkeley, CA SF Tech Week

Innovation Intelligence Hackathon

Find the problem worth solving.

A selective startup hackathon. Build for a week, then demo live to founders and investors on October 11.

Build week Oct 5–11  ·  Demo Day Oct 11, 1–4 PM  ·  UC Berkeley  ·  SCET × DECODE  ·  Official #SFTechWeek event  ·  Build week Oct 5–11  ·  Demo Day Oct 11, 1–4 PM  ·  UC Berkeley  ·  SCET × DECODE  ·  Official #SFTechWeek event  · 
Build week
Oct 5 – 11
Demo Day
Sun, Oct 11 · 1–4 PM
Venue
UC Berkeley
Teams
1 – 4 builders
Applications open · Demo Day in
{{ cdDays }}
Days
{{ cdHours }}
Hours
{{ cdMins }}
Min
{{ cdSecs }}
Sec
Priority deadline Sep 28 · final Oct 4. Reviewed on a rolling basis.
Hosted with support from
Pantas and Ting Sutardja Center for Entrepreneurship & Technology, Berkeley Engineering
Innovators-in-Residence DeCal Leads
DECODE
Berkeley & Stanford founder community
Tech Week by a16z
Official #SFTechWeek event
01Thesis

Not another generic hackathon.

01

Build for a real problem.

Name a market and a customer, not just a demo. Sharpest insight beats largest codebase.

02

Think past 4:00 PM.

Judging weighs insight and venture potential — evidence of something worth continuing.

03

Work next to people who build and invest.

Founders, operators, and investors from SCET and DECODE are in the room all week.

04

Demo like it matters.

Three minutes, live, on October 11. A startup demo, not a class presentation.

02Process

How it works.

Four steps from a pain point to a live demo.

01

Choose a track

Start from a real problem in one of five areas.

02

Build your team

Form a team across engineering, design, research, and business.

03

Build for a week

Turn the idea into a working prototype.

04

Demo live

Present to founders, investors, and the Tech Week community.

Great companies often begin as a small experiment run by people who couldn't stop thinking about a problem.

A full week to build — long enough to talk to real users and ship something that works — and three hours on October 11 to prove it.

We are not looking for finished companies. We are looking for evidence of something worth continuing.

03Tracks

Five tracks.

Tracks mark the space you're building in, not a required format. Every project competes for the general awards.

TRACK 01→

AI-Native Enterprise

Reinvent a real workflow with AI.

Agents · vertical AI · developer tools · legal · finance · operations · cybersecurity · infrastructure

Track award
Best Enterprise Reinvention
TRACK 02→

The Physical World

Build where software meets atoms.

Robotics · manufacturing · logistics · mobility · autonomy · computer vision · energy · drones · IoT

Track award
Best Bits-to-Atoms Startup
TRACK 03→

Health & Human Performance

Build products that improve how people live, work, learn, or recover.

Health · biotech · accessibility · education · diagnostics · productivity · aging · HCI

Track award
Best Human Impact
TRACK 04→

Frontier & Deep Tech

Build for technologies and markets that are still taking shape.

Semiconductors · space · quantum · advanced computing · energy · climate · materials · scientific tools

Track award
Best Frontier Technology
TRACK 05→

Consumer & New Experiences

Build products people genuinely want to use.

Consumer AI · social · creator tools · marketplaces · commerce · travel · new interfaces · entertainment

Track award
Best Consumer Experience

The goal isn't to build something cool for a week.

Start with a real problem. Build something worth pursuing.

04Format

A week to build.
Three hours to prove it.

Teams form at kickoff on October 5 and build through the week. October 11 is judging and Demo Day.

→ Coaching runs all week — daily office hours in person and online.
→ Build remotely or on campus during the week; Demo Day is in person.
→ Existing code, open-source, and AI tools are fine; the product must be built during build week.
→ Bring a laptop and a charger. You keep your IP.
Coaching · all week
A mini accelerator, compressed into six days.

Founders, operators, SCET Innovators-in-Residence, and investors hold office hours every day of build week — on campus and online.

· Problem framing and customer discovery early in the week
· Technical and product review mid-week
· Pitch and demo rehearsal before submissions close
Build week · Oct 5 – 10
Sun, Oct 5
Kickoff — track briefings and team formation. Building starts the same day.
Oct 6 – 9
Build — daily coaching and office hours with mentors and investors, on campus and online
Sat, Oct 10
Submissions close, 11:59 PM — repo, demo video, and one-paragraph thesis
Demo Day · Sun, Oct 11 · UC Berkeley
1:00
Check-in and setup
1:20
Opening remarks — SCET Innovators-in-Residence and DECODE
1:30
Preliminary judging — table rounds with judges and mentors
2:30
Finalists announced
2:45
Demo Day — three minutes per finalist, live on stage
3:45
Awards
4:00
Close — community hour with mentors and investors
05What wins

What we're looking for.

Not a finished company. Evidence of something worth continuing.

01
A problem someone actually has

Named customer, named market. Not a use case invented to fit the tech.

02
An insight the room missed

Something you understood about the problem that others did not.

03
Software that runs

A working prototype beats a deck. Rough edges are fine; vapor is not.

04
A reason to keep going

A first customer, a next step, a team that wants to build it past Sunday.

Recognition
Best Overall

One top award for the strongest project overall, plus one award per track. Judges may name a small number of standouts beyond that.

06Judging

How judging works.

Five weighted dimensions, scored by founders, operators, and investors. No revenue or business plan expected.

Judges announced soon.
Problem / Insight
20%

Is this a meaningful problem with a non-obvious insight?

Product & Demo
25%

Did the team build something compelling and coherent?

Technical Execution
20%

How strong is the implementation relative to the time available?

Market / Venture Potential
20%

Could this become an important product or company?

Team & Pitch
15%

Can the team say why this matters and why they are suited to build it?

Applications are selective.

One short form, reviewed on a rolling basis. Priority deadline Sep 28.

07Questions

Questions.

Who can apply?+

Undergrads, grad students, and recent graduates from any school — technical or not.

Do I need a team or an idea beforehand?+

No. Apply solo or with a team — teams form at the October 5 kickoff.

Can I participate if I'm not a strong programmer?+

Yes. The strongest teams mix technical, design, and market thinking.

Do teams get any support during the week?+

Yes. Build week runs like a short accelerator: daily office hours on campus and online, covering problem framing, technical review, and pitch practice.

Do I have to fit a track?+

No. Tracks carry their own prizes, but every project competes for the general awards.

Can I use existing code, and can I keep working after?+

Existing code, open-source, and AI tools are fine — the demo must be built Oct 5–10. You keep your IP.

How are projects judged?+

Five weighted dimensions — the full rubric is above.

Will the event be photographed?+

Yes. Photos and video use are covered in the participation terms; ask an organizer to be excluded from published media.

When do decisions go out?+

Decisions are sent by email on a rolling basis after the priority deadline. There is no status portal.

Application · Fall 2026

Apply to the Innovation Intelligence Hackathon.

Reviewed on a rolling basis. We look for builders, designers, researchers, and entrepreneurial thinkers.

Priority deadline
Sep 28
Final deadline
Oct 4
Time to complete
~7 min
Form slot

Airtable form mounts here

Applications run through the Partiful event page until the form is live.

By submitting you agree to the participation terms — conduct, photography and media, and data use. Responses are seen only by the organizing team.
After you submit

A confirmation email lands right away. Decisions follow by email — no status portal.

If accepted

An RSVP link, plus team formation details.

Questions

Use the open-ended question in the form. Organizers reply directly.

Organizers

Run by builders, for builders.

A build week hosted with the UC Berkeley SCET Innovators-in-Residence DeCal leads and DECODE, the largest founder community across Berkeley and Stanford. Demo Day is an official Tech Week by a16z event.

Host program
Sutardja Center for Entrepreneurship & Technology

SCET Innovators-in-Residence

Berkeley's entrepreneurship center pairs students with practicing founders and operators. Its DeCal leads co-host this event.

Co-host
DECODE

DECODE

The largest founder community across Berkeley and Stanford, connecting student builders with founders and investors.

Partner, judge, or mentor.

Interested in partnering or co-hosting, judging on Demo Day, or mentoring during build week? Fill out the form and we’ll be in touch.

Hosted by a UC Berkeley program and a student founder community; not sponsored by the university. Conduct, photography and media, and data use are covered in the participation terms.
Participation terms

Terms of participation.

Innovation Intelligence Hackathon · Fall 2026

Submitting an application confirms your agreement to the terms below. They cover conduct, media, data, intellectual property, and eligibility for the build week of October 5–10 and Demo Day on October 11, 2026.

01

Conduct

All participants, mentors, judges, and organizers are expected to behave professionally toward one another. Harassment, discrimination, plagiarism, misrepresentation of work, and interference with another team are grounds for removal from the event at the organizers’ discretion. Concerns may be raised with any organizer during the event or submitted through the application form.

02

Photography and media

The event is photographed and recorded. Images, video, and audio captured during build week and Demo Day may be used in event recaps, program materials, and partner communications, and may include team names and project summaries. Participants who prefer not to appear in published media may notify an organizer at any time and will be excluded.

03

Data and privacy

Application responses are accessible only to the organizing team and are used solely to evaluate applications and operate the event. Data is not sold or shared with third parties for marketing purposes. Participants may request deletion of their application data after the event.

04

Intellectual property

Participants retain full ownership of all work created during the event. No rights are transferred to the organizers, host programs, or partners. Organizers may publicly reference a project by name with a brief summary as part of event coverage.

05

Eligibility and submissions

Participation is open to current students and recent graduates. Teams may include one to four members. Projects must be developed during the build week of October 5–10; pre-existing code, open-source libraries, and AI tools are permitted. Submissions close at 11:59 PM on October 10. Demo Day attendance is in person at UC Berkeley.

06

Changes

Schedule, format, judging panel, and awards are subject to change. Material changes will be communicated by email to accepted participants.

Last updated September 2026. Questions may be submitted through the application form.
Hosted with SCET Innovators-in-Residence and DECODE.