The 'Show, Don't Tell' Revolution
For decades, the path to an IT job was clear: get the right degree, collect relevant certifications, and list them on a polished resume. Today, that model is being disrupted. A significant shift is underway, with hiring managers and tech leaders increasingly
prioritising what a candidate can do over what they claim to know. According to a recent NASSCOM report, a majority of Indian tech employers now value demonstrated, hands-on ability more than formal credentials in their hiring decisions. This 'show, don't tell' philosophy means that a resume, while still necessary for passing initial automated screenings, is no longer enough to convince a human reviewer. Companies want to see your skills in action before they make an offer.
Why Proof of Work Is Winning
Several factors are driving this change. Firstly, the rapid evolution of technology means that skills gaps are a constant challenge for businesses. A certification from two years ago might not reflect the current demands of a role. Tangible projects provide up-to-the-minute proof of a candidate's capabilities. Secondly, this approach de-risks the hiring process. Evaluating a project portfolio or a code repository allows a company to assess a candidate's real-world problem-solving abilities, not just their talent for passing exams. This is especially true for in-demand specialisations like AI, cybersecurity, and cloud engineering, where practical application is everything. Employers are looking for professionals who can bridge the gap between business needs and technology, and project evidence is the most reliable indicator of that skill.
What Counts as 'Project Evidence'?
The term 'project evidence' is more than just a link to a GitHub profile. It’s about creating a compelling, curated showcase of your abilities. This can take many forms, including: a personal website with detailed case studies explaining a project's goals, your process, and the outcome; a well-documented GitHub repository with clean, commented code for a personal application you built; public write-ups of your participation in Capture the Flag (CTF) competitions or hackathons; contributions to open-source projects, no matter how small; and detailed blog posts that break down a complex technical problem you solved. The key is to move beyond simply listing a technology and instead provide verifiable proof that you can use it to build, troubleshoot, or create something of value. For freshers, even well-documented university projects or practicals from online courses can serve as powerful evidence.
Building Your Evidence-Based Application
Integrating this evidence into your job application requires a strategic approach. Your resume is still the first point of contact and needs to be optimised for Applicant Tracking Systems (ATS). However, it should also serve as a gateway to your project work. Include a clear, clickable link to your portfolio or primary repository in your contact information section. In the body of your resume, instead of just listing responsibilities under a previous role, use bullet points to describe measurable achievements and link them to specific projects where possible. For instance, instead of saying "Developed a web application," try "Developed a full-stack e-commerce application, resulting in a 15% improvement in page load speed. (Live demo available at portfolio link)." In your cover letter and during interviews, be prepared to talk through your projects in detail—explain the challenges you faced, the decisions you made, and what you learned. This transforms your application from a static document into a dynamic demonstration of your value.
