π₯ Roast My Pick Β· SIH26044
Portal for Academia - Industry collaboration for Skill Mapping, Internships and Placement
Ministry of Ayush
Bold. Let us find out precisely how bold, in the order a panel will find out.
Proceed with caution. This is the most-built student project in the country with no domain angle to rescue it, so unless you ground the whole thing in NSQF competency standards and verifiable credentials, expect to present something the panel has already seen several times that day. Roughly 160β360 teams are expected to go here.
The receipts
Every red flag on this statement, in full. These are the four places it bites.
Exhibit A
Placement portals are the single most cloned student project in India and this will be compared against a long memory of near-identical submissions
It gets worse
The skill assessment measures against nothing unless you supply a competency framework, and a questionnaire that scores students on categories you invented produces gap analysis that means nothing
Still reading?
The sponsoring institution is an Ayurveda institute and the statement has no connection to Ayurveda at all, so you cannot even lean on domain specificity to differentiate
And the finisher
Three user types and ten feature areas with no stated priority means the realistic outcome is a working student flow and two stub portals
The damage report
Every score this statement earned, and what each one actually costs you.
Feasibility
4/5Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.
The whole thing is standard application work β assessments, profiles, listings, a matching function and dashboards β with no data or hardware dependency, though the competency framework that gives the skill gaps any meaning has to be assembled from published occupational standards rather than invented.
Innovation scope
1/5Nothing here is new. Your only edge is execution β and execution is also everyone else's only edge.
The statement enumerates the student, internship and placement functionality in three exhaustive sections plus a platform features list, and this is additionally the single most frequently built student software project in the country, so there is essentially nothing conceptually unoccupied here.
Clarity
4/5The ask is unambiguous, which quietly removes your favourite excuse.
The feature list is long and unambiguous across all three user types, though it never says what the skill assessment measures against, and without a defined competency framework the gap analysis at the heart of the product has no reference point.
Acceptance potential
1/5The numbers do not like you. Bring something the numbers cannot see.
Placement and skill-matching portals are the most cloned category of student project in India by a wide margin, judges have seen them in every cycle, and the portal is additionally an odd fit for an Ayurveda institute as sponsor, which means even the domain framing gives you nothing to work with.
Effort
MassiveA semester of work wearing a hackathon costume. Something is getting cut; decide what now, not in week five.
Assessment engine, skill profiling, recommendation, student portfolio, internship portal, placement portal, faculty opportunities module, institutional analytics, document management and integrations across three user types is a very large surface area with no natural core.
Demo-ability
MediumDemoable, if you rehearse it. Nobody rehearses it.
An assessment producing a gap analysis and a match is showable and works, but every judge has seen a recommendation list before and there is no moment here that surprises anyone.
Data
None suppliedNo dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.
Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.
The demo they will have already seen
Somewhere around 160β360 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly β you have built predictably, which costs exactly the same and hurts more.
What survives
The ground worth standing on when the questions start.
- Anchoring the skill taxonomy to the National Skills Qualifications Framework and published National Occupational Standards would give the gap analysis a real reference point, which is the one move that separates a serious submission here from the many superficial ones
- Zero technical risk means a team will certainly finish, which matters if a working submission is the goal
- Verifiable credentials for the student portfolio β cryptographically signed rather than self-declared β is a genuine and underused angle in a category where everyone else lets students type their own achievements
None of that means do not pick it. It means do not walk into that room having heard any of this for the first time from a judge.
The framing is a joke. The findings are not β they are the same analysis on the statement page, and every line above is attached to a score or a fact in the record. It is one opinion with its reasoning attached, so argue with it before you trust it.