Desktop Engineer?? Is this a Real Thing?

[@cashonly2539]

I'd consider a desktop technician be categorized as an "engineer" must be proficient in SCCM and PowerShell if working in Windows OS deployment. Jamf with Shell Script and maybe AppleScript for macOS management. Almost like a junior admin role.

[@learnitfromwilliam]

like I said, the term engineer is thrown around way too loosely in the I.T. field and there are only certain roles that actually deserve the title.

[@ogbamboolbc8423]

The 1 dislike is a desktop engineer.

[@learnitfromwilliam]

I didn't catch what you're saying?

[@normandy17]

You have a point, I am a Sr. Desktop Engineer, focusing SCCM, Windows AutoPilot, MS Intune. I focus on modernization, innovation and automation. Standing up the infrastructure. But I have seen the engineer word passed around like help desk engineer, desktop support engineer…and read requirements and basically these people follow SOP, not designing and implementing Infrastructure. I think I’m a little shy on considering my self a systems engineer…

[@learnitfromwilliam]

I’ve been in the industry for 22 years and my current title has the word “engineer” in it and I hate it. I’m not an engineer.

[@dyo228]

I worked in a large enterprise environment and we had Sr. Desktop Engineers. If they imaged and deployed a variety of desktops such as thin client with citrix, regular local desktops and Virtual Desktop Infrastructure (VDI) for 10,000+ internal and remote employees and do large software/updates deployments using SCCM or IBM BigFix with custom automated powershell scripts and batch files then the tile would be justified in my opinion. I was not a desktop engineer, however, this was the technology they were using.

[@learnitfromwilliam]

It's the use of the word "engineer". I just have a very diff opinion on how its used so commonly in I.T.

[@KevtechITSupport]

That was the title given to me when I first worked in a MSP Environment. I was doing the following as a Desktop Engineer/IT Engineer: AD/Exchange 365 (mailbox creation)(Mobile device management), GPO, Vlan changes, troubleshooting software issues, pc moves, new hires, setting up access points, IDF room set up, putty commands, rack and stack switches and routers. The list goes on, it really depends where you work. Absolutely right on the pay rate, I was making 40k a year in New York. A lot of responsibility with horrible pay. Honestly, I feel like the title itself is given by HR because they don't do IT support. This job required a 4 year degree but I got hired somehow. Almost forgot (good to see you again on video).

[@learnitfromwilliam]

Hi Kev! You're proof of what I said...don't let the qualifications deter from applying because most of the time, it's bullshit and if you know how to interview, you'll get the job. Thanks for commenting as always!

[@cashonly2539]

You were making $40K/yr in NY doing all that? Please tell me that was 20 years ago and outside of NYC (Manhattan). Since you mentioned Exchange 365, it must be relatively recent. Dude, update your resume and move on.

[@KevtechITSupport]

@@cashonly2539 I make way more now. That job was a long time ago. I still live in New York.

[@rommelaquino1808]

Thanks for the feedback. Yeah..common sense "if your not engineering things, your not an engineer". I'm someone who is new and learning to be in this field, your replies are valuable information. Thanks again.

[@ArrowNation]

Desktop techs can break fix, Senior Desktop techs are starting to build images for companies, create user accounts, because system engineers are doing more complicated configurations they are leaving image build's, accounts being created in active directory to senior desktop technicians.. Desktop jobs may be entry level but jobs in elevated job rules are leaving it to desktop roles and naming them desktop engineers

[@PlayaX01]

it's a job title to make people feel important and seem like they're doing more than they really are

[@justadickhead3080]

Great topic. I did research after I saw your video today....and you guys are right. I seen titles like "help desk engineer, help desk analyst, help desk specialist..etc.

[@learnitfromwilliam]

thanks for watching!

[@riasathassan7592]

Hi mate how are you? I watched most of your videos and I am a big fan of yours mainly because you help us understand the reality of corporate level processes which is really helpful specially for fresh graduates like us. My question to you is that, I have been hired by an IT company for a Level 1 (Desktop Rollout Engineer/Media Operator) role last week and I have graduated last month from Masters in Networking and Telecommunications Engineering. I am not sure wether this position is relative to my course work or not. I am a fresh graduate with no work experience before. At this stage of my life, how do you think I should consider my current role and please give some of your best advices from your experience relative to my situation.

[@learnitfromwilliam]

Since you have no experience, this would be considered an entry level role. It may or may not be related directly to your degree but that's fine. Depending on the company, you might be able to move up the ladder as you grow or work there until you find something better. Just know that having a Masters will not be the magic pill to get you into a high paying, high profile position. You still need to gain the knowledge and experience.

[@bryanrodriguez9226]

What about IT Support engineer? What’s your take on that

[@learnitfromwilliam]

Basically, I have a problem with the use of the word “engineer”. It’s way overused in this field.

[@bryanrodriguez9226]

@@learnitfromwilliam I understand thank you

[@no_special_person]

How did I get here from TF2, I'm so confused Good vid tho

[@chrisgast]

Some may argue that designing and putting together a computer system is considered just as complex as a computer network - which to them, I'm sure it is. I agree that the term 'engineer' is rather inappropriate for a Desktop/PC Technician/Specialist role. But if that's what they are going name it and the pay is appropriate enough, then I'm applying. As long as I can do the duties of the position (I know I can), then I don't care if I'm called a Senior President of Desktop Engineering. Oops! Maybe I shouldn't say that. Maybe this (comments like mine) is where the job title madness came from. And salaries? Don't even get me started! Either hiring managers are clueless on the (fair) market values of the positions they are trying to fill or they are being cheap-stakes. It seems rather obvious at times why jobs go unfilled - not so much that there isn't qualified, skilled workers but the hiring managers don't necessarily know much of what the positions are that they are trying to fill. Which is rather ridiculous, because most (if not all) people that are promoted should be from such positions in which they manage now. Which means they should know a thing or two (seriously, much more than that) about the jobs they are posting as a hiring manager. I have no idea why people who have no experience or knowledge of computers (or hardly any prior experience/knowledge before obtaining an IT job) get put into manager/supervisory roles, other than they had a leg up with someone higher up. It truly is who you know more than what you know, and those that should realize that just don't (or choose not to).

[@learnitfromwilliam]

Amen to all of that. There are some serious fundamental hiring issues within I.T. organizations in particular that drive me insane. The problem is we have to know how to navigate them in order to be successful. That's my hope for this channel and my video's is to help with that as much as possible. Appreciate your reply and for watching.

[@good_time_guys]

I am currently in interviews and they trying to place me as a Linux desktop engineer. I had the same reaction. What the hell is that? Guess it's primarily writing deploy and automation tools for helpdesk but kinda getting red flags since I originally applied for systems engineer.. Engineer is definately is thrown around too much lol.

[@learnitfromwilliam]

Yup!!

[@thesanctionedone]

It's just a title to justify the overly onerous requirements listed for the position. They want to get someone with vast knowledge to leverage that into essentially a lower pay scaled position, while more than likely using that person's knowledge base for "other" projects/assignments. Big titles equate to more responsibilities with usually less than proportional pay.

[@learnitfromwilliam]

you said it!! couldn't agree more, appreciate you watching.

[@thesanctionedone]

@@learnitfromwilliam Working on my Oracle DBA, found your channel awhile ago. Thank you sir for the content. I'm looking forward to more.

[@eddier2k9]

💯

[@claytonljenkins]

I’m a IS student and when I was looking for jobs I would just omit anything with admin/specialist/engineer then I saw this and realized half the job titles listed are hardly relevant to the job tasks

[@learnitfromwilliam]

That’s Exactly right!

[@Eidenbites]

…….. i think it’s silly man but don’t take the title away from me cx I’m an engineer yaaaay

[@titanfallgamerwithnotitanf8187]

#Tinydeskengineer

[@no_special_person]

yippiyee hiyeahieaaa!

[@drcratty]

So the title says your going to tell us the difference and then you proceed to say they are not different. Yes, the word Engineer gets thrown around way to loosely and it gets silly. The trashman is not a "Sanitation Engineer" that said there is such a thing as the Engineering Process. If your job requires you to follow that process regularly to create solutions, not create accounts or run trouble tickets or deploy desktop images to laptops all day, then you are indeed an Engineer. Techs and Admins do not follow that process. They follow processes and use toolsets created often, by Engineers or right out of the box. I have been a Desktop Engineer for nearly 20 years and while I wont site my salary it well above the range you mentioned and nearing CCIE levels. That is because I use the Engineering Process to create complex solutions around Desktop technologies for Enterprise not because the companies I have worked for over the years have inflated the jobs by slapping the word engineer on the end. I agree whole heartedly that no one should be overly intimidated by over inflated requirements because that happens all the time. All of that said to suggest there is no such thing as a Desktop Engineer who is indeed an engineer because hiring managers use the term to loosely is kind of silly.

[@learnitfromwilliam]

The title does not indicate that I would discuss the two. I appreciate your perspective but your position is obviously a unicorn because most desktop “engineer” jobs have nothing to do with actual engineering. That’s the point I was making.

[@drcratty]

@@learnitfromwilliam OK so the description 😀

[@claytonljenkins]

Love this guy😂

[@learnitfromwilliam]

Not sure if that’s a genuine comment or sarcastic. Either way, I appreciate it.

[@theteflonron]

Great breakdown #respect

[@CandiceKMitchell]

😂😂 you’ur so bad, assembling a desktop can be complicated for some🙈

[@xxjarrodxx2007]

It’s clear you have no idea what you’re talking about

[@learnitfromwilliam]

You’re right. 22yrs in IT and I have no idea. Ok.

[@xxjarrodxx2007]

You can be in for a lifetime and still not know what you’re talking about.

[@ArrowNation]

20 plus years in IT I was in construction area low voltage fiber and cabling at data centers prior was a cell site technician climbing towers learning from the military later on after passing A+ and Network +, I bounced around desktop information security analyst, identity management now back at desktop as a lead I'm a part of a lot of jobs with system engineers I'm kept in the loop with patches that are pushed out, I do see issues when they happen even after they tested them and where we see these issues happening desktop technicians are always the ones that see the issues first, tickets with issues always fly to the desktop tech.. as a senior desktop technician I create the builds for different departments so there is a niche for people in the desktop relm, your world of desktop was basic now they are throwing it back to desktop to do image bills to be a part of network or operations senior level desktop job roles should be labeled Engineer, at my site we do everything there is no system engineer, network engineer or a IT specialist on site or even on call.. here in Chandler Arizona to Toyota Financial Services desktop team is the only one on site 24/7.. Also if Senior Desktop technicians are local and can do the job companies need, a person in the desktop role with a lot of experience, they are the best at fixing any issue that is escalated.. at our location only desktop technicians can go on site after hours because system engineers and Network teams are all offshore!

[@xxjarrodxx2007]

@@ArrowNation Yeah that seems to be the problem. Desktop Support and Desktop Engineer are not the same position even remotely. one is an entry level job and the other is a 6 figure expert level craft.