Introduction words: this challenge might seem a bit overwhelming at first sight, yet the reason why the description page is so long, is because it's just well documented with a lot of context. We're a Startup, we want to move fast, we want to take a lot of small decisions to go in the right direction. This is only possible through trusting and empowering everyone and thus by giving as much context as possible to take smart decisions. Use this context to decide what to do and what not to do. Don't hesitate to ask questions if you need extra information.
This challenge aims at making sure that we've got an understanding of your design implementation and technical level. There is no perfect answer, and we'll be pleased to hear how and why you came to the solution you propose. There are however wrong answers (the ones that do not meet the specifications).
The coding is important, yet not the most relevant part of the challenge. The choices you make and the decisions in terms of design, coding structure and architecture are what we'll be really focusing on.
<aside> 🚀 Your mission, shall you choose to accept it, is to create the frontend quote presentation and cover selection part of a self-employed insurance adviser.
Don't implement every details of it, this would take you too long, so follow the lean approach by deciding where you'll focus your energy and time now for this challenge, what you'll delay for later (out of the scope of the challenge) and of course why you take those decisions. Think of it as a solution you would like to build if you had to maintain it yourself afterward.
</aside>
This should take you about between half a day and a day to complete. You have one week to send us your answer as we know you might work on it from time to time on top of you current day job or on top of an ongoing mission at a client.
It's really up to you to see how much time you want to put into this as this is exactly the kind of exercices where it's never really finished.
After a long period of training, a doctor finishes her education training and will start her own business. She goes to her accountant/legal expert that helps her setup all the paper work to start her company. During the process he mentions: "Now, you need to also get yourself insured for any mistakes you might do as a doctor ; you must get yourself a RC pro". Of course she doesn't know what that is, she Googles it and land on blog page written by one our our expert on our website (SEO page) that explains what this insurance is. The blog’s call to action redirects to a small simulation page.
<aside> 👨🏫 The "RC PRO" or "Responsabilité Civile professionelle" is a kind of insurance that all businesses should have to insure themselves against any professional risks they have while working. Its english equivalent is the “professional civil liability” I am sure you will find some quite good information on the internet shall you want to know more about it 😉.
As a doctor's activity is considered as a business by the law (self-employed - independent), she must insure herself with a "RC pro" to protect her against the acts she does while working (administrating the wrong medicine or the wrong dosage, cutting something that must not be cut while in surgery, ...). You get the point.
</aside>
From the company perspective, the context is the following. The main goal of the company is to sell this doctor an insurance contract that will fit her needs and protects her for the years to come. Fortunately, the company is an insurance broker and thus there is no need to reinvent the wheel nor need to create a new insurance product.
For the purpose of this exercise, you will work with an insurance company that has a wonderful Rest JSON API (in reality this is not the case, don't get over excited here, the API has been setup by us for this exercice only 😆).
Your backend colleague just implemented the logic that gathers the user information and you now need to pass that information into the API call, display the quote to the client so that she can select what she wants in terms of covers (covers are the sub-components of a contract).
The business reality is that the client will very probably go on some other websites or check with a friend and ask where he got his insurance, then contact another broker or an insurance's agent. So competition is harsh and we need to find a solution that will provide the client with the most relevant information and present it in a ludic and clean way so that she gets interested in contracting the product with us.
**quote** is more than a price, more about that here). Your colleagues have already implemented a solution that gather all the user information. So for this exercice, you can make the API call with static user information as if you received it from the backend (you can hardcode the payload in JSON file and pass exactly the same info at every call, we don’t care. That’s not the part of the challenge to focus on).