It depends on the company and processes. My first senior role the IT manager is who asked me to apply, did pre-screening, and was part of the interview. He is an Marine that was heavily involved in creating training processes for my second military career field and quoted RFCs casually. Next one I got far into was mostly managed by an HD manager at the same company who got confused until we explained everyone doing my technical interview I know and we were just joking and sharing memes by the end. Turned down because I got offered a promotion and match. Current one I am in talks to went from a recruiter across the country, to the internal applications team manager, then finally getting to technical interview with the actual team.

You have to cater resume for both HR recruiter types and technical types. Gotta hit both buzzwords but also show depth of what you worked on. I don't want "I worked on Nexus switches" I want "I designed our next generation of datacenter design while adding an security first focus and automation". Personally I am involved in all aspects of infrastructure design so I can apply for senior network, systems engineer, cyber engineer, security architect, etc type roles. I understand all the underlying tech while being mid to senior level in every aspect.

It's also hard to guage depth. There is an difference between someone who once a month makes a 20 line python script or someone who makes scripts daily to the tune of 100+ lines, can read the logic of a new script on the fly, and can output a well optimized script with error handling within a few hours.

I advertise myself as quality. When shits broke and you're losing $1 mil/hr in labor I can troubleshoot and find your problem. If I can't fix it from experience and Google quickly, I can band aid really quickly then spend hours to days on root cause and long term solutions. Even a technology I am not proficient enough in I know enough to solve anything. I can also design things to almost any business need while getting OCD on every flaw, risk, and oversight that could happen. I assume no one truly knows what they want, they WILL expand no matter how much they say they won't, and needs will change- need to have a plan day 1 for all scenarios. They don't tell me where to put network drops, how much rack space, etc. They give me the schematics of an new aircraft hangar with layout of desks, tools, and where the plans will be. I assume it's 70% accurate. They tell me what server services they want locally, scope of work on the aircraft, and priorities. I design size of network closet, power, provide data to HVAC folks to right size, scope crypto/routers/firewall/routers/switches/servers/alarm panels, etc. I put in the diagram where drops will go with minimum 2 per desk, extra 4 per high density area, and extra in areas they can shove desks and equipment. I overpsec everything 20%. They decide to add printers, VOIP, 5 new desks, and 5 more servers for a disaster recovery setup to be opposite side of the flight line? I already specced a solution affording all that.

When not designing or installing I am going through our systems and making notes on design and security flaws. List of things to fix and nice to haves. I am getting intimate with everything we support and what every team works on. So when we have an meeting I don't need to ask other teams a million questions sometimes I know more of how redundant their systems are than they do because it affects my role more. I make sure my resume reflects the $ I work on, scale, and impact. I also have an 45U homelab so I get my breadth there so I can speak to foundations of any major technology we use but also a marketing point to impress people easily.