What to Look For When Hiring a Full-Stack Developer for Your Startup

Most hiring advice fixates on the framework checklist. But a developer who lists ten technologies and a developer who has shipped a real product to real users are not the same hire. Here's what actually predicts whether someone delivers.

Shipped products beat listed skills

A CV says "React, Node, PostgreSQL." A portfolio of live, working products says they can take an idea to production and keep it running. Ask to see things that are live — URLs you can open, not screenshots. Shipping is a different skill from knowing syntax, and it's the one you're paying for.

Look for end-to-end ownership

Can they take something from empty repo to live product, handling the data model, the payment integration, the deployment, the edge cases? Or do they need a fully-specced ticket for every step? For a startup, the former is worth several of the latter.

Judgment about scope

The best signal in an interview: ask how they'd build something, and listen for whether they cut scope sensibly. A developer who wants to build everything will never ship; one who instinctively finds the core loop will.

Care where it counts

Good developers know where to be rigorous and where rough is fine. Money paths bulletproof, marketing-page polish later. Misplaced perfectionism is as costly as carelessness.

Communication you can actually work with

You'll be trading messages constantly. Can they explain a tradeoff in plain language? Do they push back when you're about to make a mistake? A developer who only says yes is a risk.

Takeaway

Prioritize shipped products, end-to-end ownership, scope judgment, knowing where to care, and clear communication. Frameworks are learnable; those are the traits that get a product live.

Looking for a developer who ships? That's what I do.