Reading A Competitor's Job Board For Strategy

A company can keep its roadmap private, but it can’t hire in secret. To build a new product, enter a country or start selling to a new segment, it has to find people, and to find people it has to say publicly what it needs them to do. A job board is one of the few places where a competitor describes its plans months ahead, in its own words, because it has to.

Reading it well takes some care. Most postings mean nothing on their own, many are noise, and the useful signal is in patterns over time rather than in any single role. This guide covers what to look for, what to ignore, and where the line sits.

Why job boards are worth reading

Websites describe what a company sells today. Press releases describe what it wants you to believe. Job postings describe what it is about to spend money on, which makes them closer to a budget than to marketing.

They are also unusually structured. Most companies above a certain size use a hosted applicant tracking system, and the public board it produces lists every open role with a title, a department, a location and often a date. That structure is what makes it possible to compare one month with the next.

What to look for

New departments

The strongest signal on a job board is a department that didn’t exist before. A software company that has only ever hired engineers, sales and support, and suddenly opens a role under “Partnerships” or “Public Sector”, is building a function it didn’t have. A first role in a new department is often the person who will build the team, and the posting usually says so: “our first”, “founding”, “build the team from the ground up”.

Read those postings closely. The description of what the first hire will do is often the clearest written account you will get of a competitor’s next bet.

New countries

The second strongest signal is a new country. A company with every role in two countries that opens a sales role in a third is entering a market. A support role in a new time zone usually comes after customers have arrived there; a country manager or a first account executive usually comes before.

Language requirements are worth noting too. A role requiring fluent German in an office outside Germany is still a statement about where the customers are.

Surges in one department

A department that grows quickly against its own history is a priority. If Lumen Labs usually has three or four open engineering roles and now has twelve, and most mention the same product area, that area is where the next release is coming from. If the surge is in sales, especially in one segment or region, expect a push in that market within a few months.

The comparison has to be against the company’s own baseline. Ten new roles is a surge for a forty-person company and a quiet week for one with four thousand people.

Growth or closures across the board

When many roles open across departments at once, a company has usually raised money or hit a budget cycle. When many close at once without being filled, it has usually frozen hiring. Either is worth knowing, but neither tells you much about direction until you see where the growth or the cuts are concentrated.

Words in the descriptions

Titles are standardised; descriptions are not. Look for the names of technologies a competitor doesn’t yet support, integrations it doesn’t yet have, compliance standards it doesn’t yet claim, or customer types it doesn’t yet mention on its website. A product manager role that mentions “our upcoming enterprise offering” is a launch announcement written in advance.

What to ignore

Most of what changes on a job board is not news.

• Reposted roles. Many companies close and reopen the same role to refresh its date, or post the same role in several locations. Three postings for “Senior Backend Engineer” in three cities may be one hire. Treat a role that closes and reappears with the same title as the same role.
• Evergreen postings. Some roles stay open permanently to collect applications: “General application”, “Talent pool”, “Future opportunities”. They tell you nothing.
• Normal churn. A company of any size always has a few roles opening and closing. One new engineer and one closed designer role is a Tuesday.
• Single roles out of context. One posting in a new city may be a remote hire who happens to live there. Wait for a second role, or for a title that only makes sense locally, before calling it an expansion.
• Titles alone. “Head of AI” can mean a research team or a single person adding a chatbot to the support page. Read the description before drawing a conclusion.

A useful rule: a hiring move is a change in where a company is growing, not a change in how many roles it lists. If you can’t say which department or which country moved, you probably don’t have a signal yet.

Reading over time

A single snapshot of a job board is a list. Two snapshots a month apart are a story. Keep a dated record of what was open and compare like with like:

Keep the record honest about what you couldn’t see. If a board was unreachable on one check, that gap is not a hiring freeze. If a company moves from one applicant tracking system to another, the old board will look as if every role closed at once. Note the move and start a new baseline rather than reporting a collapse that didn’t happen.

Connecting hiring to the rest of the picture

Hiring signals are strongest in combination. A cluster of enterprise sales roles plus a new “Enterprise” plan on the pricing page plus a security page that suddenly mentions an audit is one story told three ways. Any one of them alone is a hint; together they are a plan.

When you write up a hiring move, say what you saw and what you think it means, separately:

Seen: Arcfield opened its first four roles in France in three weeks, including a country manager and two account executives. Likely meaning: A direct sales push into France, probably starting with mid-sized companies. Confidence: Medium. No French pages on the website yet.

That separation lets the reader disagree with your interpretation without having to doubt your facts.

Where the ethical line sits

Reading public job postings is ordinary research. Every candidate, recruiter and analyst does it. A few lines are worth drawing clearly, for legal and for plain reasons of decency.

• Read only what is public. Postings on a company’s public careers page or hosted job board are published to be read. Anything behind a login, an internal referral portal or an applicant account is not.
• Respect the site’s rules. If a site’s robots.txt asks automated visitors not to read a page, don’t.
• Don’t apply for roles to gather information. Applying, interviewing or contacting a competitor’s recruiters under false pretences is deceptive, wastes real people’s time and can create legal exposure.
• Leave individuals out of it. Postings sometimes name a hiring manager or recruiter. Your analysis is about the company’s direction, not about the people who work there; don’t build profiles of them.
• Don’t poach from the data. Using a competitor’s job board to target their employees is a different activity with different rules. Keep the two apart.

The test is simple: would you be comfortable if the competitor saw exactly what you did and how? For reading their public job board and noting what it says about their plans, the answer should be yes.

Where Orlea fits

Orlea finds a competitor’s public job board when it is hosted on Greenhouse, Lever or Ashby, and checks that the postings really name that company. It compares what is open now with the last hiring event and flags a move only for a new department or country, a surge in one department, or growth or closures across the board. Thresholds scale with the size of the board, and a reposted role counts as the same role. It reads public postings only.