Take-Home Task Review

What they ask

The loop is three steps and candidates describe it as conversational rather than stressful: an HR phone screen, then a task sent by email, then a technical interview that reviews the task and your background, and finally an open discussion with a manager about mindset. Test automation roles are rated the hardest; software engineer roles the easiest.

The task depends on the track. For frontend it is a small React feature (a list with filtering, a form with validation, or a page consuming a public API) with attention to state, loading and error states. For backend it is a small Laravel or Node service with a couple of endpoints, a relational model and tests. In both cases the review call, not the task, is where the decision is made.

What the review covers:

• Walk us through the structure. Why these folders, components or layers?
• Which decision are you least happy with, and what would you change with another day?
• How did you test it, and what did you decide not to test?
• Where would this break if the data grew a hundred times?
• Something from your background that relates: a similar problem in a past project.

What they look for

Ownership of the decisions in the code, honesty about shortcuts, clean commits and a README that runs. They are an agency working with many clients, so they also listen for how you explain technical choices to a non-technical person.