Skip to main content

Job postings

Read each company's open job postings so a later AI research step can see what they are hiring for.

Job postings · Intelligence · Accepts companies

Reads each company's open job postings from Ocean's own data, so an AI step can see what the company is hiring for. It needs the add-on that unlocks job filters. The step's settings call it "Advanced job filters", and it may be shown as Advanced filtering when you buy it.

When to use it

Use it when hiring is a buying signal. For example, find companies that opened sales roles in the last 30 days, then have an AI research step write a one-line reason to reach out.

What it does

For each incoming company, the step looks up its open job postings, narrowed by the settings below, newest first. It adds two fields to the record: a text list of the postings, and the number of postings that matched. A company with no matching postings is not dropped. It carries on with empty text and a count of 0.

Each posting becomes one numbered entry with only the details you chose under Include, separated by " | ". For example:

1. Senior Backend Engineer | Engineering (Software development) | Senior | Copenhagen, Denmark | first seen 2026-09-27 | EUR 70,000-90,000 per year

Configure it

  • Job title: words that must all appear in the job title, such as "sales manager". The last word can be the start of a word, so "eng" matches "engineer". Leave it empty to include every title.

  • Departments: only postings in these departments or sub-departments.

  • Seniorities: only postings at these seniority levels.

  • Locations: only postings in these countries or regions.

  • First seen: Any time, Past 7 days, Past 14 days or Past 30 days.

  • Postings per company: the most postings to keep for each company, from 1 to 100. The default is 25.

  • Include: which details each entry shows: Job title, Departments, Seniority, Location, First seen date, Salary and Description. Everything except Description starts selected, and you need at least one. Descriptions are long, so AI steps that use them cost more. Each description is cut off at about 2,000 characters.

All filters are optional.

Outputs

  • Job postings: one entry per open posting, with the details chosen under Include. Mention it in an AI research prompt to let the AI read the postings.

  • Job postings count: how many postings matched your filters, before the Postings per company limit. You can use it in a Filter or Route to keep only companies that are hiring.

See Reference earlier steps with @-mentions for how a later step reads these fields.

Cost

This step does not use credits. An AI research step that reads the postings does, and a long Description makes that step cost more. See Credits in workflows.

If it fails or finds nothing

  • Nothing matches. The company continues with empty Job postings and a Job postings count of 0. Use a filter on the count to drop those companies.

  • The lookup fails. The step tries once more after a short wait. If it fails again, the record fails with a "job postings lookup failed" message.

  • No company domain. A record without a company domain fails with "this record has no company domain".

  • No add-on. See below.

  • To let records carry on when this step fails, open the step's settings, find If this step fails and switch on Continue anyway. The record then moves on without this step's data. See Troubleshooting workflows.

  • You can try the step on a sample first with the play button at the top of its settings (tooltip: Run a test).

Example

A weekly workflow starts with a Company search. Next, Job postings keeps postings with Job title "sales", First seen set to Past 30 days, and Include set to Job title and Location. A Filter keeps companies where Job postings count is above 0. An AI research step reads Job postings and writes a short hiring summary. Then Send companies to CRM saves the accounts.

Gotchas

  • Advanced job filters add-on. You can add this step on any plan, but without the add-on its settings show "Advanced job filters is an add-on to your plan." instead of the options. If you pay by subscription and manage your account, the page has a View add-ons button. If you do not have a subscription, it has a View plans button. Other users see the message with no button. A workflow with this step cannot be published until the add-on is on, and Run a test is hidden.

  • If the add-on is removed after you publish, the step fails for every record with the message "Job postings need the Advanced job filters add-on". Remove the step or add the add-on back.

  • This step works on companies only. Put it after a company step, and before any step that turns companies into people.

  • The same add-on unlocks the hiring filters in Company search. See Job Postings filter.

Did this answer your question?