Hello developer, thank you for taking time to resolve this challenge. Please read carefully the instructions below before start and feel free to ask any question you may have.
This challenge contains 3 exercises that will help us to understand your way of coding.
- Logical exercise (required)
- Framework exercise (required)
- SQL exercise (optional)
- FORK this repo, DO NOT clone it
- Once you forked it, before to start change the
authorwithin thepackage.jsonfile and add your name - Install the dependencies, run the
devscript and go to:http://localhost:5173/ - To start the challenge perform the first commit with the
authorchange
We will consider this commit as the start of the test, you will have 120 min to complete this challenge. We will only consider the commits you make that are within the 120 min range, you will have only 8 minutes of margin (because of the time it may take to make the commits).
- Please, DO NOT use github copilot for this challenge, yes I know we use it daily but for this test, we want to evaluate your skills.
In order to properly assess the candidate's skills, problem-solving abilities, coding style, and overall suitability for the position. Here are some important factors we will consider.
Correction: The candidate ensures that the code works as expected and solves the problem described in the challenge. Look for bugs, logic errors and edge cases that might not have been addressed.
Effectiveness: We will evaluate the efficiency of the code in terms of time complexity, space complexity and performance. We will also evaluate whether the candidate has chosen appropriate data structures and algorithms to solve the problem efficiently.
Readability: We will evaluate the readability and maintainability of the code. Clear variable names, well-structured code, meaningful comments, and adherence to coding conventions and best practices.
Scalability: We will consider whether the code is designed to scale well as the size of the input data increases. We will evaluate the candidate's ability to write code that can handle larger data sets without compromising performance or functionality.
Error handling: We will check whether the code includes adequate error handling mechanisms to deal with unexpected input, exceptions and edge cases. We will evaluate the robustness of the code in handling potential errors and bugs.
Testing: We will consider with higher priority candidates who add unit tests to their code, for us it is very important that they have knowledge of testing.
Documentation: We will evaluate the quality and completeness of the attached documentation or comments provided by the candidate. As well as whether the documentation effectively explains the purpose of the code, its functionality and how to use it.
Creativity: We will consider whether the candidate has demonstrated creativity and innovation in their approach to solving the problem. We expect unique or elegant solutions that demonstrate a deep understanding of the problem domain.
Collaboration and communication: If the code challenge involved collaboration or communication with other team members, we will evaluate how effectively the candidate communicated ideas, solicited feedback, and incorporated suggestions from others.
Overall fit: We will consider the fit of the candidate's skills, experience and problem-solving approach with the organization's requirements and culture. Evaluate whether the candidate would be a good fit for the team and the position you are applying for.
I know, all of this sounds kinda picky, but at the end of the day we consider that those are basics of any software engineer, and you'll be facing this kind of challenges daily, but we hope you love your job as much as we do, so don't worry if you couldn't complete the whole exercise, we value the effort and we will only evaluate the code you write, not if you complete the 100% of each exercise.
Goku and Vegeta are training with Wiss to increase their powers using training dummies. Each turn, the number of dummies is randomized and each dummy has a number written on it that represents the number of hits it can take before it is destroyed.
Wiss has given them the following conditions:
- Only 2 dummies can be hit per turn.
- Once you hit the first dummy, you can only hit dummies that are to the right of it, not to its left.
- The subtraction of the number of the first dummy minus the second must not be negative.
As punishment they must change the Bills sheets according to the subtraction between the number of hits of the first dummy minus the second. So you must concentrate on making sure that the subtraction is always the smallest possible. (You wouldn't like to change Mr. Bills' sheets many times, would you?)
To make sure your code works, we have added some test cases. DO NOT modify the test cases files, only run the
pnpm testscript within thepackage.jsonfile.
Example: dummies = [10, 7, 20, 8, 4] // each number represent the number of hits it can take before it is destroyed
The minimum times they should change Bills sheets is by hitting the first dummy at dummies[0] = 10 and the fourth dummy at dummies[3] = 8.
Return 10 - 8 = 2
Description:
Complete the fewerChangeSheets() function located at src/modules/logical-exercise/result.ts that accept following parameter(s):
- int dummies[n] array: a list of dummies (remember, the length of the array represent how many dummies appeared, and each position represent the number of hits each one can take)
Returns:
- int: the minimum possible change of sheets
Constraints:
- All the number of hits are distinct.
- A valid answer exists always.
Sample Input 1
5 10 3 9 7
Sample Output 1
1
Explanation 1
Vegeta hits the second dummy at dummies[1] = 10 and the fourth dummy at dummies[3] = 9, as result he will only change Bills sheets once
Sample Input 2
8 15 6 22 11 30
Sample Output 2
2
Explanation 2
Goku hits the first dummy at dummies[0] = 8 and the third dummy at dummies[2] = 6, as result he will change Bills sheets 2 times
Using the Poke Api, the goal is to be able to list a bunch of pokemons and see their original sprites and with a button, see it's shiny sprite, as well as their name, their available types and their abilities.
Acceptance criteria:
- Must use Redux Toolkit as state management
- Must use RTK Query for fetching pokemon data
- If the pokemon already exists in the store, should retrieve it from there instead of performing an api call
- Only pokemon names are displayed within the list
- User should be able to switch between original sprite and shiny as desired
Optional:
- Current state must persist on window reload
- The user can change the number of pokemon to be displayed in the list
Using HackerRank, we'll perform this challenge, it's optional so feel free to do it if you want, since SQL is not required for your position, may be helpful to have some extra knowledge.
Please resolve this exercise, and add your solution to the src/modules/sql-exercise/index.sql file