Hire an Astro developer: what to look for

When a general web developer is not enough

Honesty first: for a simple brochure site with a handful of pages, a good generalist is enough. You do not need a specialist to publish five pages of company information. The guide to hiring a web developer covers that decision, and everything there about portfolios, references and ownership applies here too.

An Astro specialist’s expertise can justify the extra cost when your project relies on Astro’s particular strengths:

• Island architecture. Astro renders most of a page to static HTML. It adds small islands of JavaScript only where you need interactivity, as the Astro documentation on islands explains. Partial hydration is a deliberate choice, not a default you get for free. A specialist can explain which islands your site needs and why the rest stays plain HTML.
• Content collections as a content model. Your content can live in Git as MDX and JSON or in a headless CMS. Either way, a specialist designs the collections, schemas, and relationships so editors can work without breaking the build.
• E-commerce with Astro. The storefront frontend and the checkout architecture are separate decisions. A specialist knows where Astro ends and where a dedicated checkout or platform begins.

The Astro team describes the pattern like this:

If your project is really an application — signed-in users, shared state, server logic — the decision changes. Astro vs. Next.js walks through that comparison; a trustworthy Astro developer will tell you the same thing and sometimes advise against their own specialty.

What to look for in an Astro developer’s portfolio

A portfolio is evidence, not decoration. Four things I check when I review another developer’s Astro work:

• Live Astro sites, not mockups. Open two or three on your phone. Click around, use the forms, watch how fast pages load. A static website that feels heavy on a phone was not built with much care, whatever the framework.
• A source check anyone can do. Right-click, view source. An Astro page should be mostly readable HTML, not a skeleton filled by JavaScript after loading. A large script payload deserves questions: it may come from interactive islands, analytics, or third-party embeds. Ask what each script does and whether it is needed on that page.
• Measured performance. Ask for numbers, not adjectives. A specialist has PageSpeed runs or Core Web Vitals data for the sites they built, and can tell you what they changed when a metric regressed.
• Community contributions. Astro has an active open source ecosystem. Some developers publish integrations, answer questions in the community, or contribute to the framework. Their work is public, so you can read how they think before you ever email them.

Ask about their role in each project, too. “The client had their own designer; I built the frontend and the integrations” is an honest answer. Vaguely claiming credit for everything on the screen is not.

General web developer or Astro specialist

The choice depends on the project, not on the job title. This is how I frame it for clients:

Start with a performance audit

A specialist starts by measuring, not by proposing a redesign. Ask what a candidate measures before the build and after it. A serious answer names a baseline: current load times, Core Web Vitals, and search visibility. It also includes regular measurements after launch, so you can see whether the new site does what it promised.

That is how I work on my own projects. The production sites in the portfolio get monthly PageSpeed and Search Console measurements, and I publish the results per case. You can check that claim instead of taking my word for it — the numbers live in the case studies. One example: the Verhuurwinkel online store scored 99/100 for mobile PageSpeed in the measurement of September 17, 2026, and its LCP for Chrome users (p75) was 0.7 seconds. Whoever you hire, ask for that same loop: measure, build, measure again.

Speed promises without measurements are marketing. A baseline plus a follow-up measurement is a commitment.

Questions to ask before you hire

Five questions that surface real expertise in a first conversation:

• Which live Astro sites have you built, and what exactly was your role in each?
• How do you keep the JavaScript footprint small — which components become islands, and which stay plain HTML?
• How do you set up content management: content collections in Git, a headless CMS, or a combination?
• Who can take over the code later — is this a standard Astro setup another developer recognizes?
• What do you measure after launch, how often, and what happens when a number regresses?

The content-management question matters more than it might seem. Your site will outlive the build phase, and the person updating it in two years should not need a developer for every paragraph. A specialist has an opinion on this and can defend it.

Red flags when hiring an Astro developer

The patterns I would walk away from:

• Astro sold as the answer to everything. Astro supports server-rendered routes, but a state-heavy application needs a different assessment from a marketing site. Ask how the proposed stack handles authentication, shared state, and server logic rather than ruling it in or out by framework name.
• No live sites to show. Mockups and screenshots are presentations; you want URLs you can open and test yourself.
• Speed promises without measurements. “It will be fast” is not a plan. Ask for the baseline and the follow-up.
• No maintenance arrangement. “We will figure that out later” in practice means never. Frameworks, dependencies and hosting keep moving after launch.
• Lock-in through custom “systems.” A custom layer only the builder understands is a relationship without an exit. Standard Astro with content in a place you own is the opposite.

Every red flag has the same remedy: ask for the evidence behind the claim, in a form you can check without technical knowledge.

How to compare Astro project quotes

I publish no rates — the scope determines the price, and a number without scope is noise. What I can give you is a framework for comparing quotes.

Only compare quotes when the scope description is identical: same pages, same integrations, same content work, same arrangements for after launch. Otherwise you are comparing different products that happen to share a name. Ask each candidate whether they quote a fixed project price or work at an hourly rate, and exactly what the quote includes.

Three things drive the cost of an Astro project. The first is content volume: how many pages and templates you need. The other two are integrations, such as a CMS, forms, checkout, or search, and custom work beyond the framework’s standard patterns. The budget frameworks in website development costs apply here unchanged — what holds for judging a quote there holds for an Astro quote too.

Where to find an Astro developer

Three channels, each with its own evidence:

• The Astro community. The framework’s open source ecosystem — integration authors, theme builders, developers answering questions in public — is where specialists are visible before you hire them. You can read how someone explains a problem before you ever speak to them.
• Their own site. An Astro specialist’s own website is the cheapest portfolio check there is. If it is slow, heavy or poorly maintained, take that seriously.
• Your network. A supplier or partner who had a good experience with an Astro project can tell you about the collaboration, which a portfolio cannot.

And the direct route: I build Astro sites for clients myself, starting from measurement rather than assumptions. The service page linked in the introduction explains that approach — and if your project turns out to need something else, I will tell you that too. For broader hiring advice, hiring a web developer remains the general starting point.