Senior Astro/TypeScript Developer — Existing Component Reuse, CMS, SEO & QA

We are hiring a senior web developer to build a second production website for a regional real-estate brokerage office by reusing and adapting an existing production Astro website/component library. This is a specification-driven implementation project, not a greenfield design exercise and not a WordPress/Webflow build. The project already has a detailed requirements package with locked page architecture and copy, annotated visual-fidelity standards, reusable component expectations, CMS content models, SEO/meta/schema rules, form/integration requirements, deployment controls, performance targets, and an evidence-based final acceptance matrix. A separate full-site Figma reconstruction is not expected. Core stack / skills: Astro + TypeScript / modern front-end architecture Git/GitHub and disciplined component reuse Git-based CMS experience (Decap or equivalent) DigitalOcean App Platform and Cloudflare GA4 / Search Console / technical SEO / JSON-LD schema Cloudflare Turnstile + server-side form validation + webhook integrations Playwright or equivalent browser/E2E testing Lighthouse / Core Web Vitals / accessibility Modern AI-assisted coding/testing workflow (Claude Code, Codex, Cursor, Copilot, etc.) used for efficiency with human review and QA Representative launch scope: Homepage built first as the visual master and owner-approval gate Core editorial pages and reusable page families Areas Served index + five city pages Professionals directory + data-driven professional profile template Marketing portfolio Client reviews carousel Curated featured-properties carousel + static grid page Referrals, Careers, Contact, Resources, Search shell, legal/utility pages CMS create/edit/publish workflows Forms, validated webhook handoff, analytics events, SEO/schema, responsive behavior, accessibility, performance, production deployment and handoff Important scope boundaries: No custom IDX No custom listing-detail platform No full-site Figma redesign No separate parallel design system when existing donor components can be reused Owner supplies approved copy and media; developer is not being hired to invent the brand or write the site from scratch Quality expectations are material. Before each owner-review milestone, the developer must complete automated + manual QA. Final acceptance includes production build, responsive/browser review, CMS workflows, form/integration testing, analytics-event verification, broken-link review, technical SEO/schema, accessibility, Lighthouse/Core Web Vitals evidence, ownership/handoff, and a formal PASS/FAIL acceptance matrix. Availability: Worldwide candidates are welcome. We require strong written English and approximately 3 hours of working-time overlap with U.S. Eastern Time on normal development days for communication and milestone review. Candidate process: Submit a structured preliminary proposal answering the questions below. Shortlisted candidates interview through Upwork. The top 2–3 candidates may be offered a small paid repository/specification audit under an Upwork contract. After that audit, finalists submit a firm fixed-price proposal with phase hours, schedule, assumptions/exclusions, and reuse map. We prefer a senior individual freelancer. A small agency is acceptable only if the named senior developer in the proposal will personally perform the core implementation and QA. Please answer every question below in your proposal: Show one or two recent Astro/TypeScript projects most relevant to this work and state exactly what you personally implemented. Based on the scope above, what do you expect to be the three highest-effort or highest-risk areas, and why? How would you audit and reuse an existing Astro component library without creating unnecessary duplicate components or leaking donor-site branding/configuration into the new site? Describe your AI-assisted development/testing workflow. Give one concrete example of what the AI accelerated and what you personally verified before production. Give your preliminary estimate of total labor hours, elapsed calendar weeks, and fixed-price range before repository audit. State your assumptions. Identify one requirement you would challenge, simplify, or implement differently, if any, and explain why. Budget note: The budget shown in Upwork is a planning placeholder, not a target bid. Provide your independent estimate. We will evaluate technical fit, reuse strategy, QA discipline, communication, and total value—not lowest price.