HACK&GROW With Magnit

• The theme for Hack&Grow this time is Innovate for the Evolution of Work, where participating developers will be required to design a web application for monitoring employee levels of happiness and satisfaction, for employers to identify the area of improvement and fill the gap for their employees.
• The detailed problem statement will be published and sent to all registered participants via email on 16th January.

• Problem statement:
• A new trend is sweeping across businesses: monitoring employee levels of happiness and satisfaction, which help them to identify the area of improvement and fill the gap between employers and employees. Companies are monitoring how employees feel at work by deploying software. To achieve this goal companies ask employees formal and informal questions.
• Design the web application which prompts a series of questions through UI, and based on the answer the application generates relevant reports to showcase the employee happiness/satisfaction index (e.g. when is the employee most happy during the week/day or the employee is sad/happy because of work or something personal).
• The application should be dynamic as much as possible instead of static content (avoid emoticons and use input elements).
• Answers should be captured in different formats along with the plain text.

Step 1: Registration - All interested participants should register for Hack&Grow on WeAce.

Step 2: Confirm Participation - All participants who register for Hack&Grow will receive a call from the organising team to confirm their participation and answer a few questions to complete their registration . It is mandatory to complete this step.

Step 3: Join Slack Channel - link to be shared via email.

Step 4: Attend Speaker Session.

Step 5: Start Hacking!!

Before participating, you can review detailed description for the role Hack&Grow is hiring for here:

• Full stack Developer – SSE

• Registration Begins - 9th January
• Registration Closes - 17th January
• Dates for Coding - 19th to 20th January
• Coding Check-in Update- 19th January, 11:59 PM
• Submission Deadline - 20th January, 11:59 PM
• Shortlisted Entries will be screened on their solution via personal interviews by Jury Members - 10th February
• Roll out of offers to winning participants - 17th February

• Only individuals can participate. No teams.
• In the spirit of fairness, we request you to start coding on the dates of the event, i.e., 19th and 20th January.
• All participants have to submit the code check-in form to confirm their participation by 19th January 11:59 PM.
• The code submitted has to be designed/developed by the registered participant. Participants may be questioned on every line of code.
• All entries have to be submitted latest by 20th January 11:59 PM via a form sent to you by email.
• All original ideas are welcome as long as they are in line with the theme of the Hack&Grow. Please avoid plagiarism.
• Once the code is complete, it has to be uploaded to github. A form link to submit this will be sent via email. After the hackathon, shortlisted participants will get individual time to present their solutions to the jury members.
• Participants can be disqualified based on organiser’s discretion, for breaking rules, and not respecting the judges/jury/mentors.
• Participants have to submit all components required: Refer to the Submission Guidelines for the same.

• Only Java can be used to develop the code however you can use any IDE of your choice.
• You are permitted to use publicly developed and openly licensed APIs and SDKs for your project.
• Any intellectual property developed during and within the scope of the hackathon must be open source.
• The license selected by the team must be clearly listed in code (page per page) or a generic page announcing the license the application adheres to. The public code used inside your application should also list the licenses the code is subjected to.
• You can use multiple licenses in the application. For example, the public code used could be licensed under the Apache license agreement whereas the code written by the team for the application licensed under the MIT license agreement.

• Who will own the Intellectual Property Rights to my final product?
  • It is yours. You are the solution creator, and you will have all rights and own the IP of the product. However, all code needs to be shared, as these are to be evaluated by the jury panel.
• Does one have to be online and available for the entire duration of the challenge?
  • You have the flexibility to work as per your convenience. We expect solutions to be submitted within the mentioned time frame. You do not have to join any live zoom link or be online on any platform during the Hackathon.
• Do we need the entire idea completely working?
  • The jury will need to see a solution that can be evaluated to establish the feasibility of the solution. Therefore, try to work towards the logical representation of the solution and define the problem statement as clearly as you can. The more complete it is, the better the jury can evaluate.
• What should the idea be based upon?
  • A. We welcome original ideas as long as they are in line with the theme of the Hackathon. Please avoid plagiarism. You may use the code that is open sourced and publicly available.
• How long should the code be?
  • A. The idea is to finish the hackathon application with the least number of lines of code you can manage. As long as the code solves the purpose, the length of code does not matter.
• What will I get for participation?
  • All participants will receive a participation certificate for being a part of Hack&Grow.

Please state clearly the below points while submitting the project.

• Submission name: The name for your solution in five words or less.
• Long description: Describe your solution in 500 words or less.
• Short abstract of the project.
• The platform and development tools used to build the project.
• SDKs, APIs, assets and libraries used in the project.
• Any components not created at the hackathon.
• A Link to GitHub code repository. You can provide additional description and diagrams here.
• Link to a three-minute demo video. Record a demo of your project, upload it to YouTube or Vimeo, and share the URL. Alternatively, participants may submit a presentation explaining their code and submission.