For this challenge you will be creating highly simplified version of the Tanda web app from scratch using Ruby on Rails. This is a Ruby on Rails challenge, so you don't need to worry about design too much. You should use Git as you build your solution. For submission you are asked to push your repo to GitHub and provide us with the link and any necessary instructions.
It is recommended to use Ruby on Rails (.erb / .haml for the view files) (https://guides.rubyonrails.org/layouts_and_rendering.html) when building out the front-end for your project, but using a different framework like React or Vue is also allowed. Experimenting with Hotwire on Rails is also very much recommended (see the "Optional exercises" section).
Please also provide a README file with the instructions needed to clone your project, install any dependencies, and run the app.
Your app is to have three models: users, organisations, and shifts. Your database should closely resemble the following entity-relationship diagram:
Figure 1:
The following illustrations should only serve as an example. You do not need to follow the designs presented below. You can split functionality out to other pages. Just make sure it is all there.
An unauthenticated user should first be prompted to log in, sign up, or reset their password:
Figure 2:
As per Figure 1, users have names, so "Name" should be a field on your sign up page.
Figure 3:
After signing up, users will not belong to an organisation, so when they log in for the first time, they should be prompted to join an organisation (or create a new one).
Figure 4:
Users should be able to edit all organisations (i.e. their names and their hourly rates).
Figure 5:
Once a user has joined an organisation, the home page should change to become an overview of actions for that organisation: viewing shifts, editing the organisation, or leaving the organisation.
Figure 6:
Leaving an organisation should return the user to the state they are in just after they sign up, i.e. not belonging to any organisations. The departed user's shifts should be deleted.
Finally, the shift page should show all shifts that belong to the user and their fellow employees at their organisation.
Figure 7:
A few things to note:
- The hourly rate at Bob's Burgers in Figure 7 is $10/h.
- Your table should include all the columns in Figure 7, and should be ordered with the most recent shifts listed first.
- Breaks are considered unpaid and are thus subtracted from
shift lengthto determinehours worked(which in turn determinesshift cost):shift length = finish time – start time hours worked = shift length - break length in hours shift cost = hours worked * organisation hourly rateshift lengthdoesn't need to be displayed in the table, buthours workedandshift costdo. - You will need to incorporate a way of creating a new shift for the user that is logged in. As with everything else, you don't need to copy the way it was done in the screenshot above.
- As per Figure 1, shift date and start time are to be stored in the same database column. Separating the two (and joining them together when you create a shift) is an exercise left to the reader.
Here are some optional exercises for you to do. We recommend that you try at least one of them. They are all mutually compatible, so you could do all of them. Some will require changes to the structure of the database.
Allow users to change their own name, email address, or password.
Allow users to modify or delete existing shifts.
Create a way for shifts of a departed employee to be stored. Create a link on the "View Shifts" route that would direct a user to a table of prior employees shifts. You may need to make schema changes for this exercise. Bonus: If a departed employee re-joins the organisation, have a way for their past shifts to be re-added to current shifts.
Allow users to filter which shifts are visible based on employee or a date range or both.
When creating a shift, if the finish time of a shift is earlier than the start time, the shift should be considered overnight. For example, if the start time is 7:30pm and the finish time is 1:30am, then it is an overnight shift that goes for 6 hours.
The hourly rate should be doubled for shifts worked on a Sunday. If you do exercise (4) then you will need to account for overnight shifts in the following manner: The 2x should only apply to the hours worked on Sunday. For the sake of simplicity, subtract the break length from the end of the shift. For example:
| start | finish | break length | shift cost (assuming $10 hourly rate) |
|---|---|---|---|
| 10pm Sunday | 3am Monday | 1 hour | $60 (5h at work – 1h break = 2h worked on Sunday and 2h worked on Monday) |
| 5pm Sunday | 2am Monday | 2 hours | $140 (9h at work – 2h break = 7h worked on Sunday) |
| 9pm Sunday | 1am Monday | 2 hours | $40 (4h at work – 2h break = 2h worked on Sunday) |
People often take more than one break when they work. For this exercise, instead of a shift having a single break length, it could have multiple. The sum of all these should be taken into account when calculating hours worked and shift cost.
Some people have 2+ jobs. Extend organisation functionality to allow users to belong to more than one organisation. You will need to rethink the shifts model. Shifts currently belong to a user (who belongs to a single organisation). If there are multiple organisations involved, this falls apart, because you don't know which organisation the user worked the shift at.
Hotwire is a Ruby on Rails front-end framework that allows for partial page reloads, handling of front-end DOM actions, and much more. You can learn more about it here: https://hotwired.dev/. Experiment with the framework and see if you can add a turbo frame or a Stimulus controller to your project!
Adding tests is a good idea. We don't mandate that you write any for this challenge, but feel free to go ahead and write some tests for your code.
It is possible to build a solution to this challenge without writing a line of JS. However, a solution that used some would be more exciting. Here are some ideas:
- A datepicker for the shift date field
- Using Ajax to create shifts
- Sorting by column
Feel free to add a feature of your own devising. You're more than welcome to sign up for a trial Tanda account to look for inspiration.
You will be judged on the the appropriate use of database constraints, your choice of data types, working data validation, the general quality of your Ruby code, and how closely your solution matches this spec. Be a show off! Impress us with your strong command of relational databases and idiomatic Ruby on Rails.