← Back to Home

Submit a Challenge

Share your real-world engineering challenge with our community. Help us build a comprehensive library of practical assessment tools.

Submit a Challenge

Creating high-quality challenges is a significant undertaking. Each challenge typically takes multiple days to develop, test, and refine. The value comes from their depth, complexity, and real-world relevance.

Our challenges are not designed to trick or stump candidates. Instead, they represent real engineering problems you might encounter in a production codebase, requiring thoughtful solutions and practical engineering skills.

What Makes a Good Challenge?

  • Real-world production scenarios that reflect actual engineering challenges
  • Clear success criteria and multiple valid approaches
  • Sufficient complexity to require multiple days of work
  • Tests practical engineering skills and decision-making

ML Coding Agent Considerations

  • Clear, well-defined requirements and success criteria
  • Solutions should be verifiable through automated testing
  • Context should be easily parseable by ML models

Quick Path to Approval

The fastest way to get a challenge approved is to build on our existing codebases:

  • Identify real issues in our production codebases
  • Propose improvements to existing challenges
  • Create variations of proven challenges

Example of a Bad Submission

Title: "Implement a Custom Hash Function"

Problem: Create a hash function that takes a string input and returns a unique integer. The function should be collision-resistant and efficient.

Why This is a Bad Submission:
  • Too theoretical - real-world systems rarely require custom hash functions
  • Success criteria are vague ("collision-resistant" and "efficient" are subjective)
  • No real-world context or business value
  • ML agents can easily solve this with standard library implementations
  • Doesn't test practical engineering skills or decision-making

Better Alternative:

"You're working on a legacy e-commerce system that processes orders through a complex workflow. The system has multiple microservices with inconsistent error handling, and orders occasionally get stuck in intermediate states. Design and implement a solution to identify, recover, and prevent these stuck orders while maintaining system availability."

  • Requires understanding of complex, real-world system interactions
  • Involves working with legacy code and technical debt
  • Needs careful consideration of business impact and risk
  • Requires deep system understanding to identify root causes
  • Tests ability to balance immediate fixes with long-term improvements
  • Success depends on understanding the specific business context

Challenge Development Workflow

1

Idea Submission

Submit your challenge idea for initial review. This can be a brief description of the problem and why it's valuable.

2

Initial Design

Once approved, work on creating the core problem, success criteria, and initial test cases.

3

Technical Review

Senior engineers evaluate the challenge's technical merit, difficulty level, and real-world relevance.

4

Testing Phase

Multiple developers attempt the challenge to validate difficulty, clarity, and solution approaches.

5

Refinement

Incorporating feedback, improving documentation, and finalizing evaluation criteria.

6

Final Approval

Once approved, your challenge becomes part of our assessment library.