PastaHR

What I built

PastaHR lets candidates apply for jobs by chat, on WhatsApp or Instagram, and its AI screens the answers. Their previous Webflow site explained the product on the homepage, and most of the menu's feature links jumped to sections of it. The careers link went to a Notion page, and the five customer stories were blog posts.

I rebuilt it as a new Webflow project with a page type for each kind of content: five industry pages, three use-case pages, a case study collection, a careers collection and the blog. It went live in March 2025, in German and English.

Jobs are the clearest example. Each open role got its own page on pastahr.com in both languages, six of them in April 2025, with the full job description in the HTML Webflow serves.

pastahr.com ran on this build from March 2025 until at least July 2026. By then the case study collection held twelve stories, up from five in April 2025, and the site had new pages for its Workday and Abacus Umantis integrations.

Details

• German is the default and English is under /en, both on Webflow Localization. Slugs are translated as well: /industry/gesundheit in German is /en/industry/healthcare in English, and every page lists its other-language version as an hreflang alternate.
• Team, location and contract type are their own collections, nested into each job with Finsweet's CMS Nest, so the job listing shows all three on every role. On the job page, a script turns the title, contract type and location into JobPosting structured data. It maps the contract types to schema.org values and marks remote roles as telecommute.
• Each industry page has an FAQ section, like the homepage. A script builds the FAQPage structured data from the questions on the page, so the markup always matches the visible answers. The answers themselves are in the HTML, which crawlers that skip JavaScript still read.
• Case studies live in a separate collection, and the success stories page filters them by industry or integration with Finsweet's CMS Filter. On the homepage and the industry pages, the testimonial slider is a CMS list, and a quote shows a button to its case study only when one exists.
• Shared components cover the navigation, footer, testimonial slider, logo strip and demo block. All five industry pages use a footer variant with an image and a closing pitch for that industry: nursing staff on the healthcare page, drivers and logistics specialists on the logistics page.
• Every demo button on the homepage goes to /demo, which has an inline Cal.com calendar with the customer logos and testimonials below it. Webinars load from Contrast into a widget on the site's webinars page; before, the menu linked straight out to Contrast.