Dialectica Careers: a Webflow Cloud job board powered by Greenhouse

Dialectica did not need a prettier link to Greenhouse. They needed their careers experience to feel like part of the Dialectica website.

The existing pattern was familiar: a careers page in the brand site, then an external recruitment flow somewhere else. The brief was different. Candidates should be able to browse jobs, search opportunities, open a role and apply without leaving dialectica.io. At the same time, Dialectica’s internal team still needed Greenhouse to remain the system where jobs and recruitment workflows were managed.

That made the technical question precise: could Greenhouse stay the source of truth while Webflow kept owning the candidate experience?

The request was not a standard Webflow page

Dialectica already knew, from the Origin project, that Webflow Cloud could support application logic inside the Webflow ecosystem without moving the product to a subdomain or a separate website.

Careers had a similar constraint, but a different shape. This was not a large database product. It was a recruitment experience connected to an external ATS, with job listings, search, detail pages, application forms and live operational data.

The obvious shortcuts were not right.

Redirecting candidates to Greenhouse would have been simpler, but it would break the brand experience at the exact moment someone is deciding whether to apply. Syncing jobs into Webflow CMS was also possible in theory, but it would create a second source of truth and introduce a fragile sync process between Webflow and Greenhouse.

The better answer was to let each platform do the job it was built for.

Greenhouse would manage the jobs and hiring process. Webflow would remain the public brand and content layer. A custom Webflow Cloud application would handle the job board, detail pages and application flow.

Validating Greenhouse before designing the system

Fred’s first step was not visual design. It was reading the Greenhouse API documentation and checking whether a custom application could be built reliably on top of it.

Once Fred confirmed that the API could support the core requirements — job listings, job detail data, form questions and application submission — the architecture became clear.

GOMO built the full careers application with Astro, React and Tailwind on Webflow Cloud. The app lives at /careers/jobs, inside the same website structure, and handles the candidate journey from job discovery to application submission.

The pages are server-rendered for performance and indexability. React handles the interactive parts: search, filters, job cards, form behaviour and repeatable application fields. Greenhouse remains the live data source and receives the applications.

The point was not to replace Greenhouse. It was to build the public-facing layer Greenhouse could not provide in Dialectica’s own visual language.

A React component inside Webflow itself

There was another important layer.

The full job board and application flow live in Webflow Cloud, but Dialectica also needed live job discovery inside the main Careers page, which is managed in Webflow.

For that, GOMO created a Webflow Code Component: a custom React component imported directly into the Webflow Designer. It can be placed inside the native Webflow page like any other component, while still running custom React logic and pulling live job data.

This matters because it avoids the usual compromise. The Careers page can stay editable in Webflow, while the job search experience is not limited to standard Webflow elements, embeds or static CMS content.

It is a more advanced Webflow pattern: Webflow for the page, React for the interaction, Greenhouse for the data, and Webflow Cloud for the deeper application flow.

Designing the application around Dialectica’s existing site

Dialectica’s internal team provided requirements, content, feedback and approvals. GOMO handled the technical architecture, implementation and application design.

Fred designed the application around the existing Dialectica website, rather than treating it as a separate product UI. The goal was for candidates to feel they were still in the same environment as they moved from the Careers page into the job board and application pages.

That meant matching the visual language of the main site while making the job experience functional: clear job cards, searchable listings, filters by team and location, job detail pages, application forms and the right paths back into the main careers experience.

The result is not a generic ATS skin. It is a custom candidate experience built around Dialectica’s site, with Greenhouse quietly powering the operational layer behind it.

The result: candidates can apply without leaving the site

In a few weeks, Dialectica moved from an external recruitment journey to a custom Webflow Cloud careers experience on the main domain.

Candidates can now browse, search, open and apply for roles without leaving dialectica.io. Dialectica’s team can continue managing recruitment in Greenhouse. The Webflow Careers page can include live job search through a React Code Component. The full application flow can live in a proper server-rendered app, without forcing jobs into Webflow CMS or sending candidates to an external interface.

For GOMO, this is the kind of Webflow Cloud development that makes the platform more useful without pretending it should do everything. Webflow keeps the brand experience. Greenhouse keeps the recruitment workflow. The custom application layer connects them in the place where candidates actually feel the difference.

It also shows where advanced Webflow development is heading: not just building pages, but extending Webflow with React, APIs and application logic when the project needs more than a visual website.