Submit a coding problem

Quant coding interviews are not LeetCode. They ask you to price something, simulate something, or deal with a stream of ticks. There is almost nothing public on that.

Every problem you add is one more thing people can be graded on, automatically, for as long as the site exists. Twenty minutes of your time goes a long way.

1. 1
   Log in, or sign up

   Create an account if you do not have one. Google works in one click.

2. 2
   Open the form

   In the sidebar, scroll down to Community and select Submit Coding Problems.

3. 3
   Title and description

   What the function has to do, what it gets, what it gives back, and one worked example. Write it the way you would want to read it with a clock running.

4. 4
   Language, topic, difficulty

   This is how we decide who gets shown it.

5. 5
   Where it was asked

   The company. It is what lets someone practise the firm they are interviewing at.

6. 6
   The three code fields

   The part that makes automatic grading work. Section 3 below goes through them one by one.

7. 7
   Submit to review

   You get an email when it has been read.

8. 8
   Done

This is where people get stuck. Three boxes, three different jobs.

Starter code is what the candidate sees when the editor opens. Usually the function signature and an empty body. We call exactly that name with exactly those parameters, so do not leave a different one in there by accident.

Test stub is the hidden code that calls their function and checks the answer. They never see it. Cover the normal case, the empty case, and whatever edge case makes the problem interesting.

Explanation is the worked solution. It is only shown to someone who asks for it.

We run your tests against your own solution first. If they pass, a human reads the description and the problem joins the coding bank, graded like every other one.

You get an email either way.