Questions to Ask a Web Developer Before Hiring

You have a shortlist, a budget, and a 30-minute call. What you ask in that call decides whether you get a site that feels like your brand or a template with a custom invoice. This is the practical list — the questions to ask a web developer before hiring, grouped by what actually goes wrong, with the green-flag and red-flag answers for each. It is written from the other side of the table: I am a creative developer and an Awwwards jury member, so I have answered these questions for clients and judged hundreds of the sites that came out of them.

Use it as a checklist. You do not need to ask all of them — pick the groups that match your project and listen for trade-offs, not buzzwords.

First, what separates a creative developer from a templater

Before the questions, the frame. A templater starts from a theme or a page builder and bends it toward your brand. The output looks fine in a thumbnail and falls apart the moment you want a custom interaction, a motion sequence, or a WebGL moment — because the foundation was never built for it. A creative developer starts from the design and the outcome, owns the motion and the performance budget, and writes the code that makes interaction feel expensive on a real phone.

Almost every question below is designed to surface that difference. A templater answers in features and plugins ("I'll use this slider, this animation library"). A practitioner answers in trade-offs ("a GSAP timeline here because we need scrubbing, but the hero stays CSS so LCP doesn't suffer"). If you only remember one thing: the depth of the answer matters more than the answer itself. If you are still deciding whether you need this kind of specialist, start with what a creative developer is and when you need one.

Portfolio & craft

This is the interview. Spend your time here, not on the CV.

"Can I see live links, not just a showreel?" Showreels hide jank. You want URLs you can open on your own phone.

• 🟢 Green flag: a handful of live sites they're proud of, opened without hesitation.
• 🔴 Red flag: "it's under NDA," "the client took it down," or only video. Some NDAs are real — but if everything is hidden, you can't verify anything.

"Which parts of this project did you personally build?" One slick site can be a team effort. You're hiring a person, not a logo.

• 🟢 They draw a clear line: "I owned the front-end and all the motion; the studio did the design."
• 🔴 Vague "we" language that never resolves into what they did.

"Do you have any third-party recognition?" Anyone can say "award-winning." Juried recognition is strangers who do this for a living rating the craft.

• 🟢 Verifiable honors: Awwwards Site of the Day, CSS Design Awards, FWA, the GSAP showcase. For calibration, my own work has earned multiple Awwwards Site of the Day awards, Awwwards "Independent of the Year" twice, and a CSS Design Awards Website of the Month — and I sit on the Awwwards jury, so I judge these too.
• 🔴 "Award-winning" with nothing you can click to confirm.

"Show me something that went wrong and how you fixed it." Experience lives in war stories, not in a flawless highlight reel.

• 🟢 A specific, slightly uncomfortable story with a technical resolution.
• 🔴 "Nothing's ever really gone wrong." Everyone has shipped a bug at 2am.

Process & communication

Most builds don't fail on talent — they fail on the gap between what you imagined and what got built. Process closes that gap.

"Walk me through how a project runs, from kickoff to launch."

• 🟢 A real shape: discovery → design alignment → milestones → staging reviews → launch → handover. Clear checkpoints where you see and approve progress.
• 🔴 "You send the brief and I send you the finished site." No checkpoints means no chance to course-correct.

"How and how often will we communicate?" This is the single best predictor of how the project will feel. Communication lag during the sales phase almost never improves after the contract is signed.

• 🟢 A named channel and cadence (weekly check-in, staging link, async updates). My long-term collaborators consistently cite clear, proactive communication as the reason they come back — it should be the baseline, not a bonus.
• 🔴 Slow, vague replies before you've even paid.

"What do you need from me, and when?" Good practitioners manage your side of the project too — content deadlines, asset delivery, approvals.

• 🟢 A clear list of what they need and the dates it's needed by.
• 🔴 No expectations set — which means the slippage will quietly become your fault.

"How do you handle scope changes mid-project?"

• 🟢 A defined change process (a small change log, a quick re-quote for big additions). Calm, not adversarial.
• 🔴 Either rigid "that's out of scope, full stop," or a pushover who absorbs everything and burns out before launch.

Motion, WebGL & performance

This is where templaters and creative developers visibly diverge — and where most of the value (and the risk) of an interactive site lives.

"Walk me through how you'd build the hero on [a reference site I like]." The single most revealing question in the call.

• 🟢 Approach and trade-offs: GSAP timeline vs. scroll-driven, when WebGL earns its weight, what they'd simplify to protect performance.
• 🔴 Naming a library and stopping there. Tools aren't a plan.

"How do you keep this at 60fps on a mid-range Android?" Beautiful and slow is a failed brief.

• 🟢 Concrete tactics: GPU vs. main-thread work, lazy-loading heavy assets, throttling, animating transforms not layout. You can sanity-check the techniques against our GSAP ScrollTrigger tutorial and the guide to smooth scroll in Next.js with GSAP and Lenis.
• 🔴 "Modern phones are fast, it'll be fine." That's how you ship a 4-second hero.

"What happens on slow connections and for users who disable motion?" Accessibility and graceful degradation are non-negotiable for a professional.

• 🟢 Mentions prefers-reduced-motion, fallbacks, and progressive loading without being prompted.
• 🔴 Hasn't thought about it — your beautiful site will be unusable for a real slice of visitors.

"Can we run Lighthouse / Core Web Vitals on your flagship work right now?"

• 🟢 Happy to; treats a performance budget as part of the design, not an afterthought. Heavy WebGL with a good LCP is the mark of someone who knows what they're doing — more on that in Core Web Vitals for animation-heavy sites.
• 🔴 Deflects, or their showcase site scores in the red.

Timeline & cost

"What's a realistic timeline, and what drives it?"

• 🟢 A range tied to scope, plus the dependencies that move it (content readiness, rounds of feedback, motion complexity).
• 🔴 A suspiciously exact date with no conditions — or a refusal to estimate at all.

"How do you price — fixed, milestone, or hourly — and what's included?"

• 🟢 A clear structure with deliverables, revision rounds, and what counts as extra. Independent creative developers typically run ~$75–100/hr, with project tiers commonly starting around $1,500–$3,000+ and scaling with motion and WebGL complexity.
• 🔴 A single number with no breakdown, or a quote far below market — cheap almost always means a template with the serial numbers filed off. For the full picture, see how much an animated website costs.

"What would you cut first if we had to fit the budget?" A great question to ask them — it reveals how they prioritize.

• 🟢 Protects the one or two moments that matter, trims the decorative rest. Outcome-thinking.
• 🔴 Everything is essential, or they'd cut the wrong thing (the hero, the performance work).

Ownership, handover & maintenance

The part everyone forgets until launch week — and where lock-in is born.

"Who owns the code and the accounts when we're done?"

• 🟢 You do. Repo, hosting, domain, and CMS in your name, transferred at handover.
• 🔴 "It lives on my account / my platform." A site you can't take with you is a leash.

"How will my team edit content after launch?" A build only the developer can update is a liability.

• 🟢 A real CMS your non-technical team can use, plus a short walkthrough or Loom at handover.
• 🔴 "Email me and I'll change it." That's a recurring invoice disguised as a feature.

"What does support look like after launch, and what does it cost?"

• 🟢 A defined window for fixes, plus a clear retainer or hourly rate for ongoing work.
• 🔴 No plan — you find out the relationship is over the first time something breaks.

"What happens if we want to keep building next year — or work with someone else?"

• 🟢 Clean, documented code and a handover doc; they're confident another dev could pick it up.
• 🔴 Defensiveness, or code so bespoke nobody else can touch it. Job security for them is lock-in for you.

The short version (copy-paste checklist)

Group	The one question that matters most
Portfolio & craft	"Can I open your live work on my phone — and which parts did you build?"
Process & comms	"How and how often will we communicate, and what do you need from me?"
Motion & performance	"How do you keep this at 60fps on a mid-range Android?"
Timeline & cost	"How do you price, and what would you cut first to fit budget?"
Ownership & handover	"Who owns the code and accounts, and how does my team edit content?"

If you want the full buyer's playbook around these questions, read how to hire a creative developer, and to decide whether a freelancer, studio, or platform fits at all, see creative developer vs. templates vs. Webflow vs. an agency.

FAQ

What is the most important question to ask before hiring a web developer?

"Can I open your live work on my own phone right now?" It validates the portfolio in seconds — live performance can't be faked, and how a site feels on real hardware is the entire point of hiring a creative developer rather than a templater.

How do I know if a developer is overcharging or undercharging?

Calibrate against the market: independent creative developers typically run ~$75–100/hr, with projects commonly starting at $1,500–$3,000+. A quote far below that usually signals a template build; far above usually means agency overhead. Either way, ask for a deliverable breakdown — see the pricing guide for ranges by scope.

What questions reveal a developer who will lock me in?

Ask who owns the code, repo, domain, and CMS at handover, and how your team edits content without them. If the answer is "it lives on my account" or "email me to make changes," you're being set up for a dependency, not handed a deliverable.

Should I ask the same questions of an agency and a freelancer?

Yes — but add one for agencies: "Will the senior who pitched be the one building?" Many agencies subcontract motion and WebGL to a specialist creative developer anyway, so you may be paying overhead for the exact skill you could engage directly.

---

Let's talk about your project

I'm Hon Tran — a creative developer and Awwwards jury member with 11+ years building award-winning experiences for founders, agencies, and brands across Europe, the Middle East, and Asia. If you're running these questions past candidates, I'm happy to be one of them.

Browse the projects archive for live work, see what I offer and how engagements run, and when you're ready, let's talk.