A resume listing six stacks reads as none of them. Pick the one you can defend under thirty minutes of follow-up questions, put it in the headline and the first two roles, and demote the rest to a single line. Breadth becomes an asset only once a specific depth claim has already been established.
Client work is usually invisible and often confidential, which leaves an interviewer with nothing but your description of it. A small public repository, a written design note, or a deployed side project gives them something to inspect. It does not have to be large. It has to be real, recent, and relevant to the role you are targeting.
Consulting work carries genuinely hard constraints: fixed deadlines, legacy systems, migrations you did not design, and stakeholders who change requirements. Those become engineering trade-off stories when told as decisions with consequences. Told as process descriptions, they sound like status reports. The raw material is strong; the framing usually is not.
These phrases are visible, grouped and relevant to this page. They help search engines understand the page without hidden keyword stuffing.
Lead with the one you are targeting and present the rest as adaptability rather than as an inventory. A single sentence, such as delivering across four client environments while owning a payments integration end to end, conveys both at once. Interviewers penalise unfocused breadth because it makes level assessment hard, not because breadth itself is a weakness in an engineer.
Yes if it is small, finished and relevant to the target role, and no if it becomes a reason to delay applying. Two weekends producing a deployed service with a readme and tests is worth more than six months of an unfinished ambitious project. Its job is to give an interviewer something concrete to open, not to impress anyone with scale.
Describe the system, the scale and your decisions without naming the client or exposing proprietary detail. A large European retail client, four million daily transactions, ownership of the order reconciliation service communicates everything an interviewer needs to assess you. Confidentiality restricts names and internals, not the shape and difficulty of the engineering work you did.
Usually yes for the first move. Domain familiarity is the one part of your background that transfers without translation, and it shortens both the screening conversation and your ramp-up time. Change domain and stack simultaneously and you are asking a company to take two separate bets on a profile it already regards as unconventional.
