Suggestion: Don't call yourself "A jack of all trades." When you call yourself that, some people/interviewers will add "master of none" mentally. Call yourself a "Swiss army knife" or something.
Lately the idea of a "specialist" (at least in webdev) has come to mean (in my head): "I really know how to use this particular framework, but do not understand any of the surrounding technology. If I reach a problem, I will bloat the code with more libraries until it starts to work."
Full stack means a specific kind of developer, though. I would never call myself "full stack", even though the "stack" I work on goes from the kernel all the way to UI code.
That's my "stack" too, which is why I once called myself "real full stack developer" once in a conversation. It was intended partially as a pun on the "full stack" term, but I said it only half-joking.
When people ask what are my particular areas, I'll say I mainly do... I'm expert in... I have strong experience with... over the years I've worked in several technical areas...
And list 4 or 5 different specialisms where I would realistically do ok if interviewed in those areas on the spot without warning.
I don't know if that would work for someone who really is a generalist without specialist knowledge at the current stage in their career.
In my case, I really have gone much deeper than most people into a number of different sounding domains. Not different skills or tech stacks, but really very different tech areas. I'm often regarded as interesting because of that, rather than "master of none".
In my case, I call myself a specialist in one of the relevant fields I have worked in the last 3 years. Then I mention all the other things I have done when I have a chance. Don't call yourself a jack of all trades, make them call you that.
If you really are a jack of all trades, it doesn't matter. At that point, you're smart and capable and generally a great hire. If a company isn't hiring well enough to recognize that, you don't wanna work there anyway.
As a systems engineer who usually works in the intersection of HW and SW (usually working with systems requirements or managing interfaces), I tend to add 'master-of-none' myself as I'm proficient in neither. :)
Although I've interviewed for 2 companies in the past that actually appreciated this and basically called me like this themselves. :D They worked on actually complicated stuff and also expected some kind of work sample. Turned out both were jobs where you can burn out quickly so I didn't stay long at either.
But true, normally interviewers already get confused when you mention a skill that is not directly required by the job ad.
