Innovative Refrigeration Systems Junior Software Developer interview questions

For this challenge, you will be creating a web application to assist Acme Widgets, Inc. with recording Job Hazard Analysis. This challenge is meant to be open-ended and should not be “tricky” by any means - so please reach out if you have any questions. What is Job Hazard Analysis? A JHA (sometimes called a JSA) is used by EHS professionals to record hazards that exist in the workplace as they correspond to specific tasks a worker would perform. It’s often helpful to see a real life example of a process like this. Here is the public portal describing the University of Washington’s JHA process from their risk management team. The docx template found there may be helpful as well. The Problem Acme Widgets is frustrated with their JHA’s being on paper, and are looking for a paperless solution and have turned to you to digitize their JHA process. Create a web-based recordkeeping application to assist them with keeping an online database of JHAs. Technical Requirements ● Build a JHA web application! It should: ○ Allow a user to Create / View / Update / Delete a JHA as well as List existing JHA’s. ○ A JHA should have at least some top-level metadata like Title and Author ■ As a user I can add job steps to the JHA ■ With every recorded Step taken to complete the Job, Hazards should be listed with their appropriate controls to mitigate the associated risks involved with performing the Step. ● Build your web application as a Single Page Application, with a back-end API. ● You may use any language or framework to build your back-end API except Node/Javascript. ● Use a RDBMS such as MySQL, Postgres, or SQLite for persistent storage. ● (Optional) Use a CSS framework like Tailwind or Bulma to beautify your front-end UI ● (Optional) Use a JS framework like VueJS or React on the front-end ● (Optional) Allow the user to upload photos to job steps Notes This challenge is left open-ended by design, have fun with it! Please include a readme that illustrates the steps to run your submission. We have to be able to run your submission to review it. Be prepared to demonstrate usage of your application and discuss both your code and decision making. Please ensure your submission includes enough quality code for our team to evaluate your abilities! Note: While we want you to wow us with what you can do, adding functionality like user authentication, permissions, etc is not expected or necessary.