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.
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.
The progression track.
Five levels, six titles.
Partner
Partner
Partner
Partner
Partner
What each level owns.
Scope, days, and the bar.
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.
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.
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.
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.
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.
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.
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.
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.