1. Plans a date in a calendar for a phone call with an internal recruiter.
2. Fifteen-minute conversation with the recruiter (the screening).
3. You get sent a test on the site HackerRank to be completed in 90 minutes (5 questions).

Based on my first experience with HackerRank, I've now decided to boycott any company that uses HackerRank. Reasons:

• The interface is absolutely horrendous, very difficult to work with.
• None of the questions are tailored to a frontend developer (as if written by a backend dev and an attempt is made to keep it as generic as possible) and using wrong wording (e.g., generic coding terminology that could mean anything in JavaScript).
• Someone who just came out of school could possibly pass this with ease, but someone who has been working for a while would not (I've been a dev for 15 years, a technical lead). The questions are very reminiscent of the questions we used to get in university (very unpractical, tailored to applying mathematics in coding, rather than coding itself).

Question (1/5): We have a robot that can pick up blocks from a stash, move them horizontally, and lower them in place. There are 10 positions available to lower blocks, numbered from 0 to 9. Each position can hold up to 15 blocks.

[Two diagrams with the hexidecimal axis of x-axis [0-9], and y-axis [1-F] and arbitrary placement of blocks in diagram]

The robot understands the commands 'P', 'M' and 'L':

• P: Pickup from the stash and move to position 0
• M: Move to the next position
• L: Lower the block

The robot is safe to operate and very forgiving:

• There are always blocks in the stash (Pickup will always get a block).
• If the robot already holds a block, Pickup will reset the robot to position 0.
• The robot will not go beyond position 9. Trying to Move it further does nothing.
• Lowering a block on a pile of 15 blocks does nothing (and the robot will keep any block it holds).
• Lowering without a block does nothing.
• The robot ignores any command that is not 'P', 'M' or 'L'

Implement a function that takes a [String] of commands for the robot. The function should output a [String] representing the number of blocks (in hexadecimal) at each position after running all the commands.

This all has to be implemented in an input field below it with random data coming from the backend.