Show Us Your Code and Get Hired

Developers all over the world have found the perfect job by showing us their code. Everyone can create a resume, but great developers can build projects. Your task will be to build projects at the HackRocket Hackathon for amazing opportunities, cash prizes, and a promising jobs. This is our exclusive event with AthenaSquare and Shiprocket as our partners after the earlier ones saw massive participation and success.



Schedule

  • 24th march 2022 end

    Registration

    Team must register themselves during this time interval on DevFolio

  • 25th march 2022

    Release Problem Statement and Idea Submission

    Team E-Cell will release the problem statements.

    Team members must choose any one problem statement and must submit an idea based on the given theme.

    Idea Submission is optional but will certainly provide you with extra credits during the shortlisting round and you'll be eligible for "MOST INNOVATIVE SOLUTIONS" prize.

    Accepted responses – PPT, Video, Animation etc. (only one)

  • 25th march 2022

    Join Our Discord Server

    All the teams registered must join our discord server Click Here to participate in our hackathon.

    On joining, the team leader must fill the team registration form to confirm your attendance in HackRocket

    For all further info please refer our website/discord

  • 25th march 2022 (12 PM)

    Welcome Meet

    Welcome Meet hosted by E-Cell Team Members explaining rules and regulations about the hackathon.

    The team leader must initialize an empty git repository and add all its team members and E-Cell NITB (ecellnitb) as a collaborator

  • 25th march 2022 (5 PM)

    Release Problem Statements

    Team E-Cell will release its problem statement for the hackathon. The team members have to select the problem statements and start building a prototype over it.

  • 26th march (12 AM) to 28th march 2022 (11.59 PM)

    Hackathon

    Team Leads have to submit the problem statement they selected on a google form circulated.

    Participants will be given 2 days of time to design a prototype as desired for given problem.

    After every 12 hours, a new google form will be circulated in which the team members (any one) can post the update of their project.

    After 48 hours, a google form will be circulated. This form will be filled by team leaders who have completed the prototype and are ready for pitching infront of our judges panel.

  • 31th march 2022

    Result Announced

    Final verdict of Hackathon will be announced

Rules and guidlines

  1. The problem statements will be released on the 25th march after the event briefing round at noon.
  2. Every team must create an empty git repository and add all its team members as collaborators along with E-Cell [ecellnitb]. All team members can only push their code to this repository
  3. At 5PM, Team Leads have to submit the problem statement they selected on a google form circulated
  4. After every 12 hours, a new google form will be circulated in which the team members (any one) can post the update of their project.
  5. After 48 hours, a google form will be circulated. This form will be filled by team leaders who have completed the prototype and are ready for pitching infront of our judges panel.
  6. Teams can take help from the internet/previous project if they are stuck, but they must use their creativity and skills to develop a unique solution.
  7. Teams can use any framework or library at their convenience.
  8. Plagiarism is strictly prohibited; the solution of all teams will be strictly monitored, and if found to be copied from other teams or a complete solution from the internet, they will be immediately disqualified.
  9. After completing the project, it must be live (it must be hosted on the internet and can use GitHub Pages or Heroku or any free cloud services).
  10. Teams must update their status of projects every 12 hrs in a google form. If they fail to do so, they will be contacted by Event Coordinators. If any team remains inactive for more than 12 hrs, the team will be disqualified/eliminated.
  11. Teams must stop hacking once the time is up. If you find a bug that breaks your application during demoing your hack and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.
  12. Teams can be disqualified from the competition at the organizers' discretion. Reasons might include but are not limited to breaking the Competition Rules, breaking the Code of Conduct, or other unsporting behaviour.
  13. Every team can only ask for a mentor's guidance 3 times every 6 hours. This number will not be carry-forward to the next 6 hours.
  14. After the hacking round, every team has to record a video of the working prototype and upload it on the google form provided. The team will be given additional 2 hours for the task mentioned above apart from the 48 hours of the hackathon. The video has a maximum duration limit of 3 minutes.
  15. Out of the total submissions, only 30 teams (subject to change) with the best prototypes will be allowed to pitch on 26 and 28th march.
  16. Project violating the code of conduct will result in instant disqualification.

Evaluation Criteria

  • Economic, Environmental and Social Impact
  • Value Proposition
  • Problem-Solving
  • Clear Walkthrough of Solution with Technicalities
  • Vision and Team
  • Features
  • Presentation
  • Personal Experience of the Mentors/Judges
  • UI & UX
  • Innovation and Creativity
  • Opportunities and Barriers in the Market
  • Scalability
  • sponsor

    meet our sponsors/partners

    E-Cell NIT-B sincerely appreciates your support for our mission to incline the nation towards an entrepreneurial India.

    subscribe our newsletter

    Sign up to get the first-mover advantage on all announcements and updates on the events by E-Cell NIT-B..

    -->