Team and accountability

Names before claims.

Compute Forward was founded by two high schoolers who understand the path from learning basic syntax to solving advanced algorithmic problems. We built the structured curriculum, live instruction, and mentorship system we wished existed when we started.

Founder profile 01

Anish Koppula

Co-Founder USACO Platinum

Anish is a USACO Platinum competitor and co-founder of Compute Forward. He helps develop the program’s curriculum in Python, data structures, algorithms, and competitive programming, while guiding students toward stronger independent problem-solving skills.

FocusAlgorithms · Competitive Programming · Data Structures · Mentorship

anishkoppula@gmail.com

Founder profile 02

Kaushik Atla

Co-Founder USACO Platinum

Kaushik is a USACO Platinum competitor and co-founder of Compute Forward. He designs and teaches structured lessons that help students progress from programming fundamentals to advanced algorithmic problem solving and contest preparation.

FocusPython · Algorithms · Curriculum Design · Competitive Programming

kaushik.atla@gmail.com

Cohort launch gate

A cohort does not begin with anonymous responsibility.

Before any active cohort starts, this page and the family cohort brief must identify the accountable people.

Founder profiles

Approved biography, relevant experience, role, and direct contact path for each active founder.

Mentor roster

Name, program role, relevant experience, screening status, conduct acknowledgement, and training completion.

Safeguarding ownership

A named adult-oversight and safeguarding contact, escalation coverage, and the limits of student-led operations.

How accountability works

One owner for every workstream.

Program operations

Scheduling, attendance, family communication, and admissions response commitments require a named owner in the cohort brief.

Curriculum and mentorship

Each level requires a curriculum owner, active mentor roster, review expectations, and clear progression rules.

Safety and privacy

Reports, incidents, privacy requests, and data deletion need named responders and a documented handoff path.