Problem Writing for Rapid Development Matches (RDMs)

Do you have the skills and ideas to write/test interesting problems for our new Rapid Development Competitions? Here’s what you need to do:

Problem Writing

What are the roles and responsibilities of a problem writer?

As a problem writer your tasks will be:

• Prepare a problem statement with a single clear requirement or a bunch of related requirements which is independent of language, technology or any library.

• Wrap it around an interesting fantasy or real world business statement with the help of the contest coordinator.

• Prepare the required environment or starter pack/packs for the problem.

• Prepare automation test script with relevant test cases for automated review system.

• Work with the match coordinator and prepare the problems based on coordinator/tester feedback.

• Be available during the contest to help the members navigate questions or issues they have.

We are starting new contests and all problem ideas in any category of software development are welcome, be it System Design, Front-End, Back-End or Web App/Mobile App.

How does it work?

There are three ways to write problems for RDMs:

• Write a full problem set (three problems). Each contest has three problems, you can write all the problems of the contest

• Collaborate with other members (for example, your friends) and construct a full problem set as a group.

• Write a subset of the problem set. The subset should contain a medium or a hard problem. We will try to complement your subset with problems from another writer. Please note that it may be necessary to wait in order for an appropriate complement to become available.

Eligibility:

1. 18+ years old

2. Topcoder Development rating of at least 1100
   OR
   You should be a Topcoder Copilot/Reviewer for the Development Track

You may not participate in any contest in which problems you wrote are being used.

How will you be paid?

Being a problem writer can pay the bills! Here is the breakdown of payments:

ENTIRE RDM PROBLEM SET**: $500

AUTOMATED TESTER PAYMENTS

How do you submit your problem proposals?

• Prepare raw problem ideas and send them to us at talgorithm@topcoder.com. You don’t need to wrap the problem in a fantasy or a business statement at this moment. Make sure you share your Gitlab username in the email.

• You will be given access to a Gitlab Repository to add your problem statements in the given template. Sample statement and the rest of the details are available in the Readme file of the repository.

• Your proposal will be reviewed and you will be provided feedback and informed about the contest they will be used for.

• Once they are used, you will be paid according to the payments mentioned via Topcoder Payments.

Problem Testing

As a round tester your tasks will be:

• To judge the feasibility, difficulty, time and issues members might run into.

• Suggest and add proper statements and help links to allow members to solve these challenges without any hiccups.

• Read over the problem statement, suggest edits, write up a test solution to confirm it matches the expected solution.

How does it work?

• You will be assigned a full match to test (three problems).

• You will have to submit your solutions and be available to discuss the problem statement with the coordinator and the problem writer.

Eligibility:

1. 18+ years old

2. Topcoder Development rating of at least 1100
   OR
   You should be a Topcoder Copilot/Reviewer for the Development Track

You may not participate in any contest in which problems you wrote are being used.

How will you be paid?

How do you submit your tester application ?

• Prepare a cover letter application and share with us at talgorithm@topcoder.com.

• You will be given access to a Gitlab Repository where problem statements for the match will be available to you for testing and providing feedback.

• Once the contest is complete, you will be paid accordingly via Topcoder Payments.