Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Building a global job architecture for an 18,000-employee food-processing group

Industry
Food processing / agricultural products
Region
Europe / global
Size
18,000+ employees
Best for
Large multinationals seeking one global architecture with local adaptability
18,000+
employees within one architecture
14
clusters of job families
€5bn+
annual revenue of the group
1
consistent methodology across a global footprint
01 Context

Starting point

A stock-listed European food-processing group with over 18,000 employees replaced fragmented local job structures with one global job architecture, designed for global consistency with room for local adaptability.

Client profile

The client was a publicly listed, European-headquartered group specialising in agricultural raw materials and processed products, with revenue above EUR 5 billion and a global footprint of production sites and export markets.

Its workforce spanned production and operations, technical and engineering, quality, supply chain, commercial, IT, finance, HR and corporate management. HR maturity was comparatively advanced, but the group lacked a single, consistent way of describing and comparing roles.

The problem

  • No consistent job architecture spanning divisions and functions
  • Limited ability to compare roles for internal equity and salary benchmarking
  • No shared analytical basis for job evaluation across the group
  • Difficulty supporting global HR applications on a common structure
  • Fragmented role definitions that obscured feeder roles and career paths

Why it mattered at that point

The architecture was framed not as an end in itself but as a backbone for organisational design, reward and career management. A consistent job architecture was the prerequisite that made these applications credible and comparable across the group.

Alternatives considered

Options included continuing with local grading practices, building a job catalogue without analytical evaluation, or relying primarily on market pricing. The group chose an analytical, factor-based route, as only a consistent methodology could provide a defensible basis for comparison across divisions and countries.

02 Approach

How the project was delivered

Structured job-architecture design combined with analytical, factor-based job evaluation in four steps.

Step 1

Design

A framework of job families outlined the clustering of jobs and logical career paths.

Step 2

Describe

Consistent job descriptions captured purpose, dimensions, key responsibilities, know-how, skills and challenges.

Step 3

Measure

Roles were evaluated analytically with gradar against one consistent set of factors.

Step 4

Slot and roll out

Evaluated roles were slotted into the architecture and implemented in the wider organisation.

Scope at a glance

  • A complete group-wide architecture in 14 clusters, from engineering, quality and operations to sales, IT, finance, HR and management
  • Individual jobs defined and slotted within these clusters
  • End-to-end delivery from design and data gathering to evaluation, roll-out and implementation

Evaluation factors

Knowledge and experience, thinking and problem solving, processes and complexity, communication, people and organisational responsibility, and scope of decisions. For management and project roles also leadership span, functional responsibility and project size and budget.

Key decisions
  • How to define the cluster and job-family structure so that it was complete but not over-engineered
  • How to balance one global structure against local adaptability
  • How to handle management, professional and project-based roles within a single evaluation logic
  • How to slot individual legacy jobs into the new architecture
  • How to treat executive roles, which can exceed standard management levels
Data and inputs

Organisation charts and divisional structures, existing role information, and the context needed to describe each job: strategy and objectives, operating model, organisational structure, purpose, dimensions, key responsibilities and required know-how. Structured interviews provided primary input from senior stakeholders.

03 Challenges

What made it difficult

Several real-world complexities surfaced, particularly when the architecture was operationalised in the supporting system.

Linking job families to functions

Grading lines from overarching job families could not always be linked to individual functions in the system.

Multilingual job titles

Differences in the language of job titles could not be linked together in the system, complicating multi-country use.

Manual uploads

Job descriptions had to be uploaded individually and manually per job, with no mass upload or export.

Executive grading

Executive roles often exceeded standard management levels. Graded in a separate module, they could not be linked back to other levels or to pay databases.

On the opportunity side: the system supported user-defined hierarchies and assigned regions, access-control roles and users, mass import of grading lines, and matrix export per region or hierarchy, which helped manage scale and regional differences.

Stakeholder involvement

Input was gathered through structured interviews with the Executive Board, Divisional Board, Corporate Directors and the wider HR community. Governance combined a steering committee and executive sponsor with a project manager and delivery team, providing decision rights, senior validation and a clear path from design to roll-out.

04 Results and lessons

What changed

Before
After
No consistent job architecture across divisions and functions
One global job architecture in 14 clusters of job families
No shared analytical basis for job evaluation
Analytically evaluated roles under one common methodology
Limited comparability for internal equity and benchmarking
A clearer basis for comparing compensation and benchmarking against the market
Fragmented role definitions and unclear career paths
Clearer role expectations underpinning career paths and feeder-role planning

What was delivered

  • A global job architecture organised into 14 clusters of job families
  • Job (family) descriptions as a consistent basis for evaluation and development
  • Analytically evaluated roles for internal and external comparison through gradar
  • A slotting of individual jobs into the architecture
  • A backbone for organisational design, reward, salary benchmarking and career management

Lessons learned

  • Design the architecture as a backbone, not a deliverable in its own right.
  • Apply one consistent, analytical methodology for defensible comparisons across divisions and countries.
  • Engage senior stakeholders early to validate the structure and secure decision rights.
  • Test the supporting system early, including job-family links, multilingual titles, bulk uploads and executive grading.
  • Decide how to treat executive roles at the outset, so they stay connected to the grading structure and pay data.

Relevant for

  • Large, multinational organisations seeking one global job architecture with local adaptability
  • Stock-listed groups professionalising reward and compensation governance
  • Organisations with diverse workforces spanning production, technical, commercial and corporate functions
  • Companies connecting job evaluation with salary benchmarking and internal equity
  • Organisations building a foundation for HR applications across organisational design, reward and career management

Explore our job architecture features

Through analytical job evaluation, gradar helps organisations design a clear, consistent job architecture that supports fair, transparent pay decisions.
Businesswoman using a stylus on a digital tablet at a bright office desk with pens and papers.

FAQs

How does job evaluation support a global job architecture?

Job evaluation provides a consistent analytical basis for comparing roles across divisions and countries. This allows roles to be slotted into a shared structure, compared for internal equity, and benchmarked against external market data.

Can one job architecture work across many countries?

Yes. A consistent methodology and factor set can be applied globally, while the architecture is designed to allow local legal, market and organisational differences. The aim is global consistency with local adaptability.

What is the difference between job evaluation and salary benchmarking?

Job evaluation assesses the internal value of a role using consistent factors. Salary benchmarking compares pay levels against external market data. Both are complementary: evaluation establishes internal equity, benchmarking ensures external competitiveness.

How are job families and clusters defined?

Roles are grouped into logical job families and clusters based on the nature of the work and typical career paths. The structure should be complete enough to cover the organisation but not so detailed that it becomes hard to maintain.

How should executive roles be handled?

Executive roles often exceed standard management levels and may be graded separately. It is important to decide early how these roles connect back to the wider grading structure and to pay databases, to avoid them becoming disconnected.

Who should be involved?

Typically the Executive Board, divisional leadership, corporate directors and the HR community, supported by a steering committee, executive sponsor, project manager and delivery team. Senior involvement provides validation and clear decision rights.

Build your job architecture with gradar

Job architecture insights are delivered through the gradar platform - connecting job evaluation, compensation analysis and pay transparency in one consistent framework.

Job evaluation

Compensation

Pay transparency