Adobe Hackathon Round 2 | Frustration Grows Over Selection Process
The recent Adobe Hackathon Round 2 has ignited significant backlash among participants as a mere 416 teams were selected from a staggering 28,000 submissions. Many contestants have taken to forums expressing their doubts about the fairness and transparency of the selection criteria. This growing dissatisfaction raises questions about how these shortlist decisions were made.
Shortlisting Disappointment
Participants are reeling from the shock that only 1.48% of entries were chosen. A common comment is, “Nah, I thought my team did really well, but nvm..” Many others echoed similar sentiments, asking, “Do u know how they have picked??” This mixture of frustration and confusion highlights widespread concern over the selection process.
Evaluation Process Under Fire
The prevailing view in forums is that the selection process lacked transparency. Many users are questioning whether all submissions were fairly evaluated. One participant remarked, “I bet they didn’t read everyone’s 2500 character fckin case studies,” reflecting a broader concern that quality entries may not have received due consideration.
Bias and Transparency Issues
Several comments suggest a bias towards teams from recognized colleges:
"Looks like more people are from well-known colleges only," voiced a frustrated contestant, suggesting that established institutions may have had an edge.
Sentiment Across the Board
While congratulations poured in for the shortlisted teams, the general mood is primarily negative:
Disappointment: Many participants felt their hard work was overlooked.
Skepticism: There are calls for greater transparency in the judging process.
Community Response: Participants have shown empathy, with responses like, “You’re not alone,” indicating a supportive atmosphere amid the discontent.
Key Highlights
🔹 Out of 28,000 entrants, only 416 made it to the next round.
🔹 “Congrats to those who made it!” remains a mixed sentiment, reflecting shared disappointment.
🔹 Ongoing discussions on forums highlight a strong desire for clarity: "Have you got any shortlist/rejection mail? I have not got any."
The fallout from this hackathon is leaving Adobe with pressing concerns to address. The community awaits a response regarding how the judging criteria might evolve for future events.
Future Directions for Adobe
The growing pressure on Adobe to clarify its evaluation methods is palpable. Participants, representing about 70% of applicants, are expecting improved transparency for future hackathons. This disappointment could force a rethink of how selections are made, aiming for fairness and inclusivity regardless of participants' educational backgrounds.
A Reminder from the Past
Similar scrutiny faced NASA during the space shuttle program in the 1970s, where frustrations arose over selections favoring established firms over novel ideas. This historical context emphasizes the need for innovative companies like Adobe to reconsider their approach to nurturing creativity while maintaining public trust.
As participants await a response to their valid concerns, the debate over fairness in the hackathon selection process continues to heat up.