Five levels. Six titles.
One culture of ownership.

Volge is built around a single non-negotiable: every practitioner at every level owns client relationships and drives outcomes directly. Analyst is the entry grade, developed on live engagements from the first week; every grade above it is an experienced hire. There are no intermediary layers between the people doing the work and the people the client trusts.

Client Partner at every level Two ways in Scope sets the grade Everyone builds
The Philosophy
Client ownership is not a seniority privilege. It is a baseline expectation.

Most firms reserve client relationship ownership for senior grades. The rationale is straightforward: juniors need supervision, so seniors manage the relationship while juniors do the work. The result is a structural gap between the people who understand the work and the people the client actually trusts.


Volge's model collapses that gap. Every practitioner (from a Level 0 Analyst on their first engagement to a Level 4 Principal or Partner) carries the Client Partner function. The scope of the relationship changes by level. The responsibility for it does not.

5
Career levels
100%
Client Partner function
0
Intermediary layers
6
Titles across the firm

The progression track.
Five levels, six titles.

Level 0
Entry grade
Analyst0 – 2 years of experience, including none at all
Client
Partner
Level 1
Delivery ownership
Deployment Strategist
Client
Partner
Level 2
Technical direction
Architect
Client
Partner
Level 3
Technical authority
Senior Architect
Client
Partner
Level 4
Firm leadership
PrincipalPartnertwo tracks, the same scope; neither reports to the other
Client
Partner
Client Partner Active at every level: client ownership is not a reward for seniority. Every practitioner at Volge carries the Client Partner function proportionate to the scope of their level, from Day 1.

What each level owns.
Scope, days, and the bar.

LEVEL 00
Analyst
Level 0 · Entry grade
Entry
The Role

This is the entry grade, and the only one at which a candidate joins without a delivery record behind them. What is sought is evidence of how a problem is approached rather than a list of technologies. Analysts are placed on live engagements from the outset, with a named Architect accountable for their development.

What the days look like
Working a defined slice of a live engagement, with the work reviewed before it ships
Sitting in the reviews and the client sessions rather than hearing about them afterwards
Building depth in one stack and one sector rather than sampling several
Pairing with a Deployment Strategist or an Architect on the harder parts
What is looked for
0 – 2 years of experience, including none at all
Demonstrable engineering ability, from study, projects or prior work
A problem framed clearly, including the parts that are not yet understood
Willingness to be corrected, and to apply the correction
LEVEL 01
Deployment Strategist
Level 1 · Delivery ownership
Execution
The Role

This is an engineer who wishes to be inside the problem, rather than behind a ticket queue. Production code is written, delivery workstreams are owned, and both engineers and stakeholders are addressed fluently. Ambiguity is the setting in which this engineer is most effective, energised by presence in the room where decisions are made.

What the days look like
Embedded in the estate, whether at the client site or in the delivery centre
Owning one or more workstreams end-to-end, not just contributing to them
Shipping working software in sprint cycles with CI/CD from day one
Building capability in the client team as you work alongside them
What is looked for
Strong engineering fundamentals in at least one primary stack
2 – 5 years of production delivery experience
Comfortable owning outcomes in ambiguous environments
Can explain technical decisions to non-technical stakeholders
LEVEL 02
Architect
Level 2 · Technical direction
Design & Leadership
The Role

This practitioner has been in the room often enough to know what good looks like. The technical direction of an engagement is set, Deployment Strategists and Analysts are led, and it is this practitioner whom clients call when an architecture decision becomes difficult. The technical authority resides here, and the responsibility is held with composure.

What the days look like
Defining solution architecture across cloud, data, application and security layers
Leading a delivery team: setting direction, unblocking, reviewing output
Running executive-level technical reviews with client stakeholders
Making and documenting the hard architectural calls, not delegating them
What is looked for
Deep technical depth in at least one domain (data, AI, platform, cloud)
5 – 8 years delivering at enterprise scale
Proven ability to lead technical teams under delivery pressure
Can lead a room: clients, partners, and internal teams alike
LEVEL 03
Senior Architect
Level 3 · Technical authority
Technical Authority
The Role

Where the Architect holds one engagement, the Senior Architect holds the decision that spans several. This is the practitioner to whom an architecture is escalated once the consequences extend beyond a single programme, and the one who is expected to say so when the chosen direction is wrong. The judgement is exercised on the record.

What the days look like
Setting architectural standards that hold across engagements, not just within one
Arbitrating the decisions an engagement team cannot resolve on its own
Developing Architects, including the judgement that is not taught by delivery alone
Carrying technical credibility into commercial conversations before the work is won
What is looked for
8 or more years delivering at enterprise scale
Authority in a domain that is recognised outside this firm as well as within it
A record of decisions that held, and candour about those that did not
Capable of dissenting with a client, and of being persuaded by one
LEVEL 04
Principal
Level 4 · Delivery track
Firm Leadership
The Role

Firms are built here, and not merely engagements. The technical credibility to hold a room with a chief technology officer (CTO) is present, as is the commercial instinct to grow a client relationship from a single workstream into a multi-year programme. At Volge, Principals set the direction of practices, hire the people within them, and are held accountable for their outcomes.

What the days look like
Owning executive-level client relationships and growing them over time
Developing and stewarding a practice: the people, the craft, the reputation
Setting technical and strategic direction at the engagement portfolio level
Originating and shaping new programmes with clients and partners
What is looked for
Ownership of a territory, an industry or a solution, and in some cases all three
Track record of building and leading high-performance technical teams
Commercial instincts: can originate, shape and close complex programmes
Recognised authority in at least one domain Volge competes in
LEVEL 04
Partner
Level 4 · Commercial track
Firm Leadership
The Role

Partner sits at the same level as Principal and carries the same scope, a territory, an industry or a solution. The distinction is where the weight falls. The Principal is accountable for what is delivered; the Partner is accountable for the relationship and the commercial position that make the delivery possible. Neither reports to the other.

What the days look like
Owning the commercial relationship across a territory, an industry or a solution
Originating work, and declining the work that this firm should not take
Holding the commercial terms that let a Principal deliver without compromise
Representing the firm where its reputation is made rather than reported
What is looked for
Ownership of a territory, an industry or a solution, and in some cases all three
Commercial judgement that has been tested against a loss, not only a win
Relationships held at executive level that survived a difficult engagement
Technical credibility sufficient to be believed by the practitioners

How a grade moves.
Demonstrated, discussed, made.

There is no annual review in which a manager decides whether you are ready, and no tenure clock. The grade reflects the scope being carried: when the scope widens, the grade follows it. The experience bands beside each title are orientation rather than gates. At level four the path splits into two tracks with the same scope: Principal, accountable for what is delivered, and Partner, accountable for the relationship and the commercial terms. Neither reports to the other.

Step one
Demonstrated
The wider scope is shown in the work itself: owned, shipped and holding in production.
Step two
Discussed
The conversation is had with the people who saw the work carried, on the record.
Step three
Made
The transition is made and carried openly. You own it, rather than waiting to receive it.
The Client Partner Function

Everyone owns the relationship.
What changes is the scope.

The Client Partner function is not a title. It is a responsibility that applies to every practitioner at Volge, regardless of level. What changes across levels is the scope: the seniority of the relationship, the strategic weight it carries, and the time horizon it covers.

Level 0. Analyst
Working Trust
Present in the reviews and the client sessions rather than hearing about them afterwards. Trust is built by shipping reviewed work on a live engagement.
Level 1. Deployment Strategist
Team Relationships
Nurtures working relationships at the project and team level. Builds the day-to-day trust that makes delivery possible, and surfaces opportunities before they become requests.
Level 2. Architect
Programme Relationships
Owns senior technical and programme-level relationships. It is the Architect whom clients call when an architecture decision becomes difficult.
Level 3. Senior Architect
Standing Authority
Carries technical credibility into commercial conversations before the work is won, and holds the relationships that span more than one engagement.
Level 4. Principal & Partner
Portfolio Relationships
The Principal is accountable for what is delivered across the portfolio; the Partner for the relationship and the commercial terms that make the delivery possible.
At a Glance

How the levels differ.
Side by side.

Dimension
Level 0. Analyst
Level 1. Deployment Strategist
Level 2. Architect
Level 3. Senior Architect
Level 4. Principal · Partner
Primary mandate
Development on live work
Workstream delivery
Engagement direction
Decisions across engagements
A territory, an industry or a solution
Client interaction
In the reviews and sessions
Project teams and stakeholders
Executive technical reviews
Commercial conversations pre-win
Executive relationships over time
Technical hands-on?
Yes. Reviewed before it ships
Yes. Primary activity
Yes. With architectural intent
Standard-setting
Orientation
Leads others?
:
Builds client capability
Leads the delivery team
Develops Architects
Practices and the firm
Typical experience
0 – 2 years
2 – 5 years
5 – 8 years
8+ years
Measured by scope

Know where you fit?
Start the conversation.

Explore open roles or reach out directly. We do not recruit through intermediaries.