What 'senior' actually means for a Shopify developer

I describe myself as a senior Shopify developer, so I owe an explanation of what I mean. It's less about how long you've done it than about how you do it.

This is a personal view, not a definition from any authority.

What I think it isn't

• Years served. Seven years of doing the same thing is one year, seven times.
• A long list of technologies. Breadth helps, but a list of tools isn't judgement.
• Never being wrong. Seniority is better recovery, not an absence of mistakes. I've shipped bugs. The difference is how quickly they're found and how little they cost.

What I think it is

1. Owning outcomes, not tasks. A task is "add this section". An outcome is "product pages convert better and don't break". Senior work asks what the change is for, and notices when the requested change won't achieve it.

2. Judgement about trade-offs. Liquid or a custom storefront. A custom app or a settings change. Fix it now or log it for later. There's rarely a right answer in the abstract, only a defensible one for this store, this team and this budget. Being able to explain why is the skill.

3. Making the safe path the default. Working on a duplicate theme, testing the full journey after a fix, keeping changes small and reversible, writing a short note on what changed. None of it is clever. All of it is why you can be trusted with a production store.

4. Being honest about what you know. "This is measured, this is an estimate, this I haven't tested" is a sentence I try to say often. It's the same instinct behind the unknown state in my scanner. Confident wrong answers cost far more than an honest "I'm not sure yet".

5. Debugging with discipline. Reproduce, isolate, change one thing, verify. Under pressure, people skip steps. Seniority is keeping them. I wrote down the routine in debugging theme and app conflicts.

6. Measuring before and after. "It feels faster" isn't a result. Which page, which device, how many runs, which metric. See Lighthouse lies.

7. Making other people faster. At Pepkor I built internal tooling used across multiple store instances to standardise operations and help the team work faster. Senior work often shows up as other people's time saved.

8. Communicating clearly. To non-technical stakeholders, in writing, across time zones. A clear update that says what changed, what's next and what's risky is worth more than a clever commit.

9. Knowing the platform deeply, and its edges. Liquid and themes, yes, but also the APIs, webhooks, limits and compliance rules around them. Building and submitting my own app taught me more about the platform's edges than any client project, which is a large part of why I did it.

10. Writing things down. Decisions, lessons, limits and open questions. I keep a lessons-learned file and read it before touching the code. It prevents repeating mistakes, and it helps the next person.

How you can tell, from the outside

If you're hiring, a few signals I'd look for:

• Can they explain a decision, including what they rejected and why?
• Do they talk about outcomes and measurements, not just features?
• Do they volunteer the limits and risks of their own work?
• Is there evidence of finishing: shipped things, not just started things?
• Can they write clearly?

What I'm still working on

Seniority isn't a finish line. I'm early in publishing my own product, and there's plenty about running a live app, with real merchants, that I haven't done yet. I'd rather say that than pretend.

If this is how you want your Shopify developer to work, let's talk.