Compare commits

..

7 Commits

Author SHA1 Message Date
211fa66618 Updated formatting, graphs, and draft status for Inter IIT 13.0 article 2026-05-03 01:26:54 +05:30
036ffdd33d Merge remote-tracking branch 'origin/master' into add-inter-iit-post
# Conflicts:
#	_posts/2026-05-03-inter-iit-techmeet-13.md
2026-05-03 00:25:51 +05:30
0f4de524d5 fix: config file and article 2026-05-03 00:19:54 +05:30
7a199b071a Add Inter IIT article (#232)
* add: the ship of theseus

* move image

* add: interiit article

---------

Co-authored-by: Rajdeep Aher <math.enthusiast163@gmail.com>
2026-05-03 00:10:23 +05:30
92ca64f6db add: interiit article 2026-05-03 00:08:23 +05:30
7cc0cdd77a move image 2025-10-23 12:54:16 +05:30
87eb5123dd add: the ship of theseus 2025-10-23 12:36:33 +05:30
2 changed files with 125 additions and 0 deletions

View File

@ -25,5 +25,6 @@ title: Watch Out, IIT Roorkee
url: http://watchout.iitr.ac.in url: http://watchout.iitr.ac.in
plugins: [jekyll-paginate] plugins: [jekyll-paginate]
description: The official news magazine of IIT Roorkee. description: The official news magazine of IIT Roorkee.
timezone: Asia/Kolkata
paginate: 10 paginate: 10
paginate_path: "/page/:num" paginate_path: "/page/:num"

View File

@ -0,0 +1,124 @@
---
layout: post
title: "INTER IIT TECH MEET 13.0: THE FALLOUT"
tags: [wona]
author: Watch Out News Agency
excerpt: "A structured reflection on IIT Roorkee's participation in Inter IIT Tech Meet 13.0—what worked, the challenges faced, and the path forward."
---
**Note: This article is currently under review and is unfinished.**
*Inter IIT Tech Meet 13.0 represented another chapter in a competition that has, over the years, come to mean a great deal to students across the country. IIT Roorkee's participation this year was no different in that regard. Students gave significant time, effort, and thought to their work, and that commitment deserves to be acknowledged before anything else.*
*In the weeks since the event concluded, a number of narratives have circulated within the community: some grounded in experience, others shaped by incomplete information or the natural frustration that follows an intense competition. This report is an attempt to move past those narratives and offer a structured reflection on how the participation unfolded, what worked, and where genuine gaps exist.*
*This report is based on anonymized feedback from IIT Roorkee Inter IIT Tech Meet 13.0 participants across multiple problem statements. Individual identifying details have been omitted to protect respondent privacy. Views expressed represent participant perspectives and may not reflect complete information about all aspects of event management and evaluation.*
<hr>
<iframe title="IITR Inter IIT Tech Performance (2022 - 25)" aria-label="Stacked column chart" id="datawrapper-chart-IFIvN" src="https://datawrapper.dwcdn.net/IFIvN/3/" scrolling="no" frameborder="0" style="width: 100%; min-width: 100% !important; border: none; margin: 2em 0;" height="437" data-external="1"></iframe>
<script type="text/javascript">window.addEventListener("message",function(a){if(void 0!==a.data["datawrapper-height"]){var e=document.querySelectorAll("iframe");for(var t in a.data["datawrapper-height"])for(var r,i=0;r=e[i];i++)if(r.contentWindow===a.source){var d=a.data["datawrapper-height"][t]+"px";r.style.height=d}}});</script>
## Selection
Views on team selection varied across problem statements (PSs). It has been widely reported that for several PSs, including the ones with lower preparation, the selection process lacked sufficient rigor, with decisions occasionally based on 'connections' rather than demonstrated competence. In contrast, teams from more structured PSs reported thorough interviews and merit-based selection.
## Structural Factors
The timing of General Secretary elections compounded these issues. Team selections had concluded before new student leadership was elected, limiting their ability to ensure consistency. The role of "PS Leads" also created confusion: whether these were leadership positions or simply administrative points of contact remained unclear to many participants.
When questioned about the selection and exact responsibilities of PS Leads, the Contingent Leadership clarified that:
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em> The PS Lead is an unofficial internal role dedicated to task coordination and progress oversight.To maintain transparency in their selection, leadership stated that once PS domains and required skills were confirmed, an open application form was released directly on the student noticeboard, ensuring the opportunity was accessible to everyone, including undergraduate, postgraduate, and PhD students. Following this, relevant STC clubs secretaries were consulted, and expedited online meetings were held necessitated by Diwali vacations to appoint PS Leads based on technical competence, prior responsibilities, and past performance in Inter IIT and GC Tech.<br><br> Leadership firmly denied any intentional favoritism in the broader recruitment process, explaining that the sheer volume of applicants made universal interviews unfeasible, thus requiring initial filtering via resumes and form responses. To ensure fairness, all final team selections were heavily vetted through discussions with the Deputy Contingent Leaders, the Faculty Advisor, and the General Secretary Technical, with a priority placed on the necessary skill sets and cross-year diversity rather than technical club affiliations.
<br><br>Finally, leadership attributed the seemingly rushed and rigid selection process for no-preparation events, such as MathBowl, to a sudden rule change that required early team submission, drastically reducing their available decision-making window to a mere two to three days</em>
</blockquote>
## Preparation
The notion that teams underperformed due to lack of effort does not hold up to scrutiny. Teams reported long preparation hours often 14+ hours daily over multiple weeks alongside academic commitments including end-semester examinations and placement preparation. Many participants felt their technical solutions and depth of analysis were comparable to, if not stronger than, those of peer IITs.
The real issue was workload imbalance. In too many cases, preparation was carried by two or three individuals while others contributed marginally. This particularly affected morale in certain cases, where team members were either just contributing through 'GPT prompts' or, in some cases, not at all.
**What action was taken against low performing or disinterested members of the contingent? Do you have the authority to remove members mid-preparation?**
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>There was no member who made no contribution to the final submission. While it is true that some members contributed more than others, everyone was involved in some capacity. <br><br>While it is true that some members contributed more than others, labelling members as entirely non-interested or non-performing would be an extreme characterisation. Once team names are officially submitted, changes or removals are not permitted under the Inter IIT rulebook, and therefore no mid-preparation removals were possible. When such concerns were raised, we personally intervened by speaking with the teams and the concerned individuals, resolving most cases. In one instance, a member misrepresented their availability, causing distress within the team; since removal was not permitted, we worked out an alternative arrangement to minimise disruption.</em>
</blockquote>
## Evaluation and Transparency
Concerns around evaluation and marking were unanimously raised.Several teams reported difficulty reconciling final scores with the rubrics stated in PS documents or with judges' verbal feedback during presentations. In some cases, objective numerical results or optimizations appeared insufficiently reflected in final rankings. It is important to note that participants do not uniformly allege deliberate unfairness. Rather, the dominant concern was opacity: the absence of detailed score breakdowns and clarity on how different components were weighted.
In one such scenario: The original problem statement specified 65% weightage for digital design and 35% for analog modeling. However, final scoring appeared to heavily favor analog work, with teams that had optimized for digital excellence finding their efforts undervalued.
The other issue that came up is of compliance violations: multiple teams allegedly violated explicit tool bans(such as using unauthorized Process Design Kits that provided inherent advantages). Despite clear evidence and, in some cases, admissions during presentations, no penalties or disqualifications were reportedly issued which clearly affected the rankings.
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>The CL and DCL confirm the loose adherence to the marking guidelines which benefitted certain teams due to the subjective preferences of the judges. They highlighted the case of the Game Development Low-Prep PS, where 2D games appeared to be preferred over the 3D submission by our team that was worked on with rigour constituting sleepless nights.</em>
</blockquote>
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>“For example, in the game development problem statement, our team worked continuously with minimal sleep to develop a multi-level, aesthetic 3D platformer. However, the judge appeared to prioritize simpler 2D games, which led to lower-than-expected scores. Such preferences could not have been anticipated since judges were revealed only on the day of evaluation. In some cases, judges were associated with companies incubated at the host institute or had close institutional links. These concerns were raised multiple times, but the response cited existing MoUs assuring unbiased judging, leaving us with limited options.”</em>
</blockquote>
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>The DCL mentions a similar case on the Cyber Security Low-Prep PS where despite communication being facilitated with the judges by the OCs, the final result did not favour our institutes team. It was additionally highlighted that the CL and DCLs do not have any direct impact on the scores awarded to IIT Roorkee.</em>
</blockquote>
## Contentions
The handling of contentions has emerged as another area requiring attention. While some participants felt the Contingent Leaders could have raised and defended contentions more effectively.
The response received was:
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>“The contentions we raised were eventually accepted, except in three cases where faults were clearly on our side. In those instances, we took accountability. One example involved a second-year contingent member recording an event despite explicit instructions that videography was prohibited. Such violations were acknowledged by us.”</em>
</blockquote>
### A Note on the ISRO PS
One particular instance that drew significant attention was the ISRO problem statement, where the contingent's medal outcome was reportedly revised from Gold to Silver after the closing ceremony. The change was communicated without explanation, bypassing board meetings or any formal dispute resolution mechanism. It is also alleged that the administration was not able to support the team adequately during this situation, leaving participants feeling abandoned after months of intensive work.
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>Even after the CL meetings concluded and contentions were mutually decided, changes continued to be made after we had left Patna. This included IIT Roorkee being demoted from gold to silver in the ISRO problem statement. Contentions are meant to be resolved transparently during CL meetings in the presence of representatives from all IITs, and post-meet changes undermine this process. We submitted written complaints regarding this issue, but the organizing committee justified the changes citing recalculation errors or re-evaluation by judges<br><br>-CL</em>
</blockquote>
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>Rankings for medal allocation underwent multiple revisions and recalculations after the closing ceremony. In the ISRO PS case, an incorrect contention against IIT Madras was initially accounted for but later removed during revisions, leading to a change in rankings. This development was communicated to the admin teams on Discord.<br><br>-DCL</em>
</blockquote>
## Logistics
Upon arriving at IIT Patna, the contingent faced immediate logistical hurdles. Security at the main gate lacked the arrival list, forcing students to wait in their buses for nearly an hour and a half. When they were finally admitted, participants found unclean rooms missing basic necessities like sheets, blankets, pillows, and mattresses.
<blockquote style="background-color: #f9f9f9; padding: 15px 20px; border-left: 5px solid #e74c3c; margin: 1.5em 0;">
<em>The Contingent Leader and DCL escalated these issues and received a formal apology from the Inter IIT Patna Organizing Committee, which attributed the severe shortfalls to vendor supply failures. Separately, the internal allocation of specific software and computational resources for niche problem statements during the preparation phase remains a point of dispute among contingent members. Despite these on ground challenges, participants reported that the travel arrangements handled by the IIT Roorkee administration were smooth and free of issues.</em>
</blockquote>
## Recommendations
To strengthen future Inter IIT Tech Meet participation, several structural and cultural improvements are recommended. During the preparation phase, mock contention debates should be conducted to build advocacy skills among Contingent Leaders (CLs) and Deputy Contingent Leaders (DCLs), ensuring they can confidently defend team work against technical challenges, articulate evaluation inconsistencies, and present evidence effectively: all with a clear understanding of formal dispute procedures before arriving at the competition. General Secretary elections should be held prior to team selections so that elected leadership can implement consistent evaluation standards across all problem statements from the start. STC clubs are encouraged to increase their intake by approximately ten to twenty percent and treat Inter IIT Tech as a dedicated, long-term institutional objective. GC Tech should be conducted in a more professional and structured manner, as it serves as a vital intra-IIT preparation ground.
On the cultural front, both the CL and DCL strongly echo the need for a broader shift in how the institute views Inter IIT. As the CL notes, since Inter IIT Tech offers no monetary incentives, students often deprioritise it in favour of internships, placements, or returning home during winter break: a challenge further amplified by IIT Patna's location. The DCL reiterates that clubs should actively integrate Inter IIT-focused preparation into their curricula and that participation must be reframed as a matter of institutional prestige and an opportunity to represent the institute and compete with the best minds in the country. Ultimately, a cultural shift is needed to position Inter IIT competitions as highly respected and aspirational within the institute.
## The Value Question
A concerning pattern emerged in participant responses: multiple participants stated that Inter IIT felt like "a waste of time" and indicated they would not participate again. The issue is not bitterness over losses. It is disillusionment with process. When months of intensive work culminate in opaque evaluation, post-ceremony result changes, and unanswered questions, even winning feels hollow.
It is equally important to acknowledge what Inter IIT Tech does genuinely well. Participants consistently valued the exposure to unique, industry-relevant problem statements, the depth of technical growth that comes from working under real pressure, and the opportunity to collaborate and connect with peers from institutions across the country. These are meaningful outcomes that speak to the competition's core strengths, and they should not be overlooked.
This section is not intended as an indictment of Inter IIT Tech Meet, which has long served as a meaningful platform for technical development and inter-institutional exchange. It is offered in the spirit of constructive reflection with the belief that a competition of this stature deserves processes that match the dedication its participants bring to it. Participants invest significant time and energy in Inter IIT, often balancing it against academic and personal commitments, because they trust that the process is designed to reward genuine excellence. Strengthening the transparency and consistency of evaluation, selection, and contention handling would go a long way in reinforcing that trust.
## Our Two Cents
Whether the final result was technically correct or not is ultimately unknowable without access to complete evaluation records. What is clear is that the process failed: results announced with finality were reversed without transparency, leaving participants with legitimate grievances regardless of the outcome's technical merit.
Before concluding, it is essential to acknowledge the Contingent Leader and Deputy Contingent Leaders who stewarded this contingent through unprecedented logistical and procedural challenges. They operated within severe constraints: unclear rules, compressed timelines, and limited institutional leverage and yet chose to lead with integrity. They escalated concerns when needed. When their own decisions could have been better, they said so. What stands out most is their willingness to speak candidly about what happened: where the system failed, where they fell short, and what their teams deserved but did not receive. This transparency, offered after the event when silence would have been easier, is accountability in its truest form.
We also recognize every participant in this contingent. They invested months of intensive work; balancing late-night preparation sessions with exams, placements, and personal commitments. They brought technical depth and genuine care to their problem statements. They pushed each other to be better. And they did all of this in an environment where process failures were beyond their control. That they maintained their standards despite those failures speaks to their character as much as their competence.
This report exists because both leadership and participants chose candor over silence. The problems identified here: in selection, evaluation, contention handling, and post-event transparency should be viewed as structural and not personal. They are also fixable. The Inter IIT organizing committees have demonstrated the capacity to run a competition of genuine technical merit. What remains to be seen is whether they will match that capacity with processes worthy of the effort their participants invest.
<iframe title="Inter IIT Tech Meet 13.0 Feedback" aria-label="Split Bars" id="datawrapper-chart-E0r82" src="https://datawrapper.dwcdn.net/E0r82/6/" scrolling="no" frameborder="0" style="width: 100%; min-width: 100% !important; border: none; margin-top: 2em;" height="558" data-external="1"></iframe>
<script type="text/javascript">!function(){"use strict";window.addEventListener("message",(function(a){if(void 0!==a.data["datawrapper-height"]){var e=document.querySelectorAll("iframe");for(var t in a.data["datawrapper-height"])for(var r=0;r<e.length;r++)if(e[r].contentWindow===a.source){e[r].style.height=a.data["datawrapper-height"][t]+"px"}}}))}();</script>