Part of BPUT Hackathon 2026

CAMPUSLINK: Placement Season Without the Spreadsheet Tandav banner

Rooman Technologies

Open · Closed 21 Sept 2026

CAMPUSLINK: Placement Season Without the Spreadsheet Tandav

Two thousand students, three hundred recruiters, forty drives, and one Excel file that everyone is afraid to touch.

Registration closed

21 Sept 2026

Team size

3–6 members

Rounds

2 rounds

Mode

In person

Venue

Bhubaneswar and Rourkela

Registration closed

Already registered? Sign in

Role
AI / Full-Stack Engineer
Format
Evaluation only
Prize
₹60,000
Deadline
Closed 21 Sept 2026
Registered
467

Evaluation only · Open

Design and develop an AI-powered Campus-to-Corporate Placement Management System that manages student readiness, matches students to recruiter requirements, schedules placement drives without collisions, and generates actionable placement analytics in near real time.

Overview

Outcomes

  • Every student with a single, continuously updated readiness profile and a clear skill-gap picture
  • Recruiters receiving well-matched, pre-screened candidate pools with explainable ranking
  • Drives scheduled without clashes, double-booked venues, or students shortlisted in two places at once
  • Offer, documentation and joining status tracked in one place through to joining
  • Placement cells with real analytics: what converts, who is at risk, which recruiters come back

Overview Placement cells manage thousands of students, hundreds of recruiters and dozens of overlapping drives every season — mostly on scattered spreadsheets, email chains, WhatsApp groups and manual shortlisting. The result is duplicated effort, missed deadlines and inconsistent communication. Students have no single readiness profile, no skill-gap analysis and no guidance on which roles fit them. Recruiters struggle to receive well-matched candidate pools. Drives clash, offers and joining statuses are tracked by hand, and nobody has data on which branches, skills or preparation efforts actually convert into offers. The Story It is the second week of placement season. The placement officer has four browser tabs of the same spreadsheet open, because three people are editing it. A company is coming Thursday, but so is another company, to the same seminar hall, at the same hour. Eleven students are shortlisted for both. One student who is a genuinely excellent fit was filtered out by a CGPA cell that was formatted as text. The offer letter from last week is in somebody's personal inbox. Fix the season.

Problem statement

  • The system should use AI, machine learning, NLP, recommendation systems or generative AI to analyse student profiles, recruiter requirements and historical placement data. It should not merely digitise records — it should provide student readiness and employability scoring, skill-gap analysis against target roles, recruiter-student matching and ranking, conflict-free drive scheduling, offer and documentation tracking, and predictive analytics on placement outcomes
  • Student readiness profiling built from resumes, academic records, certifications, projects, aptitude and mock-interview scores, communication and soft-skill assessments, branch, CGPA and backlog history — surfacing skill gaps and low readiness before a student reaches a recruiter
  • Recruiter requirement matching by parsing job descriptions and eligibility criteria, then scoring candidates on skill and stack fit, branch and CGPA eligibility, certification and project relevance, and past interview performance, with a fit score and stated reasons for inclusion or exclusion
  • Drive scheduling and conflict management covering overlapping drives, venue and resource double-booking, students shortlisted for simultaneous drives, and panel and infrastructure availability
  • Offer and documentation tracking across offer letters and CTC, bonds, verification status, PPOs and internship conversions, and offer acceptance, deferral or withdrawal
  • Analytics and predictive insight on branch-wise and skill-wise conversion, salary and package trends, students at risk of remaining unplaced, and recruiter engagement and repeat hiring
  • Communication automation replacing manual email and WhatsApp coordination for shortlists, schedules, document deadlines, offer updates and drive announcements
  • Readiness scoring and explainability: assign each student-recruiter pairing a level such as Not Ready → Developing → Ready → Highly Employable, and explain the major factors. Instead of "Not Shortlisted", the system should say something like: below threshold, because CGPA meets eligibility but the required skill set shows a gap in cloud technologies and the mock-interview score sits under the recruiter's benchmark. Recruiter-side rankings should be explained the same way
  • Workflow automation may include: auto-scheduling around detected conflicts, auto-shortlisting on eligibility and fit score, personalised preparation recommendations, automated documentation reminders, escalation of at-risk students to mentors, and recruiter follow-up prompts on pending offers
  • Innovation opportunities: generative-AI-assisted resume and profile building, AI mock interviews and communication analysis, a chatbot eligibility assistant, predictive at-risk identification, embedding or vector-search based matching, explainable shortlisting, real-time conflict detection, blockchain-based offer verification, job-portal API integration, gamified preparation, mobile alerts and multi-campus analytics aggregation
  • Minimum expected prototype: demonstrate at least three core capabilities — preferably one covering readiness profiling and skill-gap analysis, one covering recruiter-student matching and drive scheduling, and one covering analytics, predictive insight and offer tracking — running the chain of profiling, matching, scheduling, notification, offer tracking and analytics

For the Grand Finale, your build should include:

  • A working prototype with a student readiness and employability scoring mechanism, including skill-gap analysis
  • Recruiter-student matching demonstrated across at least three simulated drives, with explainable shortlisting output and fit scores
  • A conflict-aware drive scheduling mechanism plus automated notification workflow
  • A placement monitoring dashboard with offer and documentation tracking, conversion rates, package trends and at-risk student identification
  • Technical documentation: system architecture, models and algorithms used, accuracy and performance evaluation of matching and scoring on simulated or public datasets, and the multi-campus scalability and deployment approach

The Grand Finale is judged on:

  • Quality of readiness profiling, skill-gap analysis and employability scoring — 25%
  • Accuracy and explainability of recruiter-student matching and ranking — 25%
  • Conflict-aware scheduling, notification and offer/documentation workflow — 20%
  • Analytics and predictive insight, including at-risk student identification — 20%
  • Architecture, scalability across campuses and demo quality — 10%

Rounds

This challenge runs in 2 rounds. You enter once, and the same entry carries through.

  1. Mid evaluation

    Being judged
    • In person · Bhubaneswar and Rourkela
    • Submit by 13 Oct, 7:45 pm IST
    • 8 deliverables to submit
    • The top 5 move on to Grand Finale
  2. Grand Finale

    Coming up
    • In person · BPUT, Rourkela
    • Submission dates to be announced
    • 5 deliverables to submit
    • The final round. Results are decided here

Deliverables: Mid evaluation

  • Your idea in one line

    One or two sentences a judge can read in ten seconds: what you are building and who it is for.

  • What will be working by the finale?

    The parts you commit to having running at the Grand Finale, most important first.

  • Tech stack and hardware you plan to use

    Languages, frameworks, models, boards and sensors, and anything you still need to get hold of.

  • A diagram, sketch or mock-up of your idea

    One image that shows how it works: an architecture diagram, a wireframe, or a photo of a sketch. Put anything more in your deck.

  • What have you built or tested so far?

    Optional. Anything already running, measured or prototyped, even if it is rough.

  • Pitch deck (PDF)

    Optional. Export your slides as a PDF. Judges read it on the page, next to your answers.

  • GitHub repository

    A link to your code, if you have some yet.

  • Demo video

    A YouTube, Loom or Google Drive link to a short demo, if you have one. Make sure anyone with the link can watch it.

Deliverables: Grand Finale

  • A working prototype with a student readiness and employability scoring mechanism, including skill-gap analysis
  • Recruiter-student matching demonstrated across at least three simulated drives, with explainable shortlisting output and fit scores
  • A conflict-aware drive scheduling mechanism plus automated notification workflow
  • A placement monitoring dashboard with offer and documentation tracking, conversion rates, package trends and at-risk student identification
  • Technical documentation: system architecture, models and algorithms used, accuracy and performance evaluation of matching and scoring on simulated or public datasets, and the multi-campus scalability and deployment approach

Evaluation criteria

  • 15% Problem Understanding & Relevance
  • 20% Innovation & Creativity
  • 20% Solution Approach & Technical Depth
  • 25% Prototype / Implementation & Feasibility
  • 10% Impact, Usability & Sustainability
  • 10% Presentation & Demonstration

Questions & answers

0/500

  • When our result will be out

    PIYUSH KUMAR DEY · 15 Oct 2026, 12:16 pm

    Awaiting a response

More challenges to enter

Prizes are offered and awarded by Rooman Technologies, not by Wooble. Amounts shown are as stated by the host and may include the host’s own valuation of non-cash items. Who places, how and when a prize is paid, and any tax or deduction, are between the winner and the host. A challenge may close, change or be withdrawn before results are declared.