Levels and growth
Every Exalynt engineer is at one of four levels: Associate, Mid, Senior, or Principal. This page explains what each level means, why someone is at it, and how you grow from one to the next.
- Considering Exalynt? Read the skills we value and the levels, and find the description that sounds most like how you work today. Then see where you'd start.
- Already at Exalynt? Read your level and the one above it, then moving up.
At a glance
Your level reflects the kinds of problems you have the experience to lead. Every level is held to the same standard.
- Every level does the same job. Every engineer owns their blocks end to end and works directly with clients. Levels differ in how much uncertainty you take on and how far your influence reaches (details).
- It's never a judgment of your worth. Everyone is owed the same respect, whatever their level (details).
- It's shown in your work, across five skills: understanding the problem, engineering craft, judgment, communication, and lifting others.
- It isn't tenure, location, hours, or the languages and tools you know (details).
- It doesn't change your pay. Every engineer earns the same Engineer Share, 60%, on every block, whatever their level (details).
| Engineer level | What they lead |
|---|---|
Associate | Delivers well-defined features with care, backed by reviews that keep quality high. |
Mid | Delivers scoped features independently, raising risks and tradeoffs early. |
Senior | Leads ambiguous problems, shaping the work itself and guiding other engineers. |
Principal | Sets technical direction for complex, open-ended work across engagements. |
What levels are for
Levels exist for two reasons: to make clear the kinds of problems each engineer is ready to lead, so work goes to the people ready for it, and to help all of us see how to help each other grow. They don't set pay: every engineer earns the same share of every block. They are not a ranking of people.
A level describes the kinds of problems you're ready to lead today. It says nothing about your worth.
- Everyone is treated with the same dignity. An Associate engineer's question, idea, or concern deserves the same respect and attention as a Principal's. Brushing someone off, talking down to them, or discounting what they say because of their level goes against our values and the code of conduct. Lead with kindness and humility
- Ideas are weighed on their merits. Insight can come from anyone. In a review, a design discussion, or a checkpoint, what matters is whether an idea is right, not the level of the person who raised it. Seek understanding and alignment
- Growing means more responsibility for others, not more status. The further you grow, the more of your job is making room for others to contribute, sharing what you know, and giving credit away. Succeed together
- Levels make growth something we do together. Knowing where someone is tells us what help is useful: what to pair on, what to review closely, and what they're ready to take on. Knowing where you are tells you what to ask for. Asking for help is never a mark against you, at any level. Succeed together
- We talk about levels honestly and kindly. Feedback about your level is about the work, specific and actionable, and given with care. Be honest and transparent
If anyone treats you as less because of your level, that's a conduct concern, and you can raise it like any other.
Every level does the same job
Exalynt doesn't hand some engineers the tasks and others the decisions. At every level, you:
- Own your blocks end to end. Each block is assigned to one engineer and never shared. You understand the problem, build across the stack, ship it, and show the client what changed (details).
- Work directly with the client. You confirm the goal, give the iteration update at the checkpoint in the client's language, and earn their trust (details).
- Label work honestly with the stability level it has really reached, and name the gaps.
- Own what you ship, including what AI helped write (details).
- Help other engineers, on your team and across Exalynt, through reviews, pairing, and sharing what you know, as part of every block.
- Keep the security and privacy baseline and the code of conduct.
- Practice the core values. Honesty, kindness, and ownership aren't senior skills. We expect them from your first block.
What changes as you grow isn't whether you do these things. It's how much uncertainty you can take on, how far your judgment can be trusted, and how many people your work makes better.
The skills we value
Our philosophy says code is a tool and helping people is the outcome. The skills we value follow from that, and each one puts our values into practice:
- Understanding the problem. Finding out who we're helping, what they're trying to accomplish, which constraints matter, and whether software should solve it at all. Seek understanding and alignment
- Engineering craft. Building clear, simple, reliable software across the stack (interface, backend, data, integrations, and production), verified to the level the work claims. Using AI well is part of the craft. Pursue excellence
- Judgment. Weighing tradeoffs, choosing the simplest responsible solution and the right tools for the job, investing only what a stability level needs, knowing what not to build, and estimating honestly. Pursue excellence Take ownership
- Communication. Listening well, saying what you know, what you assume, and what you don't know yet, making your reasoning visible, and raising risks early, with clients and other engineers alike. It matters most in working with clients. Be honest and transparent Seek understanding and alignment
- Lifting others. Reviewing, pairing, mentoring, sharing what works, and giving credit generously. Succeed together Lead with kindness and humility
Every level uses all five. The difference is how far each one reaches:
| Associate | Mid | Senior | Principal | |
|---|---|---|---|---|
| The work | Defined, with the approach mostly set. | Scoped, and you find the approach. | Ambiguous, and you shape the work itself. | Open-ended, across engagements. |
| Understanding | Understands the goal of their slice. | Clarifies a feature's goal and limits. | Finds what the client needs, not just what they ask. | Shapes how clients and Exalynt see hard problems. |
| Craft | Builds working, tested code, reviewed. | Delivers features to their level, alone. | Designs systems that last and are easy to change. | Owns complex architecture and technical direction. |
| Judgment | Follows sound patterns, asks when unsure. | Chooses approaches and tools, explains why. | Makes lasting decisions, including what not to build. | Makes the decisions others build on. |
| Communication | Reports progress and gaps honestly. | Raises risks and tradeoffs unprompted. | Trusted for advice; leads hard conversations. | Trusted on high-stakes calls by clients and Exalynt. |
| Lifting others | Learns from reviews, asks for help. | Gives useful reviews, helps peers. | Mentors and guides other engineers' delivery. | Raises the bar for engineers across Exalynt. |
The levels
A level fits when it describes how you consistently work, not your best week or your hardest one. You don't need to be equally strong in every skill; a level is the overall pattern.
Associate
You're building the fundamentals, and you deliver real value while you do. You're likely Associate when:
- You deliver a well-defined slice of a block end to end, with a more experienced engineer reviewing your approach and your code.
- You understand every line you ship, including what AI wrote, and can explain it at review and at the checkpoint.
- You tell the client honestly what changed, what's still rough, and what comes next, and ask when you aren't sure what they need.
- You ask for help early instead of getting stuck quietly, and you act on feedback.
- You review others' work too. A fresh question about unclear code is useful.
Toward Mid: you need less direction on how to do the work, reviews find fewer surprises, and you spot risks before someone else points them out.
Mid
You can be handed a goal and trusted to deliver it well. You're likely Mid when:
- Given a scoped goal, you find the approach, build it across the stack, and bring it to the stability level it needs without close supervision.
- The client can rely on you for your part of the engagement: you confirm the goal, raise risks and tradeoffs as soon as you see them in plain language, and recommend what to do next.
- You meet the checklist for the level you claim, and don't over-engineer past it.
- You can size Focuses in an estimate that a Senior engineer would mostly agree with.
- Your reviews help others improve their work, and you help teammates get unstuck.
Toward Senior: you take on work where the problem itself isn't clear yet, and your decisions start shaping other engineers' work.
Senior
You can be handed a problem, not a plan. You're likely Senior when:
- You start from a client's one-sentence problem and turn it into valuable slices, including recommending not to build something when that's the right answer.
- You make decisions with lasting consequences, such as architecture, data models, integrations, and technology choices, and make your reasoning visible.
- You choose the simplest responsible solution, build software that holds up when Exalynt operates it, and flag both over- and under-engineering in reviews.
- The client trusts your advice on direction, and that trust holds through hard conversations: bad news, scope cuts, and changes of direction, handled with clarity and care.
- You mentor, and other engineers deliver better work because you were involved.
Toward Principal: your impact reaches beyond the engagements you work on, into how Exalynt engineers work.
Principal
You set the direction other engineers build in. You're likely Principal when:
- You own the hardest architecture, where getting it wrong is expensive for the client or for Exalynt.
- You set technical direction that holds across engagements, and turn repeated lessons into reusable tooling and shared practices.
- Clients and engineers seek your judgment on high-stakes decisions, and you help them get better at making those decisions themselves.
- You grow Senior engineers, and the engineering standard across Exalynt is higher because of you.
- You model the values when it's costly, such as telling a client a truth that loses a block.
- You still ship. Principal isn't a hands-off level.
Two skills in more depth
Communication and judgment are where engineers most often misread what we're looking for, so they get a closer look.
Communication and working with clients
Working with clients is where communication matters most. Every Exalynt engineer works directly with clients, and clients decide after every iteration whether the next block is worth buying. How you communicate with them is part of the value you bring, so it's part of your level, not a soft skill on top of the engineering.
At every level, we look for engineers who:
- Listen before solving. Ask what the client is trying to accomplish, and check that you've understood it, before deciding what to build (details).
- Speak the client's language. Describe what changed and why it matters to them, not the activity behind it.
- Set honest expectations. Label work with its stability level, give estimates as ranges, and share bad news early instead of saving it for the checkpoint.
- Follow through. Do what you said you'd do, especially the small things. Trust is built there.
- Respect the client's decisions. Help them decide with the tradeoffs in view, then follow their direction, even when you'd have chosen differently.
- Treat everyone on the client's team with respect, whatever their role or technical background.
What grows with level is how much the client can rely on you. An Associate engineer gives clear, honest updates on their own work. A Mid engineer runs their part of the engagement with the client: confirming goals, raising risks, and recommending what comes next. A Senior engineer becomes someone the client trusts for advice on direction, and keeps that trust through disagreement and unwelcome news. A Principal is trusted on the client's highest-stakes decisions, and helps other engineers earn that trust too.
A good client relationship isn't telling the client what they want to hear. Trust earned through honesty counts toward your level. Approval won by overpromising counts against it.
Judgment and the tools you know
Experience with a particular language, framework, or tool doesn't set your level. Years with a stack aren't a level. Knowing when that stack is the right choice, and when it isn't, is part of judgment.
We look for T-shaped engineers:
- Breadth across the top. Enough fluency across the stack (interface, backend, data, integrations, and production) to own a whole solution and know what each part needs. Exalynt engineers are full stack by design, because problems don't stop at a layer boundary.
- Depth down the stem. Real expertise in at least one area, which you bring to the work and share with other engineers.
So tools still matter, just not on their own. Choosing the right one for the problem and its context, rather than the familiar one, the trendy one, or the one that looks good on a résumé (Exercise judgment), and learning a new one quickly when the work calls for it, are part of judgment and craft. Your experience influences your level through what it lets you understand, decide, and deliver.
What your level doesn't depend on
- Tenure. Time served isn't capability shown.
- Particular languages, frameworks, or tools. Knowing a stack isn't a level. Choosing the right tools for the job, and learning new ones when it needs them, is part of judgment (details).
- Where you live. Every engineer is paid the same share wherever they are (details).
- Hours or volume. Hours, lines of code, ticket counts, and how much AI generates don't demonstrate a level. A smaller change the client can rely on beats a larger one nobody fully understands.
- Being a Team Lead. It's a responsibility any level can hold, not necessarily a promotion (details).
- The client or their price. Your level is the same on every engagement.
- Bringing in work. Introducing a client doesn't change your level or your pay, including through the Partnership Program.
- Never making mistakes. Excellence isn't perfection. How you own a mistake and what you learn from it says more about your level than avoiding one.
How levels are set
Exalynt sets each engineer's level from demonstrated capability and responsibility. A Team Lead may share what they've seen, but levels are Exalynt's to decide.
Starting at Exalynt
- Your starting level is confirmed before your first assignment, along with your payout, in writing.
- Ask which level you'd start at, and why. We'd rather you join knowing exactly how we see your work and what the next level would take (questions to ask us).
Moving up
- The evidence is the work: your blocks and checkpoints, what clients could do afterward, how clients came to trust your work and advice, the reviews you gave and received, your estimates, how you handled what went wrong, and how the engineers around you grew.
- There's no fixed timeline or checklist. You move up when your work consistently shows the next level.
- Ask what's next. Ask Exalynt what it would need to see, and use the "Toward" line under your level as a starting point. Helping others and taking on harder problems are how you get there.
- A change in level is communicated before it applies, and applies to future assignments, not capacity already assigned to you (details).
Frequently asked questions
Will I be treated differently because of my level?
Not in how you're treated. Every engineer is owed the same respect, attention, and kindness, and an idea is weighed on its merits, not its author's level. What differs is the work: how much uncertainty you take on and how closely it's reviewed. If anyone brushes you off or talks down to you because of your level, raise it.
Does my level change what I'm paid?
No. Every engineer earns the same Engineer Share, 60% of a block's Capacity Payout Basis, at every level. Moving up a level means you lead harder problems, not that a block pays you more. See Engineer compensation.
How long does it take to move up a level?
There's no fixed timeline. Levels reflect demonstrated capability, not tenure, so you move up when your work consistently shows the next level. Ask Exalynt what it would need to see.
Do Associate engineers work directly with clients?
Yes. Every engineer owns their blocks and gives the iteration update at the checkpoint. An Associate engineer's work is more clearly defined and more closely reviewed, but it's still real work the client sees.
Exalynt isn't a fit for people who want well-defined tasks. How does Associate fit?
An Associate engineer's work is better defined than a Senior's, but it isn't a ticket to implement. You still understand the problem, build across the stack, ship, and explain the result to the client. The difference is how much uncertainty you take on and how much review supports you, and the goal is to need less of it over time.
Do I need to be strong in all five skills to be at a level?
Not equally. A level describes the overall pattern of how you work. Someone with exceptional craft who doesn't yet communicate risks or help others isn't working at Senior, and the reverse is true too.
I'm an expert in a particular framework. Does that put me at a higher level?
Not by itself. Deep expertise is valuable, and it's the stem of a T-shaped engineer. Your level comes from what that expertise lets you do: understanding problems, choosing the right tools for the job (including when your favorite isn't one), delivering across the stack, and helping others.
Does using AI to produce more help me move up?
Not by itself. Levels reflect judgment and the value of what you ship, not volume. Using AI well is part of the craft: understanding what it produces, verifying it to the level the work claims, and sharing what works with others (details).
Does a client's opinion of me decide my level?
No single opinion does. How clients come to trust your work and advice is part of the evidence, alongside everything else. A client being unhappy with honest bad news isn't a mark against you; hiding it to keep them happy would be.
Does being a Team Lead make me Senior?
No. Team Lead is a responsibility within your team, and any level can hold it. Your level stays the same, and so does your Engineer Share, the same as every engineer's. Like any work, how you lead is part of what Exalynt sees, but the role doesn't change your level on its own.