Optional ways to show your work
Practical ways to make project and interview evidence easier to review.
Use these ideas when they add evidence to your applications. They are optional. A public score, post, event, or referral does not guarantee an interview.
Practise with contests
Use a weekly contest as timed practice if it fits your schedule. Review the problems you missed and add useful patterns to your revision deck. Treat rating as a personal progress measure, not a hiring requirement.
Contribute to open source
Choose a project you use or understand. Read its contribution guide, start with a clear issue, and ask a maintainer when the expected change is unclear. One reviewed change can teach you how to work with an existing codebase. Do not plan around a PR being merged by a deadline.
Write about completed work
Write a short design note after a meaningful project milestone. Explain the problem, an alternative you considered, the tests you ran, and what the results showed. Link the note from the project README. Do not write a post only to meet a publishing target.
Prepare your GitHub profile
Make the first page easy to scan. Pin the strongest finished repositories, add a clear description, and make setup instructions work. Each project README should say what is implemented, how to run it, how to test it, and what you measured.
Meet people when useful
Attend a technical meetup, student event, or online community when the topic matches your interests. Ask about the work people do and follow up only when there is a natural reason. Events are optional and do not replace applications.
Use mock feedback privately
Keep mock scores and feedback in your tracker. Share a lesson publicly only if it helps others and does not expose private interview questions or another participant's feedback. After each mock, write one thing to practise next.
Consider internships carefully
Apply to internships that fit your graduation date, finances, and learning goals. Ask about responsibilities, mentorship, hours, stipend, and any stated conversion process. A conversion is never guaranteed, so continue considering other suitable roles.
Choose one useful next step
Before adding an activity, name the evidence it will create and the role it supports. If you cannot name either, leave it off this week's plan.
Do and don't
- Share specific work you completed
- Keep public descriptions consistent with the code
- Respect other people's time and privacy
- Keep optional activities inside the hours in your plan