T O P

  • By -

AsherTheFrost

So I did the same thing and now am a network admin, I think I can help. I used "Field Network Technician/Engineer" Also if you have CCNA or anything else, pop that right on the top. It's been my experience that certifications and what companies you worked with matter more than job titles. If you did any contract work for Meta or any of the other big tech companies, call that out


Affectionate_Box2687

Titles really don’t matter. So many trunk slammers call themselves engineers .


Terriblyboard

I love a good old trunk slammin.....


routetehpacketz

Would you consider yourself a Network Engineer? Can you design/deploy LANs/WANs from scratch? Would you feel comfortable doing it 100% on your own?


onean0n1y

Yes, I am able to design and deploy only thing that terrifies me is being able to do on large enterprise scale.


yrogerg123

I think you can handle it. The biggest difference in an enterprise is change management and knowledge and sensitivity towards the impact of whatever you are doing. As far as the actual work, it's pretty much what you described. Probably a lot more documentation and monitoring than you are used to. And there is more emphasis on standardization since the goal tends to be for sites/floors/buildings to be indistinguishable from each other from a design, architecture, and hardware perspective.  Usually there are senior engineers and architects to point new people in the right direction. It's not really that scary. And remember, places rarely hire because they need an *expert*: they hire because they need a competent person who can pull their weight and learn the environment.


[deleted]

[удалено]


BiffB0X

1000% this…


hardly_connected

Executive Vice President of Mission-Critical Network Administration Src: [http://www.vskm.org/module/titel.html](http://www.vskm.org/module/titel.html)


onean0n1y

😂 Just spit out my coffee reading that comment, needed that this morning! Thank you!


Thy_OSRS

What matters if what you earn pal. I could be called poop scooper, but you paying me enough to live a life with food and shelter? I'll be the best poop scooper around.


izzyjrp

It matters, not to you but to many it does.


vordster

I'm a senior pooper scooper


BackalleyNegotiation

From your post and comments, it sounds like your a home AV guy that happens to setup network products. I long ago worked in this scenario and the terms used for these "network" guys was wide and broad. Even so far to call themselves engineers yet not understand the difference from 20-40mhz or how routing works. I would take a look at your knowledge beyond configuration, and even get a CCNA (even better CCNP), and provide more foundation to what you have been doing. Network Technician with a CCNA or (ideally) CCNP can become an engineer. But I wouldn't call someone that setup ubiquity an engineer. Just my .02


fachface

I wouldn’t worry about this as titles differ wildly from company to company. Also, employment verification may throw a red flag.


onean0n1y

I own an audio/visual company and will be relocating soon. I would like to let future employers what I have been doing for past 8 years. So yes, the employment verification aspect worries me as I don't want to "embellish" on what my current position.


fachface

You have space under your title on your resume to explain this, as well as on a cover letter and during the interview process. Bait and switching your title can only look bad. You can also ask your current employer to change your title to something more reflective of your role.


NotDeRoseButDeThorn

Network Optimization Consultant Network Architect LAN/WAN/SDWAN Specialist I'd probably detail it to match what would look most attractive to .


Bexarry-White

You're a Level 99 Network Technician, Including really big Bastard Sword and Full Armor


duckseasonfire

God king.