Feather Take Home Assessment

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.

This coding challenge applies to frontend, backend, and full-stack roles. Depending on the position you are applying for, you can focus on your specific area.

You can spend as little or as much time as you like on this project. We've added some initial boilerplate to help you get started, but feel free to refactor every part of this app as you may seem fit.

Start by reading the Engineering challenge for the position you've applied for and don't forget about 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.

Engineering challenge

We've prepared several different user stories to work on. Depending on what position you applied to, pick one of them:

Task requirements

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

Getting started

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:

cd backend
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.

API

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.

Data structure

Policy

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

Customer

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

InsuranceType can be of LIABILITY, HOUSEHOLD, HEALTH

PolicyStatus

PolicyStatus can be of ACTIVE, PENDING, CANCELLED and DROPPED_OUT

General questions

How much time did you spend working on the solution?

Around 20 hours divided in small periods along the days.
What’s the part of the solution you are most proud of?

I think I could keep the ui feeling in the additions I made, also, I made a great improvement in the resposiveness and the accessibility of the code.

Besides that I could implement the React 18 to the project. It was a bit challenging once there is some things not working properly on React 18v yet, but it was nice to make those changes and updates.
If you had more time, what other things you would like to do? I think I would create more filters, to filter more than names and also I would make more tests.
Do you have any feedback regarding this coding challenge?
I loved that everything is based on docker so, at least for me that use docker everyday it was really quick and easy to set the envirorment.

I also think that the proposal was fair, I really enjoying answer this test.

ingridbgr/engineer-challenge