Important: This article is general information for education only. It is not tax, legal or career advice and does not recommend any platform, competition or course. Tax treatment depends on facts; consult a qualified tax professional for your situation.


A cloud certification exam, a specialised course and a few months of a learning-platform subscription can easily add up to ₹40,000 or more. Many engineers, testers and analysts try to cover that from sources outside their salary: an internal hackathon prize, a public coding competition, a bug bounty, a paid open-source programme or a data-science contest. Some do well. Others spend weekends on competitions that pay nothing and then discover the prize they did win was taxed more heavily than their salary.

This guide looks at these income sources as a way of funding upskilling: how much they realistically bring in, how each is taxed, and what your employment contract says before you take part. It also covers the non-cash value, which is often larger than the prize.

The main types of competition income

SourceTypical formHow predictable?Likely tax treatment (general)
Internal company hackathonCash prize, vouchers or a learning budget paid by your employerLow; only a few teams winUsually taxed as salary or a perquisite through payroll
External hackathon or coding contestCash prize from an organiserLowOften treated as winnings taxed at a flat 30% plus cess, with TDS by the payer; facts can change this
Bug bounty programmeReward per valid vulnerabilityIrregular; skill-dependentCommonly treated as professional or other income at slab rates, depending on regularity and facts
Paid open-source mentorship or stipendStipend over a fixed periodModerate once selectedGenerally taxable income; foreign payments may also need reporting
Employer-sponsored certification challengeFree exam voucher or reimbursementModerateDepends on how the employer structures it; reimbursements of work-related training are often treated differently from cash

The distinction that matters most is between “winnings” and earned income. Under the Income-tax Act, 2025, as under the earlier law, winnings from lotteries, crossword puzzles, games and similar events are taxed at a flat 30% plus cess, without deduction of expenses and without the benefit of slab rates, and the payer generally deducts tax at source at 30% above a threshold (the TDS provision is section 393(3) in the 2025 Act, which replaced section 194B). Whether a hackathon prize is winnings, or a reward for services, or business income, depends on the nature of the contest and how often you do it. If you participate regularly as a source of income, the answer may differ from a one-off win.

Worked example: two prizes, two tax outcomes

Sneha Reddy, 27, is a data analyst in Hyderabad with a salary of ₹18 lakh, which places her top slab at 20% under the new regime for tax year 2026-27 (check the current slabs before relying on this). In one year she wins two prizes.

  1. Internal hackathon, ₹50,000 paid through payroll. This is added to her salary. At a 20% marginal rate plus 4% cess, the tax is 20.8% × ₹50,000 = ₹10,400. She keeps ₹39,600.
  2. External contest, ₹1,00,000, treated as winnings. The organiser deducts TDS of 30% = ₹30,000 and pays ₹70,000. Her final tax on the winnings is 30% plus 4% cess = 31.2% × ₹1,00,000 = ₹31,200. TDS covers ₹30,000, so she owes ₹1,200 more when filing. She keeps ₹68,800.

From ₹1,50,000 of prizes she keeps ₹39,600 + ₹68,800 = ₹1,08,400. That comfortably funds a professional certification and a year of learning subscriptions, but it came from two lucky results, not a plan. Note also that the external prize is taxed at a higher rate than her salary, and she cannot deduct the laptop upgrade or travel she paid for to attend.

Realistic value: the money is the smaller part

For most participants, competitions do not pay for learning directly. Prize pools are concentrated among a few teams, and bounty income is uneven. The more reliable value tends to be non-cash:

  • Portfolio evidence. A shipped hackathon project, an accepted open-source contribution or an acknowledged vulnerability report is concrete proof for interviews. See our guide to portfolio projects that get interviews.
  • Skill practice under pressure. Time-boxed problems mirror production incidents better than many courses.
  • Visibility. Internal hackathons are a common route to being noticed by leaders in other teams, which can lead to internal moves.
  • Free resources. Many contests give participants cloud credits, tool licences or exam vouchers, which can be worth more than the prize odds suggest.

A sensible approach is to treat competition income as a bonus and fund your core learning plan from a budget you control, such as your employer’s learning allowance, which our article on employer learning budgets explains.

Check your employment contract first

External participation can raise contractual questions, especially in large services and product companies.

  • Outside work clauses. Some contracts restrict paid work or require prior approval. Regular bounty hunting may be treated like freelancing. Our guide to moonlighting rules covers this.
  • Intellectual property. Code written using company equipment, time or confidential knowledge may belong to the employer. Read the IP clause before submitting a project; see who owns the code you write.
  • Security testing. Only test systems within a bounty programme’s published scope and rules. Testing outside scope, or testing your own employer’s clients, can breach contracts and the law.
  • Conflict of interest. Competitions run by a client or competitor may need disclosure.

Step-by-step: using prizes and bounties sensibly

  1. Decide your learning goal and its cost before you look for competitions, so prizes have a clear use.
  2. Read your contract’s outside-work and IP clauses, and get written approval where needed.
  3. Read each contest’s rules on IP ownership, eligibility and tax deduction.
  4. Keep the organiser’s payment advice and TDS certificate, and check that the TDS appears in your annual information statement.
  5. Report prize, bounty and stipend income in your return under the right head. Do not assume TDS settles it; see our guide on reconciling AIS and Form 16.
  6. For foreign payments, keep the bank’s inward remittance record and check whether other reporting applies.
  7. Move the money to a separate learning fund as soon as it arrives.

Common mistakes

  • Assuming a prize is tax-free because it was “a competition”.
  • Ignoring a small TDS shortfall that then becomes a demand with interest.
  • Submitting work-related code to an external contest without checking IP clauses.
  • Paying entry fees to “hackathons” that promise jobs or prizes but are really paid courses.
  • Spending every weekend on contests and burning out; see our article on burnout in IT jobs.

FAQ

If a prize is paid as an exam voucher, is it taxable?
Non-cash prizes can be taxable at their value. For winnings in kind, the rules require tax to be accounted for before release of the prize, so organisers may ask you to pay the tax amount. Check with the organiser and a tax adviser.

Can I set off expenses against bug bounty income?
If the income is treated as business or professional income, genuine expenses may be deductible subject to the rules. If it is treated as winnings, no deductions are allowed. The classification depends on facts.

Does my employer need to know about prizes I win externally?
That depends on your contract and company policy. Many policies require disclosure of outside paid activities; read yours.

Sources


Last reviewed: 9 November 2026. This article is general information, not tax, legal or career advice, and does not recommend any platform, competition or course. Consult a tax professional about how your income should be classified.

Leave a Reply

Trending