— Door 01 · Application Materials

Application package + live audit of all four NDOT flagship sites.

Built for Blayze Thomas and the NDOT hiring team. Everything below is verifiable in your terminal — I've included the exact curl commands so you can run the audit yourself.

Applicant
Khalid Rind
NeuraNest AI · Melbourne
Role
Campaign Website Lead
NDOT · 0.8 FTE · to April 2027
Source
EthicalJobs
Applied 18 May 2026
Trial offer
$95/hr · 2 weeks
Audit + roadmap for one campaign

Why Melbourne is not a blocker

NDOT already coordinates fundraising delivery across every state and territory Cancer Council. The work is federation-wide by definition — stakeholders are everywhere, the supplier ecosystem (Funraisin, your design and dev partners) is geography-agnostic, and AEST is AEST whether I'm typing from Melbourne or Sydney. I'm offering to fly up monthly for stakeholder workshops on my own time, and I can be in Sydney within 90 minutes wheels-up to wheels-down.

Live audit of all 4 NDOT flagship sites

Run this morning, 18 May 2026, from a Melbourne residential IP. Method: curl -sIL --max-time 12 -o /dev/null -w "%{http_code} %{time_starttransfer}s". Five real findings below — three quick wins, one critical, one validation of existing strength.

— Finding 01 · Critical
The Longest Day — no response to HEAD request within 12 seconds
A baseline reachability check (curl -sIL --max-time 12 https://thelongestday.org.au/) returned 000 from my Melbourne residential connection. The site may be behind region-restricted or aggressive bot-protection rules, or it may have been temporarily unavailable. Either way — when I as a prospective donor click your URL and wait 12 seconds for a response, I leave.
What I'd do day one: reproduce from three vantage points (Sydney AWS, Melbourne residential, mobile 4G), brief the supplier, scope a fix before the next campaign window. If it's bot-protection, audit the rule set against legitimate donor user-agents.
— Finding 02 · TTFB
Daffodil Day & Biggest Morning Tea — slow time-to-first-byte
Daffodil Day TTFB 2.07s; Biggest Morning Tea TTFB 2.52s. Google's "good" threshold for CDN-served sites is <800ms. Both well above. On a donor's mobile data this compounds — the difference between TTFB 0.5s and TTFB 2.5s is roughly a 15–20% drop-off in completed visits per Google's own field data.
What I'd do: audit Funraisin's CDN config, server location, and any third-party scripts loading before render. Target: under 1.2s TTFB on both sites before the August Daffodil Day cycle.
— Finding 03 · Win
Relay for Life — TTFB 0.43s (well managed)
Relay's TTFB of 0.43s proves your platform CAN deliver fast first-byte. The performance variation across the four sites (0.43s → 2.52s → timeout) suggests inconsistent hosting/CDN configuration across what should be a shared Funraisin tenancy.
What I'd do: use Relay's config as the baseline pattern, document the delta against Daffodil Day & ABMT, propose a unified hosting profile. This is a stakeholder-management problem, not a code problem.
— Finding 04 · SEO
Date-bound titles — good SEO discipline, opportunity for AI-search
Both <title> tags carry the campaign year/date (Daffodil Day 2026; Biggest Morning Tea | 21 May 2026). This is the correct call for time-bound campaigns — current campaign wins organic. The opportunity: structured-data + AI-search readiness so when someone asks ChatGPT or Perplexity "when is Daffodil Day this year", your page is cited.
What I'd do: ensure FAQPage and Event schema on every campaign site, add an LLMs.txt and llms-full.txt manifest, structure the date answer above the fold in plain text (LLMs scrape text, not images).
— Finding 05 · Conversion
Meta descriptions — within spec, missing impact data
Both Daffodil Day & ABMT meta descriptions are tasteful, brand-aligned, well under 160 chars. They focus on the action ("join", "donate", "hold a morning tea"). What's missing in the SERP snippet itself is the why — the impact-per-dollar number that converts a casual click into a committed visit.
What I'd test: A/B in the SERP snippet — current vs. a variant that includes a specific impact stat. Run for one cycle, measure CTR delta from Google Search Console, escalate or roll back.

Why these findings matter

Three of the four campaigns are within a 12-week window of their 2026 peak (ABMT May, Longest Day June, Daffodil Day August). A new Lead arriving in June has roughly six weeks to take the audit above from "interesting list" to "concrete improvements live before the campaign peak". I've already done the hard part — the audit itself — so we start day one with shared evidence rather than discovery.

Documents (PDF)

CV — mid-level expert positioning
Khalid-Rind-CV-2026-05-18.pdf
3 pages · 128 KB · ATS-friendly · attached to email
Cover letter — addressed to Blayze
Khalid-Rind-CCNSW-Cover-Letter.pdf
2 pages · written specifically for this role · attached to email

The trial offer (in one sentence)

If the application alone isn't enough to commit, I'll take a paid two-week trial at AUD $95/hr (4 days/week) with a single deliverable: a full audit + 90-day improvement roadmap for the campaign of your choice. End of week two you have data to decide with, I have evidence to be hired on, and there's no sunk cost on either side.

Next step is one 20-minute call.

Then either the application is enough, or we run the paid trial. Either way, low risk for NDOT.

Book the call →