Welcome to the Utility Warehouse Front-End Take-Home Challenge! 💜,🚀
We’re thrilled you're interested in joining our Insurance team — where we help protect what matters most to our customers.
This take-home exercise is simple and short on purpose, as it's just meant to be a foundation for us to work on together during the technical assessment call, and also give you a taste of the kind of work we do. It’s not just about writing code, but also something you’d be happy to discuss with your teammates.
Imagine you’ve just joined the Insurance squad, and your first ticket is to build the initial version of a Claims Handling Form. This form will be used internally (by our support agents or possibly customers in the future) to log insurance claims.
You’ll build a simple web app that collects the following information:
- Claim date – when the incident occurred
- Category – e.g. theft, accidental damage, loss, etc.
- Description – a free-text field where users can describe what happened
Build a form that collects the three fields above. You should use React, as it's the framework we use in UW 💜. Focus on functionality, simplicity but not visuals — styling can be minimal.
Here’s a rough layout for inspiration:
Set up a small Node.js server with a single POST endpoint that:
- Receives the form data
- Writes it to a file (e.g.
claims.log)
No need for a database or authentication — we just want to see how you'd structure a simple API.
- Basic form validation
- Error handling (client + server)
- Having a11y in mind
- A clear
README.mdwith setup instructions - Thoughtful project structure and separation of concerns
- A solid understanding of JavaScript and the surrounding Front-end tech.
- Clean, readable code with clear separation of concerns
- A simple but working full-stack flow from form submission to file output
We’re not expecting production-ready polish — just something that shows us how you approach problems, write code, and put things together. Most people spend around 1–1.5 hours on this.
When submitting your code, please share your private Github or similar repo with us by using the @ktzar Github handle. If you are not familiar with this, you can send us a zip file, but we'd prefer to see your repo's Git history. If you have any questions or need clarification, feel free to reach out.
Good luck — we’re excited to see what you build!