Senior Next.js Developer: Data-Driven Marketing Site

About us We run a golf tee box sponsorship business across 52 courses in the UK and US, with 800+ live sponsorships. Local businesses sponsor a hole at their local club and get their branding on the tee box. The work A new public site, replacing our current Shopify one. This is not a brochure — it's a live, data-driven site where the content sells. 52 course pages, each pulling live from Airtable: photos, current sponsors, remaining hole availability Live business figures — courses, sponsors, holes remaining — read at request time, never cached stale Map of all courses, each linking to its own page Postcode and ZIP search for "courses near me" Separate journeys for businesses wanting to sponsor and for golf clubs wanting to partner Testimonials and social proof throughout UK and US, with region-appropriate formatting The site's job is conversion. Someone arrives from a Meta ad for their local club and should be convinced by the time they reach the form at the bottom of the page. Required: -Next.js (App Router) and TypeScript, deployed on Vercel -Server-side data fetching at request time. Hole availability changes by the minute. A scheduled sync into a CMS will not work — we cannot show a hole as available an hour after it sold. -Airtable API experience, or comparable -Mapping and geocoding — Mapbox or Google Maps -Core Web Vitals and SEO — this is our primary sales channel, performance is commercial not cosmetic -Mobile-first. Almost all traffic is Meta ads on phones. -Strong visual design judgement, or a designer you work with Also required — please confirm explicitly: -We own the code outright and can host it anywhere. No proprietary CMS. -Path-level rewrites must be possible, so a route such as /join can be served by a separate application we run. Please answer in your application: 1.Link me to a data-driven site you've built where content comes from an external source. How would you architect live inventory availability across 52 pages without hammering the API or serving stale data? 2.How do you approach performance on an image-heavy, mobile-first site?