Web Developer: resume screening criteria template

Can they show you working code and live projects? This is the single best predictor of whether someone can actually build what you need. You want to see 3+ substantial projects (not tutorial follow-alongs) that demonstrate they can take an idea from start to finish.

Strong evidence: GitHub link with multiple repositories showing original code, portfolio website with live project links and descriptions of what they built, specific projects listed with URLs you can visit, screenshots or case studies explaining technical decisions, mentions of deploying or launching sites

Red flag: No portfolio link, no GitHub, or links that lead to empty repositories or tutorial projects only. Lists frameworks but shows no actual work. Portfolio shows only design mockups with no code. Projects mentioned but no way to verify they exist.

Do they have hands-on experience with the technologies you actually use? Look for 2+ years of building real websites or applications, whether in jobs, freelance work, or substantial personal projects. Prioritize depth in core web technologies over a long list of every framework.

Strong evidence: Job titles like Web Developer, Frontend Developer, Full Stack Developer, or Freelance Web Developer with duration listed. Specific mentions of HTML, CSS, JavaScript plus backend languages (PHP, Python, Ruby, Node.js). Experience with frameworks relevant to your stack (React, Vue, WordPress, Django). Mentions of databases, APIs, or version control (Git).

Red flag: Only lists technologies with no context of where they used them. Experience is all from bootcamps or courses with no subsequent work. Gaps between learning and doing (completed bootcamp 2 years ago, no projects since). Lists 15+ frameworks suggesting shallow knowledge of many rather than depth in any.

Can they build sites that actually work well? Slow, broken, or mobile-unfriendly sites cost you customers. Look for evidence they think about performance, not just features. The best candidates mention metrics: load times, Core Web Vitals, mobile responsiveness scores.

Strong evidence: Mentions optimizing page load times or site speed with specific improvements (reduced load time from 4s to 1.2s). References to responsive design, mobile-first development, or cross-browser testing. Experience with performance tools (Lighthouse, PageSpeed Insights). Mentions of image optimization, lazy loading, caching, or CDN implementation. Talks about accessibility or SEO considerations.

Red flag: Portfolio sites that load slowly or break on mobile. No mention of performance, optimization, or mobile considerations anywhere in resume. Only focuses on adding features, never improving existing code. No awareness of how real users experience websites.

Can they fix things when they break? Every website has bugs and technical debt. You need someone who can troubleshoot issues, read other people's code, and solve problems independently rather than getting stuck and waiting for help.

Strong evidence: Mentions maintaining or improving existing codebases (not just building new). Describes fixing specific bugs or technical problems. Experience with debugging tools or methodologies. References to refactoring, code reviews, or technical debt reduction. Talks about troubleshooting production issues or handling edge cases.

Red flag: Resume only mentions building new projects, never maintaining or fixing existing ones. No mention of debugging, testing, or handling errors. Describes only greenfield work with perfect conditions. Can't articulate technical challenges they've overcome.

Can they work with non-technical people? Web developers in small businesses translate requests from owners, marketers, and customers into working code. Look for evidence they've gathered requirements, explained technical tradeoffs, or worked on teams.

Strong evidence: Mentions working with designers, stakeholders, or clients. Describes translating business requirements into technical solutions. References to documentation, code comments, or knowledge sharing. Experience explaining technical concepts to non-technical audiences. Mentions of Agile, standups, or collaborative workflows.

Red flag: Resume only describes solo work with no mention of teams or stakeholders. Uses jargon-heavy language suggesting inability to communicate with non-developers. No evidence of client-facing work, requirement gathering, or collaboration. Describes conflicts or communication breakdowns without resolution.

Do they finish what they start? Some developers endlessly tinker or start projects they never complete. You need someone who ships working code on schedule. Look for evidence of completed projects, launched sites, or consistent delivery.

Strong evidence: Multiple projects with completion dates or launch dates. Mentions of deadlines met or projects delivered. References to deployment, going live, or production releases. Freelance work with multiple completed client projects. Describes full project lifecycle from requirements to launch.

Red flag: Many started projects with no evidence of completion. Portfolio full of works-in-progress or coming soon. Long gaps between projects. Describes elaborate plans but no shipped results. Only mentions learning or experimenting, never delivering to users.