Judge me based on these if you are a hiring manager.
Archived
Never saw the light of day... or figma file
For nostalgia...
exe.
Leagues of Code
Something
This should be the problem statement/opportunity statement
Transformed Leagues of Code's learning platform into a competitive programming arena, enhancing user experience and supporting successful internal contests.
Role
+ User Experience
+ User Interface Design
+ User Research
+ Design systems
+ Prototyping
The Squad
+ Myself (Product Design)
+ Ilya Yarmalkevich (Product Manager)
+ Javier Rebolledo (Design Lead)
+ Rose (Front-End)
+ Humberto (Back-End)
+ Brayan Duràn Medina (Back-End)
Impact
Competition leaderboards displayed complex metrics without clear explanations, leaving novice programmers and parents unable to understand rankings and performance
Design Solutions
Competition leaderboards displayed complex metrics without clear explanations, leaving novice programmers and parents unable to understand rankings and performance
Creating focus in the heat of the competition
To tackle the information overload, we created distinct spaces for the problem statement and submission logs. The new design separates these elements into switchable views, allowing contestants to focus fully on either understanding the problem or analyzing their submission attempts. This clean separation maintains easy access to both while eliminating the visual clutter that previously hindered quick problem comprehension during competitions.
Creating focus in the heat of the competition
To tackle the information overload, we created distinct spaces for the problem statement and submission logs. The new design separates these elements into switchable views, allowing contestants to focus fully on either understanding the problem or analyzing their submission attempts. This clean separation maintains easy access to both while eliminating the visual clutter that previously hindered quick problem comprehension during competitions.
Creating focus in the heat of the competition
To tackle the information overload, we created distinct spaces for the problem statement and submission logs. The new design separates these elements into switchable views, allowing contestants to focus fully on either understanding the problem or analyzing their submission attempts. This clean separation maintains easy access to both while eliminating the visual clutter that previously hindered quick problem comprehension during competitions.
Managing the Submission Timeline
Each problem comes with multiple test cases that validate solution correctness, and contestants often make numerous attempts before achieving success. As these submission results accumulated, they would dominate the interface, making it difficult to reference the problem statement. By creating a dedicated space for submission history, we gave contestants the ability to focus on either understanding the problem or analyzing their previous attempts – a simple change that significantly improved the solving experience.
Designing a leaderboard for everyone
Our leaderboard had to be simple. As we planned for our first competition for our students, we wanted to design a scoreboard that was easy to read. Parents had to be considered as well. So a flexible table that could also be viewed on mobile was paramount.