You can style the section around a Greenhouse embed, but not the document Greenhouse loads inside the iframe. That limit comes from the browser’s same-origin policy, not from a missing Webflow selector.

The boundary in one picture

html
<section class="careers-shell">
  <h2>Open roles</h2>       <!-- your document; Webflow CSS applies -->
  <iframe src="https://job-boards.greenhouse.io/your-company"></iframe>
                         <!-- Greenhouse document; your CSS cannot enter -->
</section>

The parent page belongs to your domain; the iframe document belongs to Greenhouse. Browsers isolate their DOM and styles. A rule such as .careers-shell iframe h3 { font-family: ... } cannot select an h3 inside that other document.

What you can style safely

  • The section heading, introduction and spacing outside the iframe.
  • The iframe element’s width, border, background and surrounding container.
  • A loading message or fallback link that lives in your own page.
  • The hosted board’s supported settings inside Greenhouse itself.
css
.careers-shell { max-width: 72rem; margin-inline: auto; padding: 4rem 1.5rem; }
.careers-shell iframe { display: block; width: 100%; border: 0; }

What will not work

Webflow classes, inherited fonts, CSS variables and site-wide resets stop at the iframe element. Adding !important, targeting deeper selectors or moving the rule into page custom code does not change the cross-origin boundary. Injecting code into a vendor document is not a stable workaround.

The fully styled alternative

Greenhouse’s public Job Board API returns job data without an API key. Fetch that data and render it into Link Blocks, headings and text nodes you built in the Designer. Those nodes are part of your page, so your normal classes and responsive rules apply.

Start with the endpoint and field reference, then use the complete no-iframe Webflow tutorial. The tutorial uses /departments so the list gets department filters without downloading full descriptions.

When the iframe is still the right choice

Keep it when the default presentation is acceptable, application flow inside the frame matters, and maintenance should stay entirely with Greenhouse. Choose the API-rendered list when matching the site design, filtering, performance control or layout reliability matters more. The live Greenhouse integration shows that API-rendered approach.