Topcoder Member Records ‌✱ disclaimer

Do you find there is no good way at the official ‌Topcoder website to see and show others your member records? Are you interested to know, how much your fellow Topcoder members earn? This tool provides visualization of Topcoder community member records, and estimates their earnings.


Updated on Nov 27, 2023
NOTE: Updates of member records have been disabled on Dec 14, 2023 as changes in the underlying Topcoder APIs rendered the current implementation non-functional. Currently there is no certain plan to fix it.


Rating: ‌1376

Estimation of Competitor Earnings

Total days spent competing: ‌47 days

Total earnings from competing: 7,050 US dollars

Estimated effective hourly rate: ‌18.5 USD / hour

Records Legend:

/ / ‌ – Topcoder Open Champion in a Data Science / Development / Design track.
1st – challenge winner
2nd – challenge runner-up
– another prize placement
– copilot (technical project manager)

[96hr]Application Modernization Web App - Frontend - Update part 2

Technologies: ASP.NET Core , Angular 11, HTML5, JavaScript, SCSS, TypeScript, UI Prototype
Dates: Sep 9 – 14, 2022
Prize: $1,200

[96h] Taas Platform - Roles Intake - Checkout page and Stripe integration

Technologies: ReactJS
Dates: Aug 3 – 8, 2021
Prize: $900

[48h] MA2 - Database Setup

Technologies: AWS, Dynamodb, TypeScript
Dates: Jul 22 – 25, 2021
Prize: $600

ElasticSearch Sharepoint Stack - Issue Fix

Technologies: Elasticsearch, Microsoft Azure, Sharepoint
Dates: Apr 6 – 12, 2021
Prize: $1,000

ElasticSearch Stack Implementation Challenge

Technologies: Elasticsearch, Search
Dates: Mar 11 – 22, 2021
Prize: $900

SiWC Brewery WiX Website Challenge

Dates: Feb 10 – 14, 2021
Prize: $150

Project ShapeUp | Single SPA application for use as a Documentation

Technologies: ReactJS
Dates: Jan 26 – 30, 2021
Prize: $600

Dragonet Data Management - Power BI Dashboard

Technologies: Power BI, SQL Server
Dates: Oct 30 – Nov 5, 2020
Prize: $1,400

Popular Members

✱) Disclaimer

This service is non-official, and it is not related with Topcoder company. Workload and earning estimates are based on public data available from public Topcoder APIs, and they might be incomplete and erroneous. In particular:

  • Member records include only challenges (i) in which selected member won a prize superior to $100; or (ii) which were copiloted by the member. All first=to-finish challenges are deliberately excluded from the records. Most of data science challenges (Marathon and Single Round Matches) are missing in the records, because they are not reported by the public Topcoder API used by this service (with exception of very recent Marathon Matches).
  • Some records are manually added / corrected for selected members,e.g. to include Topcoder Open victories into results.
  • The time spent by member on competing (copiloting) is estimated as the overall runtime of corresponding challenges included into this member's records. The runtime of a challenge is calculated from the challenge registration start to its submission deadline. If several challenges from member records were running on the same day, that day is counted only once. Overall, this is a very rough estimation of member worktime, which may be very different from the actual time/efforts spent by a member on its challenges.
  • Total earnings from competing are estimated as a sum of prizes won by selected member in the challenges included into his records. The public Topcoder API does not disclose the actual copiltoing payments received by copilots for each challenge, thus to estimate copiloting earning we assume the standard $600 copilot payment for regular-size challenges, and $5000 payment for Marathon Matches.
  • The effective hourly rate is estimated as the total competing (copiloting) earnings divided by 1/3 of estimated time spent by member on copiloting/competing (because the competing/copiloting time estimates are done as the total runtime of a challenge, and do not factor in ~8h out of 24h workday).

Overall, the absolute estimations of workload, earnings, and effective hourly rate should be taken with a grain of salt; however, these estimations should be adequate to compare relative earnings and workload of different members.

© Dr. Pogodin Studio, 2018–2024 — ‌‌ — ‌Terms of Service