Role design and job descriptions for Managed service providers: A Ladder From Level One to Architect
A managed service provider runs on tiers, but the tiers are often only titles. Written roles say what each level owns, when to escalate and what proves a person is ready for the next one.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsWhy role design and job descriptions matters in managed service providers
Managed service providers tend to name tiers before they define them. A level two engineer in one team does the work of a level one in another, and an architect spends most days on tickets. New customers add roles such as onboarding engineer and service delivery manager without anyone writing down where they sit. Escalations go to whoever is nearest, and the person escalating cannot tell if they were right to do so.
Role design takes the service as it runs and writes each role to match: what it owns, which decisions it makes alone, what it escalates and to whom. Each tier has a description of skills and of proof of readiness for the next. Handovers between tiers, and between delivery and account teams, are written as steps. The same descriptions then serve hiring, pay and appraisals.
How to set it up
1. Map the service flow
Draw the path of an alert or ticket from first contact to closure and mark who touches it. Note where it waits.
2. Define each tier in plain words
For level one, two, three and architect, list tasks done alone, decisions made and escalations. Use real examples from your tickets.
3. Write the proof of readiness
For each step, describe the tasks a person must have done well, signed off by a senior. The role design and job descriptions page describes the format.
4. Describe handovers
State what a ticket must contain when it moves between tiers and how fast it must move.
5. Check with the holders of the roles
Read each description with two engineers in that role and correct what they say is wrong.
Check these first
Before changing anything, find out what is true today. These take an afternoon and use your own records.
- Ask three engineers what separates level two from level three and compare answers.
- Read ten escalated tickets and see how many were escalated too early or too late.
- Compare an old job advertisement with the work a role now includes.
- Check whether architects' hours are logged against design or tickets.
GullyHR can do this with you. Read how we approach role design and job descriptions in general, or share your requirements and we will tell you where to start.
Questions owners ask
Use as many as your service needs, and no more. Three is common. More tiers add handovers and delay. Define each by what the person can do alone, not by years of experience.
A mix of real tasks done well, a review by a senior and a short scenario test. Years served alone say little. Keep the evidence in a simple record so decisions can be explained.
If you sign customers regularly, yes. The skills differ from ticket work, and mixing the two overloads both. Give the role its own description, measures and career route.