HackerRank Tips and Tricks

• If you’re new to HackerRank, try the sample test first. It will help you learn the environment. We will NOT see your results for the sample test.
• HackerRank will give you 60 minutes to complete each question. If you run out of time, it's OK. We will still receive any code you wrote into the HackerRank IDE.
• You can code in any language you'd like. Make sure to select your preferred programming language in the HackerRank's IDE.
• Write comments in your code so we can follow along with your thought process.
• When you run your code, it will be tested against various inputs and you will be told if your code passed the test cases. These test cases are helpful, but THIS IS NOT YOUR SCORE and it will not be used to determine if you are accepted. If your logic and thought process is correct but it does not pass any tests, you still have a good chance of passing the challenge.
• Our technical instructors will be reading and grading everyone's code submission, even if it passes 0 test cases! Do your best at writing your solution in code and write comments that we can look at when reviewing your code.
• DON'T CHEAT!!! We will be reading everyone's code, and HackerRank also detects code copied from online sources. We want to give you every chance to be accepted, but cheating is not tolerated. The following are considered cheating:
  • Searching the challenge programming question online
  • Copying a solution from an online source
  • Sharing the question and your solution with others or posting it online
• Here is a video with more CUNY Tech Prep HackerRank tips and tricks.

Virtual In Person Interview

• Get a good night's rest before the interview.
• For behavioral questions, don't just give one word answers; provide honest detail about your past experiences, and show enthusiasm!
• For the live coding part of the interview, don't jump straight into coding. Before you begin to code, do the following:
  • Understand what is being asked by asking the interviewer clarifying questions.
  • Understand what the expected input and output is by giving the interviewer for an example input and output to make sure it is correct.
  • Walk through and sudo code out your program before actually writing the code.
• Once you begin coding:
  • Pick good descriptive function and variable names.
  • Write clean and neat code with appropriate spacing indentation.
  • Use a simple input example, and go through line by line what is happening in your code to that simple input example.
  • Write comments above each line that explain what is happening at each step.
• If you are stuck, ask the interviewer for hints! This is totally acceptable and is encouraged in real world interviews.
• Although not required, it is also a good practice to send a follow up thank you email to your interviewer.

Here are additional resources that may help you with your application and journey.