How to Interview a Potential Web Developer

Choosing a web developer is a business decision, not simply a search for someone who can make a page look attractive. The right person should understand your customers, translate your goals into a practical website and explain technical decisions in language you can use. They should also be dependable after launch, when updates, security checks and small changes become part of normal operations.

For an Australian small business, the conversation should cover more than design style and a quoted price. Your site may need to support local search in Brisbane, bookings from Melbourne, enquiries across regional New South Wales or online sales throughout the country. A structured interview helps you identify the developer who can build a useful digital asset rather than deliver a short-lived brochure site.

Clarify Your Business Goals First

Before speaking with a developer, write down what the website needs to achieve. You might want more qualified phone calls, online bookings, quote requests, retail sales or stronger credibility for a professional service. A developer cannot recommend the right pages, platform or functionality until these outcomes are clear.

Ask candidates how they would turn your goals into website features. A strong answer may include a clear navigation structure, prominent calls to action, landing pages for specific services and a way to measure enquiries. It should connect design choices with customer behaviour instead of focusing only on colours, animations or personal preferences.

Ask which information they need from you before preparing a proposal. Useful questions may cover your ideal customer, competitors, existing marketing, brand materials, photography, busiest seasons and areas served. A local electrician in Adelaide may need service-area pages and urgent contact options, while a boutique retailer in Sydney may need product filters, delivery information and an efficient checkout.

Examine Their Discovery And Design Process

Find out whether the developer begins with research and planning or moves straight into a template. Ask how they learn about your audience, what they include in a sitemap and how they decide which content belongs on the home page. Their process should make room for your expertise because you understand your products, customers and daily operations better than an outside supplier.

Ask to see examples of custom-built sites and request an explanation of the decisions behind each project. You are looking for evidence of clear hierarchy, readable typography, sensible mobile layouts and consistent calls to action. A portfolio full of visually impressive home pages tells you less than a case study showing how a site solved a real business problem.

Discuss content responsibilities early. Some developers write or edit copy, source images and prepare basic search engine optimisation, while others expect the client to provide every word and photograph. Ask who will create page titles, service descriptions, image captions and metadata, and whether the work is included in the proposal. A site aimed at Australian customers should also use familiar spelling, currency and local terminology.

Test Their Communication And Project Management

Ask who will be your main contact and how communication will work during the build. Some studios use email and scheduled video calls, while others manage tasks through a project platform. The method matters less than having a reliable process for approving content, recording decisions and resolving questions.

Ask for a typical timeline with milestones such as discovery, wireframes, visual design, development, content entry, testing and launch. A vague promise to finish “quickly” is less useful than a staged schedule with clear responsibilities. Confirm how long you usually have to provide feedback and what happens if content or approvals arrive late.

Clarify how revisions work. Find out how many design rounds are included, whether minor text changes are treated differently from structural changes and how additional work is priced. This is especially important for a small business owner who may be balancing the project with trading hours, school holidays or a busy period such as the lead-up to Christmas.

Signals Of A Well-Run Process

Use these points to focus the conversation:

• A written scope links features to business goals.
• Milestones identify approvals, deadlines and owners.
• Feedback is collected in one clear, trackable place.
• The developer explains trade-offs without using jargon.

Ask Technical Questions In Plain English

You do not need to test a developer’s coding knowledge, but you should understand how the website will be built and maintained. Ask which content management system, framework or ecommerce platform they recommend and why it suits your needs. The answer should reflect your budget, editing requirements, expected traffic and future plans.

Ask whether the site will be responsive, accessible and tested across current browsers and screen sizes. Australian customers often browse on mobile devices while travelling, comparing services or standing in a shop. A practical developer should discuss readable text, keyboard navigation, image descriptions, contrast, fast loading and forms that work without frustration.

Security and ownership deserve direct questions. Ask who controls the domain name, hosting account, website files, analytics property and business email. Confirm that these accounts can be transferred if you later change suppliers. Ask how software updates, backups, malware monitoring and SSL certificates are handled, and whether ongoing maintenance is included or charged separately.

If your website collects names, email addresses, phone numbers or payment details, ask how that information is protected and where it is stored. You should also discuss privacy policies, cookie notices and compliance responsibilities with an appropriate Australian adviser. A developer who explains the limits of their role clearly is more trustworthy than one who casually promises legal compliance.

Explore Features, Forms And Ongoing Support

Forms are often the main route from a website visit to a real enquiry, so ask how they will be designed, tested and delivered. Discuss required fields, spam prevention, confirmation messages, notification recipients and what happens if an email fails. A polished website is of little value if a contact request disappears into an inbox nobody monitors. A useful guide to a simple contact form can help you recognise the practical details that should be discussed.

Ask what happens after launch. Find out whether you will receive training, written instructions or access to make routine changes yourself. Confirm the response time for urgent problems, the cost of content edits and whether support is available during Australian business hours. If your customers are in Perth and your developer operates on the east coast, agree on realistic communication windows.

Consider how the website can grow. You may begin with a few service pages and later add online booking, a knowledge base, customer reviews or ecommerce. Ask whether the proposed platform can support those plans without forcing an expensive rebuild. At the same time, avoid paying for speculative features that will not help your business in the next year.

A hands-on builder may also be comfortable explaining how separate parts work together. For example, the detailed electronics journal from Project Astromech demonstrates the value of documenting components, connections and practical decisions. That same habit of clear explanation is useful when a developer discusses hosting, integrations or website functionality with a non-technical client.

Compare Value, Cost And Ownership

Request a written proposal that separates the initial build from recurring expenses. Look for design, development, copywriting, photography, hosting, domain registration, plugins, licences, testing, launch and training. Ask whether prices include GST and whether the quoted amount is fixed, estimated or dependent on hourly work. Comparing like with like is difficult when one proposal includes content and support while another includes only a basic build.

Ask what happens if the project changes direction. A fair agreement should explain how new pages, integrations or rounds of revisions are approved and billed. You should also understand cancellation terms, payment stages and the point at which ownership of the finished work transfers to you.

Do not choose by price alone, but do treat an unusually low quote as a prompt for investigation. It may reflect an efficient process, or it may exclude essential work such as mobile testing, content preparation, accessibility checks or post-launch support. A higher fee can be justified when it buys thoughtful strategy, tailored development and a site that remains manageable for years.

Weigh Evidence Before You Appoint Anyone

After interviews, score each candidate against the same criteria. Record what they promised, what they asked about your business and how clearly they explained limitations. Check references where possible, especially from businesses similar in size or complexity. A recommendation from a nearby trade business, community organisation or professional practice can reveal how the developer behaves after receiving the deposit.

The strongest candidate will usually make you feel informed rather than impressed by technical vocabulary. They will identify risks, challenge unnecessary features and show how the website supports sales or service delivery. They should also be comfortable discussing Australian conditions such as GST, local search, privacy expectations and the needs of customers using mobile connections outside major cities.

Use the comparison below to distinguish useful evidence from warning signs during your assessment.

Area to assess	Weak indication	Reassuring indication
Business understanding	Talks mainly about appearance and templates	Connects pages and features with customers and outcomes
Scope	Gives a single price with little detail	Provides deliverables, exclusions, milestones and assumptions
Communication	Promises constant availability without a process	Sets response times, meeting points and feedback procedures
Technical quality	Avoids questions about ownership, security or testing	Explains hosting, backups, accessibility and account access
Content	Assumes the client will “sort it out” later	Defines responsibility for copy, images, SEO and approvals
Support	Treats launch as the final handover	Offers training, maintenance options and a clear support path

Before signing, make sure the agreement names the decision-maker on your side and the person responsible on the developer’s side. Confirm the launch criteria, access credentials, backup arrangements and handover materials. These details may feel administrative, but they prevent confusion when a site is ready to go live or needs attention months later.

A careful interview gives you more than a shortlist. It shows whether the developer listens, plans realistically, communicates openly and takes responsibility for the complete website experience. Those qualities matter whether your business serves one suburb in Canberra or customers across every Australian state and territory.