Coding questions

You are given a function to implement. The surrounding program — reading input, printing output — is already written. Fill in the body and nothing else.

Running your code

Use Run tests to check your work against the sample test cases before you save.

The samples are not the whole set. Most assessments include hidden test cases that your score also depends on, so passing every sample does not guarantee full marks. Think about the edge cases the samples do not cover: empty input, a single element, very large values, negative numbers.

Run your code at least once before you move on. A solution that looks right and does not compile scores nothing.

Changing language

If the company allowed more than one language, there is a language selector. Switching replaces the editor with the starter code for the new language, so anything you have written is lost — you will be asked to confirm.

Pick your language first, then start writing.

Speed

Compiled languages — Java, Kotlin, Scala, C#, Rust, Go, C++ — take noticeably longer per run than Python or JavaScript, because your code is compiled before it runs. That is normal and it is not counted against you.

Each run shows two timings: how long your code actually ran, and the total including compilation and startup. Only the first tells you anything about your solution.

Saving

Your work is saved automatically as you go, and the header shows the state. If it says Not saved, stop and check your connection before continuing.