Developer role · technical exercise

One ticket, one hour

Below is a short brief on our systems and then a problem to work through. Write up how you would handle it, on this page, within the hour. There is no model answer and nothing to install - we are interested in how you think, not in catching you out.

How this works - read this before you start

  • You have 60 minutes. The clock starts when you press Start. It cannot be paused, and reloading or closing the page does not stop it.
  • The time left sits in the top corner the whole way through. It turns red for the last ten minutes.
  • There are three parts, opened one at a time. You see part one first. When you finish a part you submit it and move on to the next, and confirm each time. A submitted part is locked - you cannot go back and edit it, and you cannot see the next part until you do. As a rough guide: 25 minutes, 20 minutes, 10 minutes.
  • Your answers are sent to us automatically when the clock reaches zero. Whatever is typed on this page at that moment is what we receive. Once you reach part three you can also submit early. Either way, once it is sent it is final.
  • Type your answers into this page. It saves on your own device as you type, so a reload will not lose your work. If you prefer to draft somewhere else, paste it in before the time runs out - only what is on this page gets sent.
  • Right-click, copying the brief and printing are switched off. We are after your thinking, not a chatbot's. Yes, there are ways around that. We would rather you spent the minutes on the ticket.
  • Use a laptop or desktop with a steady connection, and stay in the same browser for the hour. We can see when you started and how long you spent on each part.

So we know whose answers these are.