How to Make Money with Hackathon Prizes: Entering Devpost Online Hackathons and Claiming Your Prize (2026)

📘 Full practical guide (October 2026)

🪜 Step-by-step

1. Understand who pays the prize. On Devpost, some events are administered by Devpost and others by the organizer. For Devpost-administered events, winners receive an email from prizes@devpost.com with a claim link. For independently run events the organizer judges and pays; Devpost does not hold the prize money. The Rules tab names the administrator, eligible countries, age limits and prize list.
2. Pick events with the 5-filter method. Filter the hackathon list by Online and Open, then check: (1) your country is eligible, (2) enough time remains before the deadline, (3) the number of registered participants, (4) how many category prizes exist, and (5) whether a required sponsor product fits your skills. Devpost’s own Hack Devpost rules, for example, listed $100 feedback prizes, $50 prizes for early feedback and $400 idea prizes: many small prizes suit beginners.
3. Plan backwards from the judging criteria. Copy the criteria (for example technical implementation, design, impact, originality, use of the sponsor’s tool) into a table and decide which demo moment proves each one. Missing a required API or product can disqualify you, so note it at the top of your plan.
4. Build small and actually finish. Limit scope to one or two features and get a working demo early. Typical required items are a project description, a demo video (often length-limited), a public code repository and testing instructions. Most rules require work created during the submission period, so do not submit an old project unless the rules allow it.
5. Polish the project page and video. Open with one sentence: what problem, for whom, and how you solved it. Add sub-headings that mirror the judging criteria, screenshots, and the tech stack. In the video, show the product working within the first 20 seconds.
6. Claim the prize correctly. Per Devpost Help: click the claim link in the email from prizes@devpost.com, enter your name, payment country, tax residence and team details, choose PayPal, Payoneer or Wise where available (paper checks are for US residents), and upload W-8BEN if you are a non-US individual (W-8BEN-E for organizations, W-9 for US persons). Team prizes go to the team representative, who splits them. Make sure your account can receive USD; undeliverable prizes may face fees, delays or forfeiture.
7. Turn entries into longer-term income. Keep every project on GitHub with a clean README, write a short post about what you built, and connect with sponsor teams and judges. Hackathon projects often become portfolio pieces for freelance work, small paid apps or job offers.

📖 Worked example

Example: a university student with basic web skills entered three online Devpost events in two months. She skipped first-place races and targeted events with category prizes she could realistically win, such as best use of a sponsor API and best beginner project. The first two entries won nothing but became portfolio pieces; the third won a $250 category prize, paid via PayPal about seven weeks after she submitted W-8BEN, plus $100 in cloud credits.

An illustrative scenario based on public rules and typical amounts; real results differ.

💵 Amounts and math

• Hack Devpost example (from its rules): $50–$400 per prize across many small prizes.
• Team math: a $1,000 prize split four ways = $250 each before any withholding or fees.
• Time math: 25 hours over a weekend for a $250 category prize ≈ $10/hour if you win, $0 if not; the portfolio and credits are the steady part of the return.
• Non-cash prizes (credits, swag) usually cannot be exchanged for cash, so check whether a prize is cash before you plan around it.

🧾 Taxes, forms and payouts

• Non-US individuals usually submit Form W-8BEN when claiming a Devpost-administered cash prize; it certifies foreign status and is not a tax return.
• Depending on country and treaty, US withholding may still apply to prizes, so read the claim instructions carefully.
• In most countries prize money is taxable income that you report locally; keep the winner email and payment record.
• Payout fees and currency conversion vary by PayPal, Payoneer and Wise; compare them before your first claim.

General information, not tax advice. Check your local tax authority or an adviser for your situation.

🔗 Current tools (links)

• Devpost hackathons — find online hackathons and filter by eligibility
• Devpost Help: claiming a cash prize — official prize claim steps
• How hackathons on Devpost work — who administers and pays prizes
• GitHub — host your code and README
• Wise — receive USD and convert at a low fee
• Payoneer — receive international payouts
• IRS Form W-8BEN — foreign status form for non-US individuals

✍️ Copy-paste templates

Event: {name} | Deadline (your time zone): {date time}
Administrator: Devpost / organizer
Eligible countries include mine? Y/N | Age OK? Y/N
Required tech: {API/product}
Category prizes I can target: {list}
Participants registered: {n}
Submission items: description / video ({max} min) / repo / testing info

{Project name} helps {who} {do what} by {how}.
Problem: {one sentence}
What it does: {2–3 bullet points}
How we built it: {stack + sponsor tool}
Judging criteria: Technical — {proof}; Design — {proof}; Impact — {proof}
Try it: {link} | Code: {repo} | Video: {link}

Team: {names}
Prize representative: {name}
Cash prizes split: equal / {percentages}, paid within {N} days of receipt
Fees and withholding deducted before splitting: yes
Code license after the event: {license}

📅 First-week plan

• Day 1: Create a Devpost account, link GitHub, shortlist five online events you are eligible for.
• Day 2: Read the rules of each and pick one; convert the deadline to your time zone.
• Day 3: Build the judging-criteria table, fix a one- or two-feature scope, find teammates if needed.
• Days 4–5: Build the core feature and commit daily.
• Day 6: Record the demo video and write the README and project page.
• Day 7: Submit hours before the deadline and check that your PayPal, Payoneer or Wise account can receive USD.

🚫 Common mistakes and what to do instead

• Misreading the deadline time zone → convert it on day one and set an alarm.
• Skipping a required sponsor product → put it at the top of your plan.
• Submitting code written before the event → build during the submission period unless rules say otherwise.
• No video or an over-length video → keep within the limit and show the product early.
• Missing the claim-form deadline → reply to prize emails promptly (example rules give about 10 business days).
• Using code, images or music without checking licenses → use your own or properly licensed assets.

📚 Related guides

• How to Make Money with Bug Bounty Hunting
• Wise vs Payoneer vs PayPal: Best Way to Get Paid Internationally
• How to Make Money with Mobile App or Micro-SaaS
• How to Make Money with Chrome Extension Development
• How to Make Money with Discord Bot Development
• Taxes When You Make Money on the Side: The Basics Every Freelancer Should Know

Last updated: October 28, 2026.