{
  "schemaVersion": 2,
  "name": "Hiring",
  "slug": "hiring",
  "blocks": ["Pages", "Lists: forms"],
  "persona": "startups",
  "keywords": [
    "careers page",
    "jobs",
    "job board",
    "hiring",
    "job applications",
    "open roles",
    "apply",
    "recruitment",
    "work with us",
    "startup jobs",
    "route planning jobs",
    "careers site"
  ],
  "description": "A careers page and job board for a startup: open roles grouped by team with location, working pattern and salary, a role page for each one, and an application form that takes a CV or LinkedIn link.",
  "audience": [
    "startup founders hiring their first team",
    "people teams running a careers page",
    "managers who want a simple way to take applications"
  ],
  "category": "SaaS & startup",
  "job": "startup",
  "categoryId": "saas",
  "alsoFits": [
    "careers page",
    "job board",
    "recruitment",
    "software company",
    "hiring page"
  ],
  "direction": "Chart room: deep navy, signal orange, teal chart-paper grid, route lines and pins drawn in SVG, a grotesk for headlines and a mono for metadata",
  "mood": [
    "dark",
    "bold",
    "modern"
  ],
  "schemaOrg": "Organization",
  "palette": {
    "--bg": "#0B1624",
    "--ink": "#EEF3F7",
    "--accent": "#FF7A1A"
  },
  "fonts": [
    "Hanken Grotesk",
    "JetBrains Mono"
  ],
  "pages": [
    {
      "path": "index.html",
      "label": "Home",
      "purpose": "Mission, why join, the first open roles from the roles list, a benefits snapshot and the apply call to action"
    },
    {
      "path": "roles.html",
      "label": "Open roles",
      "purpose": "Every open role from the roles list, grouped by team, with location, working pattern and salary"
    },
    {
      "path": "roles/_item.html",
      "label": "A role",
      "purpose": "Item page: one role with its summary, the facts, the full description and an apply button, at roles/<slug>"
    },
    {
      "path": "life.html",
      "label": "How we work",
      "purpose": "Hybrid office days, time off, learning budget, parental leave, equipment and the four-step hiring process with honest timelines"
    },
    {
      "path": "apply.html",
      "label": "Apply",
      "purpose": "The application form slot with an email fallback: role, name, email, CV or LinkedIn link, why us, right to work, and how they heard"
    }
  ],
  "slots": [
    {
      "id": "apply",
      "kind": "form",
      "page": "apply.html",
      "fallback": "mailto"
    }
  ],
  "facts": [
    "company name, office address and postcode",
    "phone number and careers email address",
    "team names and the roles open now (title, team, location, working pattern, salary range, summary and description)",
    "holiday, learning budget, parental leave and equipment policies",
    "hiring steps and their real timelines",
    "the Head of People and the applicant privacy contact"
  ],
  "interview": [
    "What is the company called, and where is the office?",
    "Which teams are hiring, and what are the open roles, with salary ranges?",
    "How many office days a week do people do, and how many days of holiday do you give?",
    "What do your hiring steps look like, and how long does each one take?",
    "Who reads applications, and how long do you keep them before deleting them?",
    "Do you want applicants to send a CV link, a LinkedIn link, or both?"
  ],
  "customise": {
    "strings": [
      "Company name 'Tidewater Labs' in every <title>, the header and footer, the JSON-LD and the privacy notice",
      "Office address '5 Gantry Wharf, Selbury Docks QX9 1PT' in the footer, life.html, privacy.html and the JSON-LD",
      "Careers email careers@tidewaterlabs.example.com and phone 01632 960 853 in the footer, apply.html, privacy.html and the empty state of index.html",
      "Head of People 'Ama Rosenthal-Kwarteng' in life.html and privacy.html",
      "Roles: edit them as items of the roles list (title, team, location, working pattern, salary, summary, description, closing, search fields); the team sections on roles.html and the role choices on apply.html follow the same titles"
    ],
    "colours": "Edit the :root tokens at the top of styles.css; also replace the matching hex values in art/*.svg and favicon.svg",
    "fonts": "Change the Google Fonts <link> on every page and --font-sans / --font-mono in styles.css",
    "sections": "Each page is self-contained; keep the header, footer and the apply slot on apply.html",
    "images": "Replace art/route-hero.svg (1600×1000, the route map) and art/wharf.svg (1600×1000, the quay); keep the 16:10 frame and data-pl-photo notes; WebP under 300 KB"
  },
  "files": [
    "index.html",
    "roles.html",
    "roles/_item.html",
    "roles/senior-backend-engineer.html",
    "roles/frontend-engineer-dispatch.html",
    "roles/product-manager-dispatch.html",
    "roles/product-designer.html",
    "roles/customer-success-lead.html",
    "roles/operations-finance-coordinator.html",
    "life.html",
    "apply.html",
    "privacy.html",
    "404.html",
    "styles.css",
    "script.js",
    "favicon.svg",
    "og.png",
    "apple-touch-icon.png",
    "art/route-hero.svg",
    "art/wharf.svg"
  ],
  "updated": "2026-10-21",
  "visuals": {
    "notes": "Dark navy chart room. The illustrations are self-hosted SVG frames in art/: a route map with two delivery routes, numbered stop pins and an ETA box on a teal chart grid, and the quay at Gantry Wharf at dusk with a gantry crane in orange. Colours are literal hex values in the files.",
    "prompt": "Draw a flat SVG chart room: a navy grid with teal chart-paper lines, two signal-orange route lines through numbered stop pins, and a small ETA box."
  },
  "lists": [
    {
      "name": "roles",
      "label": "Open roles",
      "pages": [
        "index.html",
        "roles.html",
        "roles/_item.html"
      ],
      "fields": [
        {
          "name": "title",
          "type": "text",
          "label": "Role title"
        },
        {
          "name": "team",
          "type": "text",
          "label": "Team"
        },
        {
          "name": "location",
          "type": "text",
          "label": "Location"
        },
        {
          "name": "type",
          "type": "text",
          "label": "Working pattern"
        },
        {
          "name": "salary",
          "type": "text",
          "label": "Salary"
        },
        {
          "name": "summary",
          "type": "text",
          "label": "Summary (one line on the list)"
        },
        {
          "name": "body",
          "type": "rich_text",
          "label": "Role description"
        },
        {
          "name": "closing",
          "type": "text",
          "label": "Closing"
        },
        {
          "name": "seo_title",
          "type": "text",
          "label": "Search title"
        },
        {
          "name": "search_summary",
          "type": "text",
          "label": "Search and share summary"
        }
      ],
      "items": [
        {
          "slug": "senior-backend-engineer",
          "title": "Senior backend engineer, route planning",
          "team": "Engineering",
          "location": "Selbury Docks, hybrid",
          "type": "Full-time",
          "salary": "£70,000–£82,000",
          "summary": "Own the routing engine that plans every van's stops, time windows and road closures before the dispatcher's first coffee.",
          "body": "<h2>What you&#39;ll do</h2><ul><li>Design and run the routing engine that every customer&#39;s morning plan depends on.</li><li>Pick the right trade-off between speed and accuracy when a dispatcher needs a plan in seconds.</li><li>Review the code of the people you work with, and write down why a choice was made.</li><li>Work with the customer success team when a route looks wrong, and find out why.</li></ul><h2>What you&#39;ll bring</h2><ul><li>Several years of backend work in production, including at least one system that had to be right every time.</li><li>Comfort with graphs, scheduling or optimisation, and an honest view of what a heuristic can and cannot do.</li><li>Clear written updates, because most of your work is read by people who are not engineers.</li></ul><h2>Nice to have</h2><ul><li>Experience with logistics, mapping data or a fleet product.</li><li>Time on a dispatch desk, or driving a route yourself.</li></ul><h2>How we hire</h2><p>Four steps, the same for every role: an application read within five working days, a 30-minute intro call, a paid task of about three hours, then a final conversation. The How we work page sets out the timelines.</p>",
          "closing": "Open until filled",
          "seo_title": "Senior backend engineer, route planning · Tidewater Labs",
          "search_summary": "Senior backend engineer role at Tidewater Labs, Selbury Docks: own the route-planning engine small courier firms run each morning. Hybrid."
        },
        {
          "slug": "frontend-engineer-dispatch",
          "title": "Frontend engineer, dispatch app",
          "team": "Engineering",
          "location": "Remote, UK",
          "type": "Full-time",
          "salary": "£55,000–£65,000",
          "summary": "Build the dispatch screens that drivers and dispatchers use on busy mornings, on a laptop and on a phone at the kerb.",
          "body": "<h2>What you&#39;ll do</h2><ul><li>Build and test dispatch screens in TypeScript and React, from the first sketch to the release.</li><li>Make the map and the timeline fast on an older phone, because drivers use them standing at the kerb.</li><li>Work with the designer on the details, and say so when a design cannot be built well in the time.</li><li>Look at the error logs with the team every week and fix the ones that cost a dispatcher time.</li><li>Work from anywhere in the UK, with a team day at Gantry Wharf once a quarter, travel paid.</li></ul><h2>What you&#39;ll bring</h2><ul><li>Several years of frontend work, with at least one product that people used every day.</li><li>A clear sense of accessibility, including keyboard use and text that stays readable in a van.</li><li>Patience with the detail, and a habit of writing down what you changed and why.</li></ul><h2>Nice to have</h2><ul><li>Experience with maps, charts or real-time data.</li><li>Time spent building for a mobile-first audience.</li></ul><h2>How we hire</h2><p>Four steps, the same for every role: an application read within five working days, a 30-minute intro call, a paid task of about three hours, then a final conversation. The How we work page sets out the timelines.</p>",
          "closing": "Open until filled",
          "seo_title": "Frontend engineer, dispatch app, remote UK · Tidewater Labs",
          "search_summary": "Frontend engineer role at Tidewater Labs: build the dispatch app courier firms use on busy mornings. Remote within the UK, with a few days a year in Selbury Docks."
        },
        {
          "slug": "product-manager-dispatch",
          "title": "Product manager, dispatch",
          "team": "Product",
          "location": "Selbury Docks, hybrid",
          "type": "Full-time",
          "salary": "£58,000–£68,000",
          "summary": "Decide what the dispatch desk gets next, by spending a week a month in the depot with the people who use it.",
          "body": "<h2>What you&#39;ll do</h2><ul><li>Own the roadmap for the dispatch product, and explain each choice to the customers it affects.</li><li>Spend time with dispatchers and drivers, and write up what you saw before you decide anything.</li><li>Shape the work with engineering and design, from the first problem statement to the release.</li><li>Decide what not to build, and tell the customers who asked for it why.</li></ul><h2>What you&#39;ll bring</h2><ul><li>Experience managing a software product that people use at work, ideally in logistics or operations.</li><li>Good judgement about trade-offs, and the habit of checking a decision after it ships.</li><li>Clear writing, because the best product decisions here are written down.</li></ul><h2>Nice to have</h2><ul><li>Time on a dispatch desk, a fleet, or a small courier firm.</li><li>Experience with pricing or with onboarding new customers.</li></ul><h2>How we hire</h2><p>Four steps, the same for every role: an application read within five working days, a 30-minute intro call, a paid task of about three hours, then a final conversation. The How we work page sets out the timelines.</p>",
          "closing": "Open until filled",
          "seo_title": "Product manager for dispatch software · Tidewater Labs",
          "search_summary": "Product manager role at Tidewater Labs in Selbury Docks: set the direction for the dispatch product small courier firms use every morning. Hybrid."
        },
        {
          "slug": "product-designer",
          "title": "Product designer",
          "team": "Design",
          "location": "Selbury Docks, hybrid",
          "type": "Full-time",
          "salary": "£52,000–£60,000",
          "summary": "Design the map and timelines so a dispatcher can read a whole day's plan at a glance.",
          "body": "<h2>What you&#39;ll do</h2><ul><li>Design the map, timeline and driver screens, from the first sketch to the finished component.</li><li>Test your work with dispatchers in the depot, and change it when they find something you missed.</li><li>Keep the component library tidy, so the next screen takes a day instead of a week.</li><li>Write short notes on each decision, so the engineers know why it looks the way it does.</li></ul><h2>What you&#39;ll bring</h2><ul><li>A portfolio of product design work, with at least one piece that used real data.</li><li>Strong sense of typography and layout, and a clear view of how colour carries meaning on a screen.</li><li>Comfort working in a small team that ships every fortnight.</li></ul><h2>Nice to have</h2><ul><li>Experience with data visualisation or dense interfaces.</li><li>Time spent with operations or logistics teams.</li></ul><h2>How we hire</h2><p>Four steps, the same for every role: an application read within five working days, a 30-minute intro call, a paid task of about three hours, then a final conversation. The How we work page sets out the timelines.</p>",
          "closing": "Open until filled",
          "seo_title": "Product designer, route planning · Tidewater Labs",
          "search_summary": "Product designer at Tidewater Labs: design the maps and timelines dispatchers read every morning. Hybrid in Selbury Docks."
        },
        {
          "slug": "customer-success-lead",
          "title": "Customer success lead",
          "team": "Customer success",
          "location": "Selbury Docks, hybrid",
          "type": "Part-time",
          "salary": "£34,000–£40,000 a year, pro rata for three days a week",
          "summary": "Help courier firms set up their first routes, bring their problems back to the product team, and lead our second customer success hire later this year.",
          "body": "<h2>What you&#39;ll do</h2><ul><li>Set up new courier firms on the planner, from their first depot and van to their first full morning of routes.</li><li>Run the weekly check-in with each customer, and log every problem they raise.</li><li>Take the problems that come up most often to the product team, with the evidence.</li><li>Write the help articles that answer the questions you were asked that week.</li></ul><h2>What you&#39;ll bring</h2><ul><li>Experience in customer success, account management or dispatch, ideally with small businesses.</li><li>Calm, clear phone and email manners, and an easy way with people who are short of time.</li><li>Careful notes, because the same question often comes back in a different form.</li></ul><h2>Nice to have</h2><ul><li>Experience with logistics software or a route-planning tool.</li><li>Time working in a depot or a courier office.</li></ul><h2>How we hire</h2><p>Four steps, the same for every role: an application read within five working days, a 30-minute intro call, a paid task of about three hours, then a final conversation. The How we work page sets out the timelines.</p>",
          "closing": "Open until filled",
          "seo_title": "Customer success lead, part-time · Tidewater Labs",
          "search_summary": "Part-time customer success lead at Tidewater Labs: help small courier firms set up their routes and turn their problems into product work. Three days a week."
        },
        {
          "slug": "operations-finance-coordinator",
          "title": "Operations and finance coordinator",
          "team": "Operations",
          "location": "Selbury Docks, hybrid",
          "type": "Full-time",
          "salary": "£36,000–£42,000",
          "summary": "Keep the office, supplier bills and payroll support running, and be the first person people ask when something is missing.",
          "body": "<h2>What you&#39;ll do</h2><ul><li>Run the office on Gantry Wharf: deliveries, visitors, the kitchen and the equipment for new starters.</li><li>Process supplier invoices and expense claims on time, and chase the ones that stall.</li><li>Support payroll with the timesheets and changes that the People team sends you.</li><li>Keep the team calendar, the office days and the learning budget records tidy.</li></ul><h2>What you&#39;ll bring</h2><ul><li>Experience in an operations, finance or office support role, in a small company if you can.</li><li>Careful with figures, and comfortable with spreadsheets and accounting software.</li><li>A friendly, practical manner with people at every level, and the sense to ask when you are unsure.</li></ul><h2>Nice to have</h2><ul><li>Experience with payroll or with a UK accounts package.</li><li>Experience running events for a team of thirty or more.</li></ul><h2>How we hire</h2><p>Four steps, the same for every role: an application read within five working days, a 30-minute intro call, a paid task of about three hours, then a final conversation. The How we work page sets out the timelines.</p>",
          "closing": "Open until filled",
          "seo_title": "Operations and finance coordinator · Tidewater Labs",
          "search_summary": "Operations and finance coordinator at Tidewater Labs in Selbury Docks: run the office, supplier invoices and payroll support for a 34-person software company."
        }
      ]
    }
  ]
}
