Back End Test Project

You should see this challenge as an opportunity to create an application following modern development best practices (given the stack of your choice), but also feel free to use your own architecture preferences (coding standards, code organization, third-party libraries, etc). It’s perfectly fine to use vanilla code or any framework or libraries.

Scope

In this challenge you should build an API for an application that stores and manages investments, it should have the following features:

1. Creation of an investment with an owner, a creation date and an amount.
   1. The creation date of an investment can be today or a date in the past.
   2. An investment should not be or become negative.
2. View of an investment with its initial amount and expected balance.
   1. Expected balance should be the sum of the invested amount and the gains.
   2. If an investment was already withdrawn then the balance must reflect the gains of that investment
3. Withdrawal of a investment.
   1. The withdraw will always be the sum of the initial amount and its gains, partial withdrawn is not supported.
   2. Withdrawals can happen in the past or today, but can't happen before the investment creation or the future.
   3. Taxes need to be applied to the withdrawals before showing the final value.
4. List of a person's investments
   1. This list should have pagination.

NOTE: the implementation of an interface will not be evaluated.

Gain Calculation

The investment will pay 0.52% every month in the same day of the investment creation.

Given that the gain is paid every month, it should be treated as compound gain, which means that every new period (month) the amount gained will become part of the investment balance for the next payment.

Taxation

When money is withdrawn, tax is triggered. Taxes apply only to the profit/gain portion of the money withdrawn. For example, if the initial investment was 1000.00, the current balance is 1200.00, then the taxes will be applied to the 200.00.

The tax percentage changes according to the age of the investment:

• If it is less than one year old, the percentage will be 22.5% (tax = 45.00).
• If it is between one and two years old, the percentage will be 18.5% (tax = 37.00).
• If older than two years, the percentage will be 15% (tax = 30.00).

Requirements

1. Create project using any stack of your preference, but with PHP as its main language. It’s perfectly OK to use vanilla code or any framework or libraries;
2. Although you can use as many dependencies as you want, you should manage them wisely;
3. It is not necessary to send the notification emails, however, the code required for that would be welcome;
4. The API must be documented in some way.

Deliverables

The project source code and dependencies should be made available in GitHub. Here are the steps you should follow:

1. Fork this repository to your GitHub account (create an account if you don't have one, you will need it working with us).
2. Create a "development" branch and commit the code to it. Do not push the code to the main branch.
3. Include a README file that describes:
   • Special build instructions, if any
   • List of third-party libraries used and short description of why/how they were used
   • A link to the API documentation.
4. Once the work is complete, create a pull request from "development" into "main" and send us the link.
5. Avoid using huge commits hiding your progress. Feel free to work on a branch and use git rebase to adjust your commits before submitting the final version.

Coding Standards

When working on the project be as clean and consistent as possible.

Project Deadline

Ideally you'd finish the test project in 5 days. It shouldn't take you longer than a entire week.

Quality Assurance

Use the following checklist to ensure high quality of the project.

General

• First of all, the application should run without errors.
• Are all requirements set above met?
• Is coding style consistent?
• The API is well documented?
• The API has unit tests?

Submission

1. A link to the Github repository.
2. Briefly describe how you decided on the tools that you used.

Have Fun Coding 🤘

• This challenge description is intentionally vague in some aspects, but if you need assistance feel free to ask for help.
• If any of the seems out of your current level, you may skip it, but remember to tell us about it in the pull request.

Credits

This coding challenge was inspired on kinvoapp/kinvo-back-end-test