Skip to content

100 Job Strategies · 24 of 100

Acquisition Aftermath

Everyone watches the acquisition. Nobody watches what happens six months later.

2 viewsMedium effortPays off in 2-6 monthsExperienced candidatesProject and change managersData and systems specialistsContractors
Share

In short

When a company is acquired, duplicate roles get cut — and integration roles get created. The hiring that follows a deal is for different skills than the ones that left, so internal staff cannot fill them. Six months after an acquisition is a hiring window with almost no candidate attention on it, because the headline was about job losses.

The situation

Northwind acquires Halcyon. The coverage writes itself: consolidation, synergies, expected redundancies in overlapping functions.

Every jobseeker reads that as a company shedding people and looks elsewhere.

Six months later, the reality inside the building is different. Two customer databases have to become one. Two finance systems, two support teams, two sets of contracts, two engineering cultures. The company needs integration engineers, data migration specialists, change managers, systems analysts and project managers — roles that did not exist before the deal and cannot be filled by the people who were made redundant, because those were duplicate marketing and admin roles, not integration specialists.

The company is hiring hard into a market that stopped paying attention half a year ago.

Why this works

Acquisitions produce two opposite effects that arrive at different times, and the market only ever notices the first.

Immediately after a deal, overlapping functions are consolidated. Two finance teams become one, duplicate sales territories are merged, and redundancies follow. This is what gets reported, and it teaches candidates to avoid the company.

The second effect takes months to surface. Integrating two organisations is enormously labour-intensive and requires specific skills: data migration, systems integration, change management, process harmonisation, contract and compliance reconciliation. Almost none of that capability exists in either company at the volume required, because neither was previously in the business of merging with anyone.

So the acquirer hires — often urgently, often at premium rates, frequently on contract because the work is finite. And they hire into a candidate market that mentally wrote them off at the announcement.

Timing is the key insight. The window is not at the announcement, when everything is frozen and nobody knows who reports to whom. It opens roughly three to nine months later, once integration planning has produced actual workstreams with budgets and deadlines.

How to run it

  1. 1

    Track deals in your sector and note the date

    Trade press and business media report acquisitions routinely. What matters is recording the completion date so you can return to it later.

  2. 2

    Come back three to six months afterwards

    This is the discipline that makes the strategy work. At announcement there is nothing to apply for; half a year later the integration programme is staffing up.

  3. 3

    Target integration skills specifically

    Data migration, systems integration, change management, business analysis, project and programme management, compliance harmonisation. These are the roles the deal creates.

  4. 4

    Consider contract as well as permanent

    Integration work is finite and frequently staffed by contractors at good rates. It is also a clean way into a larger organisation.

  5. 5

    Speak the language of the deal

    Referencing the integration directly — systems consolidation, harmonisation, migration — signals that you understand what they are actually dealing with.

  6. 6

    Look at the acquired company too

    The acquired business often keeps hiring for its own operations, and its roles are even less watched than the acquirer's.

What to say

Copy, then make it yours
Hi Priyanka, I saw that Northwind completed its acquisition of Halcyon earlier this year. I imagine you're some way into integrating the two platforms by now. I've worked on three post-acquisition data migrations, twice on the acquirer side — consolidating overlapping customer records, reconciling two schemas and keeping reporting intact while the merge happens. The reconciliation piece is usually where these programmes slow down. I couldn't see integration roles advertised, which is partly why I'm writing directly. If you're building out that workstream, whether permanently or on contract, I'd like to be considered. — Stefan

When it does not work

  • Genuine long-term instability. Some acquisitions go badly and cut repeatedly for years. Look at whether the acquirer has a track record of successful integrations.
  • Political environments. Post-merger organisations can be intensely political, with two leadership teams competing. Ask what the reporting structure actually looks like now.
  • Work with a defined end. Integration programmes finish. Understand whether the role continues afterwards or whether you are being hired for a project.
  • Arriving too early. In the first weeks after a deal, nothing is decided and nobody can hire. Patience is the whole strategy.
  • Assuming the acquirer is the only employer. The acquired company frequently continues operating and hiring under its own name, and attracts even less attention.
The takeaway

The deal announcement tells you when to stop paying attention. Put a note in your calendar for six months later, when everyone else already has.

Questions

Why wait three to six months instead of applying at the announcement?

Because in the immediate aftermath of a deal, very little can actually happen. Reporting lines are undecided, budgets are unallocated, integration planning has not produced concrete workstreams, and hiring is frequently frozen entirely while the organisation works out what it has bought. The roles this strategy targets are created by integration planning, which takes months to convert into funded workstreams with deadlines. Applying at the announcement is not early, it is premature.

Which specific roles does an acquisition create?

Overwhelmingly integration-related: data migration specialists, systems and platform integration engineers, business analysts, change and programme managers, and compliance or contract harmonisation roles. There is also sustained demand in finance and HR for the practical work of merging two sets of systems, policies and payrolls. What these have in common is that neither company employed them at the required scale beforehand, since neither was previously in the business of merging with anyone.

Is it risky to join a company in the middle of an integration?

There is real risk and it is worth assessing rather than ignoring. Post-merger organisations can be politically difficult, with two leadership groups competing for influence, and some acquisitions go badly enough to produce repeated rounds of cuts. The mitigations are looking at whether the acquirer has integrated businesses successfully before, asking directly what the reporting structure looks like now, and establishing whether your role continues once the integration programme completes.

Should I approach the acquirer or the acquired company?

Both are worth pursuing, and the acquired company is frequently overlooked entirely. Acquired businesses often continue operating under their own name with their own hiring needs, and they receive even less candidate attention than the parent because everyone assumes they have stopped hiring. The acquirer typically holds the larger integration budget and the bulk of the new roles, but the acquired side can offer an easier entry point into the same combined organisation.

Find verified jobs from 100,000+ companies
Share

More from 100 Job Strategies

See all 25 in this series