How to evaluate your project before a technical interview

In a technical interview, your project is your strongest asset and your weakest point at the same time. It is the only piece of your work the interviewer can examine critically before you even speak. Evaluating it beforehand turns a weakness you know nothing about into a list of concrete fixes.

The goal is never perfect code. The goal is knowing exactly where your project stands so you can explain it, improve it, or honestly discuss its trade-offs.

A complete evaluation has three steps. First, define the profile against which you are being measured: your role (Frontend, Backend, Fullstack or Infrastructure) and your seniority (Junior to Staff). Second, gather the code that represents you. Third, audit it across the six dimensions.

• Step 1 — choose your role and seniority so the evaluation is fair
• Step 2 — upload or prepare your project, including the README and architecture notes
• Step 3 — score each dimension and collect concrete recommendations

Architecture

• Is the folder structure obvious without a guide?
• Are concerns separated (UI, business logic, data access)?
• Would the structure survive a doubling in size?

Code quality

• Are names descriptive and consistent?
• Do functions do one thing?
• Would a teammate understand it in a 15-minute read?

Testing

• Does the critical behavior have tests?
• Do tests assert behavior, not implementation trivia?
• Is the coverage realistic and not purely vanity metrics?

Documentation, deploy and best practices

• Documentation: does the README explain setup, usage and decisions?
• Deploy: is there CI/CD, environment config and a production story?
• Best practices: security, performance and accessibility basics covered?

• No README, forcing the interviewer to reverse-engineer everything
• One giant folder with every file at the same level
• Commits that mix features, fixes and "misc changes"
• Secrets committed to the repository
• A .gitignore that includes node_modules or build artifacts

Most of these are easy to fix once you know they exist, which is precisely why an automated evaluation is useful: it does not judge you, it lists what to improve.

If you want a structured start, upload your project to RateYourProject. You choose role and seniority, the analysis runs across the six dimensions, and you get a hexagonal chart plus recommendations you can act on before the interview.