Interview
TreeHacks 2027: Application Deadline, Dates, Acceptance Rate & How to Get In
TreeHacks 2027 is 12-14 Feb at Stanford. Deadline not public, about 7% acceptance in 2026, and how to get in. Checked 13 Nov 2026.

Practise the rounds for TreeHacks
Short answer: TreeHacks 2027 is a 36-hour hackathon at Stanford on 12-14 February 2027, according to treehacks.com. Applications go through the official portal (the site's "Apply now" link points to trunk.treehacks.com). No general application open or close date is published on the public site (last checked 13 Nov 2026), so watch the official page and sign in to the portal. On odds, TreeHacks does not publish an official acceptance rate that we could find. For the 2026 edition, the Stanford Daily reported over 15,000 applicants and about 1,000 accepted, which is roughly 7% (the figure NJIT's news office also quoted).
TreeHacks is Stanford's flagship student hackathon and one of the hardest to get into in the US. This guide covers what it is, what we can and cannot verify about applying, how to improve your odds, and how to turn a weekend project into a strong story for internship interviews.
TreeHacks 2027: Key Facts (last checked 13 Nov 2026)
| Detail | Status |
|---|---|
| Event dates | 12-14 February 2027, confirmed on the official site |
| Length | 36 hours (official site) |
| Location | Stanford's campus (official FAQ per the site) |
| Who can apply | "Any enrolled college student (undergrad or grad) from all over the world" (official site) |
| Application opens / closes | Not published on the public page; the portal sits behind a login |
| Stanford student deadline | A priority deadline exists for Stanford applicants; no date is given publicly. Stanford students are not automatically accepted |
| Cost | Free for admitted hackers; food, swag and flights (with regional caps) are covered, per the official site |
| Scale | Official site lists "1K+" hackers and "$1M+" in prizes |
| Teams | Team matching is offered after admission (official site) |
When is the TreeHacks application deadline? On 13 Nov 2026 neither treehacks.com nor the sign-in page of the portal showed an open date or deadline for 2027. Only logged-in applicants see it. For context only: a 2019 Berkeley EECS post said applications for the 2020 event were due before 25 November, so fall deadlines have happened before, but that is not a 2027 date. You can also email the organisers at hello@treehacks.com (the contact listed in their 2026 organiser guide).
If you want the exact deadline, the only reliable source is the application portal itself. Anything else you see on aggregator sites should be treated as third-party until it matches the official page.
What Is TreeHacks?
TreeHacks is run by Stanford students and brings over a thousand builders to campus for a weekend of shipping. Most hackathons are "build something cool and demo it". TreeHacks adds scale and polish: large sponsor presence, hardware, serious prizes, and judges who see a lot of projects.
The 2026 edition gives a feel for it. The Stanford Daily reported over 1,000 students from around the world, more than $500,000 in prizes across 14 categories, teams of up to four, and judging on creativity, technical complexity and social impact. The grand prize went to a motorised smart cane called Shepherd. That mix of a real-world problem plus something physical that works is a recurring winning shape at big hackathons.
For 2027, the official site says there are eight main tracks, all judged by the same criteria. Speakers and sponsors were listed as "coming soon" when we checked.
How the TreeHacks Application Works
What we can verify from the official site:
- You apply through the portal linked from treehacks.com.
- You must agree to the Code of Conduct.
- Admitted hackers get free attendance, and team matching happens after admission.
- Stanford students get priority if they apply by the priority deadline, but are not guaranteed a spot.
What we cannot verify, so you will not find invented specifics here: the exact essay prompts, word limits, whether a resume or links are required, decision release dates, or waitlist rules. The application is behind a login and these change year to year. Do not trust a blog (including this one) that lists last year's questions as this year's without a source. Open the portal as soon as it is live and read it end to end.
Practical advice: apply early if there are any rolling or priority elements, and keep a draft of every answer in a document so you can reuse it for other hackathons.
TreeHacks Acceptance Rate: What the Numbers Say
TreeHacks has not, to our knowledge, published an official acceptance rate. Here is what is reported:
| Edition | Reported figure | Source |
|---|---|---|
| 2026 | Over 15,000 applicants, about 1,000 selected (roughly 7%) | Stanford Daily |
| 2026 | 7% of "over 15,000" applicants | Reported by NJIT news |
| 2027 | No figure yet | Not published (event is 12-14 Feb 2027) |
Treat 7% as a reasonable planning number, not a guarantee. The Stanford Daily gave "about 1,000", not an exact count, and the 2027 pool could be larger or smaller. Also note that "acceptance rate" is the wrong lens for you personally: strong applications are far more likely to get in than the average one, and many applicants submit thin answers.
How to Stand Out in a TreeHacks Application
Selection criteria are not published, so this is judgement, not insider knowledge. What reviewers at large hackathons generally reward is evidence that you finish things.
- Show shipped work. A live link, a GitHub repo with a real README, or a demo video beats any claim about being passionate. Two small finished projects beat one ambitious abandoned one.
- Be specific. "I built a tool that cut my lab's data cleaning from two hours to ten minutes" is stronger than "I love AI".
- Say what you will build or learn. Even without a fixed idea, name an area, such as accessibility, health, or hardware, and why.
- Show range. Mention a hardware, design or non-code contribution if you have one. Teams need more than backend engineers.
- Proofread and be human. Copy-pasted generic answers read as generic. If you use an AI tool to tidy wording, keep the facts and voice yours.
- Apply with a plan B. At a rate near 7% you need other hackathons in the pipeline. See the hackathons calendar, and note that LA Hacks 2027 at UCLA is another big spring option.
Team and Project Prep Before You Arrive
Teams were up to four people in 2026, per the Stanford Daily; the official 2027 page we read does not state a limit, so confirm on the FAQ. Since team matching happens after admission, you do not have to apply with a full team, but a pre-formed team that has built together before usually moves faster.
Before the weekend:
- Agree roles. One person owns the demo and story, one the backend, one the front end or hardware, one integration. Roles can blur but ownership should be clear.
- Prepare your tooling, not your idea. Pre-build nothing that counts as the project (check the rules), but have auth, deployment, an API key setup and a starter repo ready.
- Learn the sponsor APIs. Sponsor prizes are often easier to win than the grand prize, and they reward teams who read the docs early.
- Sort logistics. Travel reimbursement or flights, sleeping gear, chargers, and any hardware you need.
For a longer playbook, read our hackathon strategy guide.
What to Build in 36 Hours
A good TreeHacks-style project has three properties: a clear user, a working core, and a memorable demo.
A sensible time budget for 36 hours:
| Hours | Focus |
|---|---|
| 0-3 | Pick the problem, scope ruthlessly, split tasks |
| 3-20 | Build the core loop end to end, even if ugly |
| 20-28 | Integrate, fix the biggest breakages, add one standout feature |
| 28-33 | Polish, record a backup demo video, write the submission |
| 33-36 | Rehearse the pitch and demo; do not start new features |
Idea shapes that tend to work:
- A health or accessibility tool for a real group of people, tested with at least one real user.
- A hardware plus software hack where the physical thing visibly does something.
- An AI application with a clear failure mode handled, not just a thin wrapper around a chat model.
- A developer tool that saves a measurable amount of time.
Judging, per the 2026 report, weighs creativity, technical complexity and social impact. So ask of every feature: does it raise one of those three? If not, cut it.
Turn the Project Into an Internship Interview Story
For US students, the real payoff of a hackathon is often months later, in a recruiter screen or behavioural round. Interviewers love project stories because they test ownership, trade-offs and communication in one answer.
Use this structure for any project question:
- Context: what problem, what deadline (36 hours is itself a compelling constraint).
- Your role: what you decided and built, not the team's.
- A hard decision: for example, you cut a feature, switched a model, or chose a simpler architecture to hit the demo.
- A setback: something broke at hour 30 and what you did.
- Result and learning: what shipped, who used it, what you would change.
Practise saying this in two minutes, then in ninety seconds. Our guide to behavioural interviews for engineers has strong answer patterns, and an AI mock interview lets you rehearse the spoken version and get feedback on clarity and structure. Do not claim a result you cannot back up: if an interviewer asks how the auth worked, you should know.
Frequently Asked Questions
When is TreeHacks 2027?
12-14 February 2027, a 36-hour hackathon on Stanford's campus, per treehacks.com.
When do TreeHacks 2027 applications open and close?
Not published on the public site as of 13 Nov 2026 (the portal sign-in page shows no dates either). Check the official site and portal. A priority deadline for Stanford students exists but its date is not shown publicly.
What is the TreeHacks acceptance rate?
No official figure that we could find. For 2026, the Stanford Daily reported over 15,000 applicants and about 1,000 accepted, roughly 7%.
Who can apply to TreeHacks?
Any enrolled college student, undergraduate or graduate, from anywhere in the world, according to the official site. Stanford students are not automatically admitted.
Is TreeHacks free?
Yes for admitted hackers. The official site says food, swag and flights (with regional caps) are covered.
Do I need a team to apply?
The official site says team matching is provided after admission. We could not verify whether applying with a team improves your odds for TreeHacks (LA Hacks says it can for its own application).
How do I get into TreeHacks?
Apply as early as you can, show shipped projects with links, be specific about what you will build or learn, and have backup hackathons lined up. There is no guaranteed method.
How selective is TreeHacks compared with other hackathons?
Very. About 7% of 2026 applicants were admitted, which is far tougher than most student hackathons. Apply to two or three others in parallel; our hackathon calendar lists them.
Does being a Stanford student help?
Stanford students who apply by the priority deadline get priority consideration, but the official site says they are not automatically accepted, and the priority date is not shown publicly.
Will a hackathon help my internship search?
It can, mainly as a story. A shipped project gives you concrete material for behavioural and project-deep-dive questions, even if you do not win. To turn it into a polished answer, rehearse it in a spoken AI mock interview that asks follow-up questions about your code, and keep your coding sharp with timed OA practice and the DSA patterns sheet.
Is there a similar event on the West Coast in spring?
Yes. LA Hacks runs at UCLA in spring; see our LA Hacks 2027 guide.
Final Thoughts
TreeHacks 2027 is on the calendar for 12-14 February, but the application timeline is not public, so the best move now is preparation: ship one or two small projects with links, line up teammates, and write down your project stories. Whether or not you are admitted, the same work makes you a stronger internship candidate. Compare your options on the hackathons calendar.
Sources: treehacks.com (official, checked 13 Nov 2026), Stanford Daily (15 Feb 2026), NJIT News. Details can change; confirm on the official site.
Topics
Related on Thita
Your next step
Practise the rounds for TreeHacks
Most selection rounds open with a timed coding test. Work through the DSA patterns they draw on, run your code in the browser, then rehearse the interview out loud with an AI interviewer.