Make your work easy to assess
Optional ways to make technical evidence clear to recruiters and interviewers.
Use this page to make your work easier to review. No contest rating, public post, referral, meetup, or internship guarantees an interview. Choose only activities that support your applications and do not crowd out preparation.
Start with a clear resume and project README. Add other signals only when you have real work to show.
The seven plays
| Play | Time per week | When |
|---|---|---|
| Contest practice | During interview practice | When useful |
| Open-source work | Optional | When you find a relevant issue |
| Project writing | After a real milestone | As useful |
| GitHub profile | One-time cleanup | Before applications |
| Meetups and community | Optional | When useful |
| Mock feedback | Inside the mock slot | Keep scores private by default |
| Internships | Based on fit | Apply when eligible roles appear |
Keep optional work optional
The week template already includes interview practice, applications, reading, and project time. Do not add all of these activities on top.
How the plays fit the week
Use an existing slot for any activity you choose. Keep interview practice and job applications ahead of public posting or extra events.
Open-source work and meetups are optional. Skip them during exams, project deadlines, or active interview loops.
Review internship terms carefully. Conversion depends on the employer and is never guaranteed.
Where to start
Start with the GitHub profile and project README. Add one other play only when it helps your current applications.
Read the play in full before you start it. Each one has a do list and a do-not list, and the mistakes cost more time than the work.