CC byteStandard~3h time-box

Deploy Window

You are building a deployment scheduling tool for a platform engineering team. Deployments follow a recurring calendar pattern: the team always deploys on a specific weekday occurrence within a month (e.g.

Deploy Window
Step 1
Clone the starter repo
Candidate gets the full project locally — README, source, tests, runner config.
Step 2
Run the visible tests
Public test file is right there. Expectations are explicit from minute one.
Step 3
Make tests pass, push
Candidate works in their own style, pushes reviewable commits for your team.
Starter repo
What candidates clone
1 files
  • CMakeLists.txt

The full README and the hidden test suite are available once you open the byte in your CodeSubmit workspace. Candidates never see the hidden tests.

Skills tested
control flow if statementsstringsstructstime functions
Difficulty
Standard

Standard engineering judgment. Multiple edge cases worth handling.