Career Strategy

Weaponise Your GitHub: How to Control Interviews and Avoid Unpaid Tests

A curated GitHub can be a negotiation tool: anchor interviews to your codebase, offer walkthroughs instead of unpaid tests, and use PRs to build recruiter relationships.

## Use GitHub as leverage, not just a portfolio Direct answer: Link a relevant, well-documented project on your CV and offer a live walkthrough to replace a take-home test — it signals capability and sets the interview agenda. ## Hijack the whiteboard with your repo Hyperlink one complex, relevant project in your Technical Projects section. Interviewers naturally ask about what you link. Instead of being tested on abstract algorithms, you get to discuss your own architectural choices, trade-offs and metrics. This changes the conversation from "Can you solve this puzzle?" to "Why did you design it this way?" If the interviewer insists on a take-home test, offer this alternative: "I can walk you through this repository and demo the feature; it will show the same skills the take-home test hopes to measure." For senior candidates this is often accepted because it respects both parties’ time. ## Push back on unfair take-home tests Senior engineers should set boundaries. A curated repo with a comprehensive README and a short demo video is a reasonable substitute for a multi-hour unpaid test. Phrase it professionally: offer a focused walkthrough, a timed pairing session, or a short code review instead. Keep the ask low-friction: 30–45 minutes to discuss a real codebase demonstrates practical problem-solving more effectively than an artificial take-home. ## Use PRs to access the hidden market Open-source contributions are a networking tool disguised as work. A well-placed pull request to a project forces a maintainer-level interaction. Use maintainer feedback to build rapport, iterate on your code, and then politely request an informational chat. That conversation often turns into an internal referral — bypassing the ATS entirely. - [ ] Pick one repo to hyperlink on your CV with a short justification line - [ ] Create a 3–5 minute demo video for that repo and link it in the README - [ ] Offer a 30–45 minute repo walkthrough as a polite alternative to a take-home - [ ] Use PR feedback to start conversations with maintainers and ask for referrals *For more on career leverage, explore our [Career Strategy](/career-strategy) insights.*