Thank you for applying at Feather and taking the time to do this home assessment.
The goal of this project is to let you show off your coding and problem-solving skills, on a task that resembles the kind of work you’ll be doing with us.
Depending on the position you are applying, you can focus more on the frontend or backend part of the application (or both if you are applying for a fullstack position).
You can spend as little or as much time as you like on this project. We've generated some boilerplate for you to get started.
- Start by reading the User story and the Acceptance criteria to have a clear idea of the requirements.
- Use the Getting started guide to set up a local version of the project on your machine.
- Take a look at the Data structure and API to know what the data looks like.
- Finish by answering a couple of questions about the project. You can answer them on this very same file.
As a user, I want to be able to search for policies using any of the text fields displayed on the table.
When a search filter is applied, I want to see the filtered information on the same table.
When a search filter is applied, I want to be able to clear the current search filter, this action will display the original information.
- Show only
ACTIVE
andPENDING
policies. - Do not display any results if there are no matches
- Clearing the search should return the table to its original state
- Make sure your feature works as expected
- Your code is easy to understand and follows best practices
- The project runs with one command, and without any external configuration
- Your code has tests to make sure the functionalities work as expected
- Make sure you have Docker installed on your machine
- Set up the environment variables
cp ./backend/.env.example ./backend/.env
- Build and run the Docker image:
cd backend
docker-compose build
docker-compose up
- On a new terminal, run the migration and the seed script to add initial data:
docker compose exec backend yarn prisma migrate dev
docker compose exec backend yarn prisma db seed
- That’s it!
You can see the app on http://localhost:3000
The API should be running on http://localhost:4000
** Note ** If you want to install new dependencies, you'll have to do it inside the docker container. To do that, you can use the following command:
docker compose exec {backend OR frontend} yarn add {the_name_of_the_package}
Make sure to replace the values between the curly braces {}
with the correct ones.
After following the Getting started guide, the backend should be running on port 4000
. The backend currently have one endpoint:
Request type | Path | Query Params | Example |
---|---|---|---|
GET |
/policies |
search |
/policies?search=BARMER |
Feel free to update or add more endpoints to accommodate or improve your solution.
fields | type | comment |
---|---|---|
id | string | Used to identify the policy |
customer | Customer | Object holding the customer's informations |
provider | string | Name of the provider (Allianz, AXA…) |
insuranceType | InsuranceType | Type of the insurance (Liability, Household…) |
status | PolicyStatus | Status of the insurance (Active, Cancelled) |
startDate | date | Date when the policy should start |
endDate | date | Date when the policy ends |
createdAt | date | Date when the record was created |
fields | type | comment |
---|---|---|
id | uuid | Used to identify the customer |
firstName | string | Customer’s first name |
lastName | string | Customer’s last name |
dateOfBirth | date | Customer’s date of birth |
InsuranceType
can be of LIABILITY
, HOUSEHOLD
, HEALTH
PolicyStatus
can be of ACTIVE
, PENDING
, CANCELLED
and DROPPED_OUT
-
How much time did you spend working on the solution?
-
What’s the part of the solution you are most proud of?
You can share a code snippet here if you feel like it
-
If you had more time, what other things you would like to do?
-
Is there anything you would like to change in the current setup?