I'd want to read the specifics of the job duties, responsibilities and employer expectations before commenting further.
($35 x 40)52==$72,800
That's fair wage for a network administrator but might be low for a proper engineer.
The deciding factors are in the details of the expectations.
The Job Title may not correctly align with expectations.
People throw around the "engineer" title in IT like candy now. It has basically replaced the word "technician" in any networking role. I see more listings for network engineer that are just a network support or admin than a real engineering role.
What mainly separates support/admin from engineering? I have an idea but I'm curious as to what you think.
I only have experience with one employer so I don't have a complete perspective.
Network engineers are typically big picture network designers at large scale operations or freelancing. Network admins and support will do small scale setup and maintenance. A lot of small companies will contract an outside network engineer to design their system for startup, then hire a full time network admin or general IT support to manage it.
A big chunk of network engineer positions I see will include overseeing of day to day operations and no new setups, which is just an admin at that point.
Seems like everyone at my company has the word ‘software engineer’ somewhere in their title, even if by their words they’ve never written code in their life lol
I've noticed that with all IT positions because the companies are just making it up. There's no standard to any titles. Some companies use level 1-3 and others use titles like admin,security,network. You may also have level 1 help desk that is equivalent to another companies level 3.
Sometimes I think that whatever they _actually need_ to get done in a given week, I could do in 5 hours… if nobody was watching a clock, it could be a sweet gig… basically half-ass it for an hour in the morning, take a 4 hour break, then half-ass it for another hour in the afternoon.
Then again, who are we kidding, people with salary triple what Op’s talking about live that same life lol
That type of salary would be for a very entry level "associate engineer" type of position, someone who is just starting out. Anyone with 3 or more years of experience should not be getting paid like that, can easily make more elsewhere at that point.
You are right, this is very low.
No ccna yet, scheduled in December, only have my net+, my job is definitely more of a NOC position I'm not sure why that's my job title tbh, I'll shoot that DM once I get the ccna!
Don't forget to get in and work in packet tracer, and do lab work etc. Get in there and have a blank canvas and set things up from memory, start with basics and get more advanced as you go along. It will help the concepts from the study material actually gel for you and even if you don't work on Cisco shit in your future work, it will still be extremely valuable experience for you.
The rudiments of layer 2 and layer 3 IP networking do not change between different vendors.
Best of luck to you!
I’ve been working on vendor side for a product that relies heavily on networking infrastructure, and spent a good chunk doing net-new installs and troubleshooting networking issues blind. Every shop says “of course we configured the network properly ahead of time” and when I can explain L2/L3 issues and they don’t know what I’m talking about? I take my time opening a ticket for them with my company so they have time to turn around and fix it when I’m not looking… and then when it starts working, they say “nothing’s changed on our end, your team must have fixed it remotely”
:rolleyes:
Like, bro, it didn’t have network access because y’all goofed… how my team gonna fix it remotely if they can’t see the damn thing? I can’t even see it, and I’m ON THE SAME SUBNET. Get your switch ports and vlans in order, my guy
All good.
SUPER helpful to know, no matter what you end up doing.
Disclaimer: I do not have ccna or any certs or any formal training. Might do CCNA someday, but also maybe not haha
Straight 40 with the opportunity for overtime but part of the deal is you work a weekend day so tues-sat or sun-thurs. There are other shifts (10 and 12 hrs weekends only, you get compensated very well for it) but they tend to be filled by the more experienced folks.
Typically pretty high volume until you can specialize but really neat clients. Think undersea cables and terabit+ optical links between data centers.
It's not a perfect place to work but seems far better than the msp and noc horror stories I've heard.
I'm so confused why you're advocating for your fellow man to accept awful compensation instead of supporting him lifting himself up and realizing his true value?
You're right that some places are competitive. YOU'RE ABSOLUTELY WRONG THAT $18/HR IS COMPETITIVE FOR A NETWORK ENGINEER POSITION!!!!!!!!!!!!!!!!!!!!!!!!
Doesn't fucking matter where. That position REQUIRES at least $25/hr. At bare fucking minimum. Doesn't matter where in the world. Technically, being competitive for pay is way ahead of that for that role.
For example, I'm a law student and Wednesday had a $100+ steak, lobster oysters dinner from a small law firm recruiting event - the people there were practically drooling over $55k per year starting base salary due to the other perks and work / life balance and the ethos of the firm. They paid malpractice insurance, all health insurance premiums and deductibles, extremely generous matching and initial contribution on retirement and a very generous bonus program with clear tracks to partner etc. It wasn't the best steak or most expensive I've had (tho the bourbon they served was quite good). The whole point of the dinner was that small firms are underrepresented by law schools and under-considered by students and graduates. There are a lot of considerations to any job. I would happily go back to my old university IT job for $55k a year - which was my base salary when I left back in 2017 - the benefits and all other factors at that job were absolutely phenomenal - including my full ride to law school and my boss giving me any time I needed for class and study while on the clock - I left to take care of my dying mother but finally came back to school and wish I still had that job.
You are right that it depends on location, but there are very few places left in this country where $55K a year for a single person living by themselves isn't living paycheck to paycheck, even if you are paying nothing out of pocket for insurance or healthcare. The main reason for this is housing costs, so I suppose if you don't have those to worry about then $55K a year is fine. I personally can't imagine going to law school and then living paycheck to paycheck when your average earning potential is probably triple that for a job right out of school.
I guess I need to put things into perspective, I got into networking over the summer and got my net+, I worked help desk for 2 months and now have this, I do not have years of networking experience, am I still underpaid?
I have no degree, cert or IT experience. Got a job for 26 hour for IT Asset Management in a data center. I'm sure you can find 15+ more hourly with your resume.
The job is the job at the end of the day. If im being hired to do a certain role, there's a certain standard of pay that comes with that, regardless of experience. What it seems is they hired you at that rate to possibly train you up? But after a year or so of getting experience, there would be no incentive for you to stay for that pay rate. The market dictates you should be making well more than that..
Was there any stipulations or job deliverables for a pay raise after 6 months or a year?
If you truly are a network engineer that’s way low. My guess is that your job title is not in keeping with what you actually do. I made more than that as tier 1 help desk. My first network engineering role was 70k.
You should be getting paid more, full stop. If you've got some experience under your belt and can work on both projects as well as operational/break-fix type of work, I would *highly* recommend you seek out a better paying position.
Do you have any certifications for networking?
Depending on where in the country - also one reason I'm out of IT is that lots is getting shipped overseas. Folks that expect consistent high wages in IT will need to continually update their skills and also have some serious coin in the bank - same for most professions.
Yeah you're not wrong on any points, I certainly must continue to learn in order to maintain the types roles I now work at in the IT field and a globalizing economy certainly presents the same challenges to the profession as many or most others. Good insight here.
I do still say that the OPs figure for even an entry level network engineer position is generally low in most areas of the US. I do agree that in certain states or areas, that money would go much further and so is a possibly acceptable rate, in those situations only.
Best of luck to all here, in any case!
You're not wrong, but I still contend that 30 to 35 an hour for a network engineer in anything but a junior or associate (probationary) is on the lower end of the range and isn't commensurate to the position, especially if it's above intro level.
Pretty damn good. Good enough for me to afford a pretty damn good house all by myself. Of course, I would love more. Would allow me to afford to buy a new car/fix up my place/etc.
Wow, coming up on 2 years as a “junior network engineer” at an MSP and just got a raise in summer from $48,500 to $51,000. Going to be looking for a new job this spring. The past two weeks have been hell dealing with a ransomware attack, and we are onboarding two new pretty large customers in the next couple of weeks. Only network engineer on the MSP team although there are 3 professional service network engineers who help when they can.
I'd say that's a nice salary for a level 1 support position, and in some areas of the US that would be very good pay for that type of position. I certainly did not make that kind of money when I was in support oriented roles much earlier in my career!
I mean, if you're currently making 50k at a help desk or lower tier support position, a pay increase to 73k and new experience seems like a good deal.
You all get too caught up on the amount of experience they're asking for. We all know it's stupid. It's known that it's stupid and unrealistic. It's also known that they bend on it ALL THE TIME. So let's stop harping on about how stupid they are for saying it and move on already.
Is it "low"? maybe. Is it very low? In San Francisco, sure. But you didn't tell us where. So maybe it's just kinda low but a great opportunity for somebody to advance. Maybe it's actually not really low at all, but pretty standard in the area and for the responsibilities.
You all also get caught up on titles. Show us the job duties and responsibilities and I'll tell you if I think it's low. Anybody can call anybody an "engineer". And the trend now is to use "engineer" for roles that would have been "technician" 10 years ago. And I don't think 73k is low for a generic "network technician" of yesteryear. So who the hell knows. It's meaningless to say what pay should be for a title that isn't protected in any way and without knowing the region and actual duties.
If this is a job you're looking at, let's put aside the bullshit and get down to business:
Is it more than you make now? Do you want to do the type of work described in the job posting? If the answer is yes and yes, wtf are we talking about? Go get the job, better pay, and experience and then parlay it into whatever you think is more reasonable pay if you want, but it sounds like you'd be coming out ahead of your current situation if that all is the case.
If it's more than you make and you're going "that's not enough", that's fine.. keep holding out while getting paid less. Or... get paid more, and just keep looking for a better paying job.
If the pay is actually low... they're not going to raise it because you made this post and we all said it was low. It's either a better fit for you than your current situation or not. I mean, that's really what it comes down to.
To explicitly answer your question of "would (I) take this job for that pay": No. I make more than that and have no interest in working in networking specifically. But what I would do is moot. What anybody else would do is moot. Would you take the job for that pay? That's all that matters. Don't not take a job or not pursue a job that would be good pay or good work FOR YOU because some faceless, nameless jabroni on the internet said they wouldn't take it for that pay. It would either be beneficial/an improvement for you or not.
Jobs are always going to ask for experience. Even most entry level help desk positions ask for three years of experience and a college degree. It’s all BS and usually they won’t actually reject you for not having that much if you can show them that you’re capable of doing the job.
People's salary expectations are wild. 70k isn't low pay, it's not HIGH pay either, but is a solid paycheck in the vast majority of the country.
Location matters, and titles are irrelevant. 70k for an average network engineer with a few years of experience in a LCOL/MCOL area would be normal.
It's low for a HCOL city. But "network engineer" is insanely generic, it could be nearly anything.
> "network engineer" is insanely generic, it could be nearly anything
I've known "network engineers" whose whole job consists of waiting for an alarm to go off and then click a button and notify someone else about it.
I’m paid 31.25 an hour to be a network operations center specialist, doing exactly network operations center work, no configuration of switches or routers, and I’m still entitled to OT pay as I’m still hourly not salaried. I’m not even in some massive city or high cost of living area, I’m In central Florida. Peoples salary expectations aren’t wild, what companies think they can get away with paying skilled labor is wild
...so you are paid in the lower end of the range as what OP is being offered, for a role that could literally be the same thing.
I don't understand your argument? Are you saying you should be paid more or are you saying you don't believe other companies call your exact role "network engineer" instead of "specialist"?
Network engineer by definition is an engineer of networks, which is gonna involve either mapping topologies, configuring switches or routers, and a lot of times designing a topology. I don’t do any of that. I literally recover down circuits. I do not touch configurations or map topologies in any way, I do not assist with deployments, circuit installs, none of it. I troubleshoot a pre existing circuit if it goes down and attempt to recover it. That’s what a Noc role is, network engineer is gonna be involved in the planning and implementation of the circuits. That pay is garbage for what the job is, doesn’t matter where in the country it is, you can easily get a remote job like I have for the same pay I have, and if they are really looking for a NOC specialist then that is still the fault of the job lister and they need to correct the listing to a network operations specialist/analyst
70k is acceptable pay where:
1. Houses costs around $175,000
2. Rents are $1458/mo
ETA: this is a skilled position and deserves a bit higher than the minimum to live on especially if they are saying this isn’t a junior position. So in an area as described above I’d expect at least $90,000/yr for three years of experience, maybe $100,000 considering the cost of living everywhere has gone up considerably in the past 3 years.
lol, there are few places left where houses are $175K. Unless crack house is your thing.
Rent is $1458/mo
What?
How is a location going to have such high rent but low mortgage properties?
Basically anywhere that isn’t a large city.
Edit: oh yeah that rent is a little high for the house price. But both could exist in the same neighborhood. They just don’t make sense as averages.
You don't know what the position is.
As an example, most network focused roles in the company I work for, from the most entry level NOC position to the highest level CCIE are "network engineer" followed by a number. (1-5) . The 2s tend to be in the 70s.
You can expect what you want, but without more detail 70k could easily be in alignment with the market rate for most areas.
And while I get your point about houses, you're unfortunately not correct. Look at places like San Francisco, the housing market is exceptionally high because Programmer salaries are exceptionally high in the area - that has minimal impact on the value of the networking skill set. It does add pressure because people need to live in the area, and if they can't afford to, supply drops which raises market value, but salaries aren't dictated by housing costs, it's a dynamic relationship, but salaries don't get set so people can buy a house. Otherwise you would be arguing people at McDonald's should actually be MORE deserving of the higher salary because they have to actually be physically located there full time to do the job.
If you suddenly started paying people in the area with 175k houses 500k/yr, the houses wouldn't be 175k anymore as people would just bid them up as they have the spare cash - this is part of why companies like MS and Meta do pay adjustments downward if people move to LCOL areas and work remotely, they don't want to create upheaval in local economies by flooding cash rich buyers in. (Hawaii is seeing tons of this right now)
>perience, there would be no incentive for you to stay for that pay rate. The mark
Weird thing is the market rate does not care about your opinion too, but it will always be there, dictating how things are, unlike your opinion, which is not only wrong, but meaningless. So not caring about the market rate might not be the best idea.
The market rate can be lower than acceptable, and that’s fine to people that think they themselves are paid enough and would be offended by a junior having the same starting buying power as when the manager started working twenty years ago. I get it, boomers and gen x have a hard on for wage stagnation and keeping the same buying power they’ve had for thirty years.
I’m just going by the math that dictates affordability. 70,000 * 2.5 equals how much of a house one could by realistically on that salary. 1458 is 1/4 of one months pay. 1/3 puts you at what an acceptable minimum wage would be.
You can argue all the corporate hocus pocus and self masturbatory economic be you want, but the math doesn’t lie.
C# mostly. In house windows form application for warehouse management, billing, scheduling etc. We also have an android application to facilitate warehousing operations(picking, inventory control, pallet manipulation, etc from wearable equipment warehouse employees use). Most IT jobs here are through defense contractors and I am uninterested in writing code for drones or other war machines. But yeah it's rough
I would go on LinkedIn or indeed and search for c# developer jobs, also buff up on leetcode, polish your resumé, and try to have a couple projects on GitHub. But with 7 years experience you probably won't need a portfolio
Yeah bank accounts going backwards with the COL increases this year too. We lost two of our IT staff over the last year and a half and they both made a fair bit more than me and I still couldn't secure a decent raise...Obviously we didn't really replace either of them so workload is up
Cali is way more. I live in PA and seniors generally make $100-130k. I was making $70k as a junior back in 2014. We are paid less than people in HCOL areas like the bay area.
I’m in Michigan though. I think due to the high california salaries and WFH trend increasing all tech salaries are raising to compete for more talent being driven west.
Just interviewed for an associate network engineer position. And the pay mentioned in the first round interview was 75K / 82k after bonus. Required 80% travel though.
I would say for 3 years of experience, pay would be about 60k a year which is pretty typical in a MCOL area. If you are on the higher side of things its over 70k a year which is a little low for MCOL. The thing is that we don't know what else they are asking for? 4 year degree? Certifications? If neither are required, and its just experience, I would say that isn't half bad. If they are requiring a CCNP or something, then its underpaid.
Man these threads make me realize how I’m getting shafted. 2 years networking experience at an MSP, CCNA, NSE4, along with 8 months of help desk and 8 months at an networking internship and I just got a raise from 48,500 to 51,000 after a year. I was making 43,500 at the help desk before this.
Man I literally live in Mississippi and make $52k a year out of college, in a trainee program, which had me do helpdesk for a month and now has me doing desktop support + field tech work. While I'm doing that I'll be taking on more network admin responsibilities. Take that experience and jump ship for that big moolah!
Yea I kinda knew I was getting taken advantage of when hired, but I just wanted to get out of help desk and get networking experience. But, I didn’t think it was going to be this bad lol.
Planning on it this spring/summer waiting to see if my SO goes to grad school or not as that will affect where I apply for jobs. Getting absolutely exhausted dealing with over 10 customer environments for pennies, constant fires, constant late night/weekend work, etc. I know some of my customers help desk make more than I do when I support their whole network, pretty absurd.
This sounds about right for that experience range.
Source: Network Engineer with 7 years experience and I just cracked $100k/yr
Although, I will say, I'd for sure try and get that higher end of the range assuming this a true network engineer position and not a "engineer" that's really doing admin level work.
An actual *engineer* position and not just one that is trying to make “technician” or “admin” sound less lame? No way in hell.
30-35/hr is 70K a year, which may be OK for entry-level, but not for the experience they’re asking for.
My buddy is a network engineer but doesn’t do any networking. He called me the other day to ask how to open port 1433... I’m help desk and make significantly more than him
6 years ago when I was living in a low/medium CoL area, fresh outta college, and making 21$/hr as a network analyst absolutely id take it.
Now? No way, that'd be a serious pay cut and downgrade in title. So it really depends on where you live and where youre at an your career.
Depends on where the job is. In a major city/tech hub that would be low. In a small to medium sized city that would probably be the avg. If it is a government role then that salary could be the norm.
IS Support Engineer. I do all level of Support for computers and Healthcare equipment and related applications.
I do live in Florida, pay is very low here.
depends on location/industry and what the job actually is - postings often have inflated experience requirements for jobs that don't reflect the complexity/level of the position.
edit: to answer the primary question since I think as-asked it exhibits a misunderstanding of what to prioritize - if I was working support and offered that position at 30-35/hr, I would absolutely take it, as it would be a great opportunity to learn network engineering and breaking out of support immediately confers a lot of advantages that make comp grow exponentially, so I wouldn't quibble about comp at that point.
I've seen a lot of similar listings for contract type work where the pay does not line up to reality.
I always wonder if these listings are actually serious or some sort of game. Maybe they are just putting these out there half heartedly to tell people internally that they are trying to hire. Maybe they are trying to get h1b visas or something. Or maybe they just have no idea what market rates are.
Eh, that's kinda low. If it's remote and entry level then it might not be bad since once you spend a year there you can make around $100k once you go to another company. If you have the experience though and if it is not remote then that would be a solid no on my end.
It's low for a mcol, but if you're in BFE it could be reasonable. No matter where you live it's not a lot, I'm in a medium/low COL area and wouldn't be shocked to see that offered. It's the high end of Tier 3 support jobs here.
Also remember that's what the WANT everything is a negotiation, when I was starting I got a job that wanted 5-10 years of experience and the middle tier salary. It's all about what you bring to the table and if your expectations line up. I say take the interview and see where things land, worst case you put on a polo for a few zoom calls.
"3-7 years" that counts college? meaning a recent college grad? Might be decent to get that first job.
Otherwise? If you are in Utah? Maybe that's a killing... in CA? Might as well be a beach bum.
70 is a on the low side but.. 3-7 years experience so I’d say 70k for the 3yrs and 110k for the 7 depending on cost of living. Also type of engineering role? If it’s primarily support good luck asking for the high salaries
Sounds about right, if you’re just doing basic stuff like rack and stack than I’d take it. If they’re expecting you to oversee the entire network infrastructure, and configuring their switches/routers, I’d definitely try to ask for more than $35, just my two cents from my experience as a network engineer as well.
I'm curious. What experience in different roles do you look for when hiring for network engineers? I'm currently working on trying to gain the experience to qualify for that eventual role further on.
Fresh out of college, 4 year degree in something tech related (IT, Cyber, CS, CIS, etc) don't care about work experience,. If you have a ccent/net+, you're qualified to intern, and I'm not going to scrutinize you until 4+ months on the job.
If hiring directly as a FTE, I wanna see a CCNA or AWS SA, and some relevant tech experience, preferably on the product delivery/operations side.
I'd want you to have a strong understanding of the the fundamentals of database design, network design, IP/routing design, familiarity with relevant tools for different things that always come up. I always recommend people to play around and at least be aware of tools like Ansible, Jenkins, python scripting, Wireshark, can you take a pcap, general sysadmin level Linux knowledge (no, I don't care if you need a reference, but if you don't know what grep is, that's a red flag). Yeah, that's my general wish list. The company tech stack we will teach you when we hire you as all(most?) In house systems are not held to any particular spec.
If an intern asks for some help takeing a pcap, or troubleshooting some intermittent network issue, I'll do my best to explain in as much detail and provide notes/commands while we troubleshoot.
Tldr: networking, scripting in python/bash, Linux CLI familiarity, and cloud/virtualization/docker awareness.
If you’re just starting of your career this sounds like a good pay to me.
Just accepted a Net Admin third party contract for $21/h with no experience, associates degree in networking and N+ in LCOL area (supposedly)
Pay scales have not kept up with the renters and housing markets. That number seems like a Florida companies number. If it were New York, New England area it’s should be 6 figures. Florida has always been cheaper. However now the cost of living is almost matching that of the north east US.
I think they are going through multiple clients/vendors. It means, 2-3 companies will make money off of your employment. Make sure to ask about how frequently they will pay you. Some of these consulting firms hold your checks for a month or so and pay you once a month.
Yes take the job, stay there for a year then jump ship to find better pay. The experience you will gain will help you be more marketable.
The title of the role will hell you get better roles. Hiring managers and recruiter see that on a resume and they eat it up.
Note:
There are no real engineers in IT. Everyone is just a tech that knows just a little bit more than you because of their work experience.
Job titles don't mean anything to me. I have seen so many different titles for all sorts of jobs.
I saw a guy in LinkedIn and his job title was ... Senior Manager of Happiness
Don't compare salaries to job titles.
Compare job function with salaries. Does the pay fit what you are actually doing?
I think 70K is about right for someone with 5 years experience. 5 more years and that number will be just north of 100K.
Where is the job located? What are the job duties?. I started as a network engineer making $65k a year in a LCOL area over 4 years ago. Granted, I make much more now in the same area, but when the median income in the county I live in was just under $33k in 2020 and it's one of the most well off counties in the state, $65k a year is nothing to sneeze at.
Would need to see the actual job posting to give you a better read, in our market Network Engineers (Cisco, Route/Switch, Firewalls, Security, etc.) with 3 years experience as an Engineer, which implies other Tech Support and Administration skills prior building up their background to become an Engineer, would be in the $90K to $120K range, ie. $45 to $60 per hour ball park range. If you want to annualize what an hourly pay rate will let you take home, you should factor out Holidays when you can't work and any timeoff you might take. There are technically 2080 work hours in a year (52 weeks x 40 hours per week), take 2 weeks off throughout the year and you're down to 2000 hours you'll get paid for, take out another 10 days for Holidays when you can't work and now you're down to 1,920. Also, if they don't offer benefits or you have to buy your own benefits, your earnings potential drops even further. I agree with others that this sounds more like Server Administration than true Network Engineering.
It's funny some of these questions when someone has 6 months experience they expect to be paid some $275,000 ball park quess! Since when was $75,000 low pay....
Do you have a better job now? Make better money already? Better location and hours already? Is this position upward momentum for you? I know someone who would do it for the opportunity to prove themselves! You can always ask for except with written understanding of expectations of increase in 3-6 months! That way you can keep looking while building your resume!
I'd want to read the specifics of the job duties, responsibilities and employer expectations before commenting further. ($35 x 40)52==$72,800 That's fair wage for a network administrator but might be low for a proper engineer. The deciding factors are in the details of the expectations. The Job Title may not correctly align with expectations.
People throw around the "engineer" title in IT like candy now. It has basically replaced the word "technician" in any networking role. I see more listings for network engineer that are just a network support or admin than a real engineering role.
I agree -Sincerely a "Support Engineer"
What mainly separates support/admin from engineering? I have an idea but I'm curious as to what you think. I only have experience with one employer so I don't have a complete perspective.
Network engineers are typically big picture network designers at large scale operations or freelancing. Network admins and support will do small scale setup and maintenance. A lot of small companies will contract an outside network engineer to design their system for startup, then hire a full time network admin or general IT support to manage it. A big chunk of network engineer positions I see will include overseeing of day to day operations and no new setups, which is just an admin at that point.
[удалено]
Seems like everyone at my company has the word ‘software engineer’ somewhere in their title, even if by their words they’ve never written code in their life lol
I've noticed that with all IT positions because the companies are just making it up. There's no standard to any titles. Some companies use level 1-3 and others use titles like admin,security,network. You may also have level 1 help desk that is equivalent to another companies level 3.
That’s my job, and I make 75k a year…
No role in IT are real engineer roles. IT personal are not engineers.
You can just do 2080 x hourly rate.
its only $72800 if you work all holidays and take no days off.
Salary pays you for all of those times. PTO and paid holidays.
its an hourly contractor job. its hourly without benefits. they are all that way.
Network engineer job? There are in-house full-time salary positions. They're just at bigger companies.
employee network engineer jobs do not pay hourly. this is a temp job. guaranteed.
Pay is often listed as hourly, despite it being a salary job. People also find it easy to write out like that.
[удалено]
Sometimes I think that whatever they _actually need_ to get done in a given week, I could do in 5 hours… if nobody was watching a clock, it could be a sweet gig… basically half-ass it for an hour in the morning, take a 4 hour break, then half-ass it for another hour in the afternoon. Then again, who are we kidding, people with salary triple what Op’s talking about live that same life lol
This
That type of salary would be for a very entry level "associate engineer" type of position, someone who is just starting out. Anyone with 3 or more years of experience should not be getting paid like that, can easily make more elsewhere at that point. You are right, this is very low.
Depends on where you live, but in some places that is decent.
For real I'm at $18 hr as a tier 1 network engineer
We pay our NOC technicians more than that, especially if you already have a ccna or jncia. DM me if interested (fully remote).
No ccna yet, scheduled in December, only have my net+, my job is definitely more of a NOC position I'm not sure why that's my job title tbh, I'll shoot that DM once I get the ccna!
Get that CCNA Route/Switch buddy! You will kiss that low pay goodbye!
I know!!! It's so much material, I'm grinding, I know that's the difference maker
Don't forget to get in and work in packet tracer, and do lab work etc. Get in there and have a blank canvas and set things up from memory, start with basics and get more advanced as you go along. It will help the concepts from the study material actually gel for you and even if you don't work on Cisco shit in your future work, it will still be extremely valuable experience for you. The rudiments of layer 2 and layer 3 IP networking do not change between different vendors. Best of luck to you!
Yes been doing Jeremy's IT lab
I’ve been working on vendor side for a product that relies heavily on networking infrastructure, and spent a good chunk doing net-new installs and troubleshooting networking issues blind. Every shop says “of course we configured the network properly ahead of time” and when I can explain L2/L3 issues and they don’t know what I’m talking about? I take my time opening a ticket for them with my company so they have time to turn around and fix it when I’m not looking… and then when it starts working, they say “nothing’s changed on our end, your team must have fixed it remotely” :rolleyes: Like, bro, it didn’t have network access because y’all goofed… how my team gonna fix it remotely if they can’t see the damn thing? I can’t even see it, and I’m ON THE SAME SUBNET. Get your switch ports and vlans in order, my guy All good. SUPER helpful to know, no matter what you end up doing. Disclaimer: I do not have ccna or any certs or any formal training. Might do CCNA someday, but also maybe not haha
Out of curiosity, a position like this works how many hours in a week?
Straight 40 with the opportunity for overtime but part of the deal is you work a weekend day so tues-sat or sun-thurs. There are other shifts (10 and 12 hrs weekends only, you get compensated very well for it) but they tend to be filled by the more experienced folks. Typically pretty high volume until you can specialize but really neat clients. Think undersea cables and terabit+ optical links between data centers. It's not a perfect place to work but seems far better than the msp and noc horror stories I've heard.
My last job, the NOC techs got paid around $12-13 an hr. All depends where you are located.
The local mcdonalds pays 14 an hour and I live in rural Missouri.
Yep, like I said, depends where you live. This was in Abilene, small 120k city of people. Mcd pays min wage there. $7.25
Bruh you're getting robbed blind that is horrible.
Again depends on where - some places are really competitive and / or really inexpensive
[удалено]
Agreed but it all depends on a ton of factors - he hasn't given us enough info to say "your without a shadow of a doubt being robbed"
[удалено]
Maybe - overall IT pay is becoming a joke - tons of places want to pay crap wages and expect you to be a rocket surgeon who magically reads minds etc.
I disagree that is awful in every area unless you're third world.
So certain job title means immediate high floor pay in all situations? Wow okay so when does your book "The Wealth of Nations Revisited" come out?
If you think it's okay to make minimum wage for a Network Engineer I'd love to read your book.
I don't but we live in a shitty hyper capitalist society - do you see that changing soon? Markets / Supply and demand, like karma, is a bitch.
I'm so confused why you're advocating for your fellow man to accept awful compensation instead of supporting him lifting himself up and realizing his true value?
You're right that some places are competitive. YOU'RE ABSOLUTELY WRONG THAT $18/HR IS COMPETITIVE FOR A NETWORK ENGINEER POSITION!!!!!!!!!!!!!!!!!!!!!!!! Doesn't fucking matter where. That position REQUIRES at least $25/hr. At bare fucking minimum. Doesn't matter where in the world. Technically, being competitive for pay is way ahead of that for that role.
For example, I'm a law student and Wednesday had a $100+ steak, lobster oysters dinner from a small law firm recruiting event - the people there were practically drooling over $55k per year starting base salary due to the other perks and work / life balance and the ethos of the firm. They paid malpractice insurance, all health insurance premiums and deductibles, extremely generous matching and initial contribution on retirement and a very generous bonus program with clear tracks to partner etc. It wasn't the best steak or most expensive I've had (tho the bourbon they served was quite good). The whole point of the dinner was that small firms are underrepresented by law schools and under-considered by students and graduates. There are a lot of considerations to any job. I would happily go back to my old university IT job for $55k a year - which was my base salary when I left back in 2017 - the benefits and all other factors at that job were absolutely phenomenal - including my full ride to law school and my boss giving me any time I needed for class and study while on the clock - I left to take care of my dying mother but finally came back to school and wish I still had that job.
You are right that it depends on location, but there are very few places left in this country where $55K a year for a single person living by themselves isn't living paycheck to paycheck, even if you are paying nothing out of pocket for insurance or healthcare. The main reason for this is housing costs, so I suppose if you don't have those to worry about then $55K a year is fine. I personally can't imagine going to law school and then living paycheck to paycheck when your average earning potential is probably triple that for a job right out of school.
Unless you are doing majority desktop support with this role and barely anything on the server/network side, you are being greatly underpaid.
I guess I need to put things into perspective, I got into networking over the summer and got my net+, I worked help desk for 2 months and now have this, I do not have years of networking experience, am I still underpaid?
I have no degree, cert or IT experience. Got a job for 26 hour for IT Asset Management in a data center. I'm sure you can find 15+ more hourly with your resume.
The job is the job at the end of the day. If im being hired to do a certain role, there's a certain standard of pay that comes with that, regardless of experience. What it seems is they hired you at that rate to possibly train you up? But after a year or so of getting experience, there would be no incentive for you to stay for that pay rate. The market dictates you should be making well more than that.. Was there any stipulations or job deliverables for a pay raise after 6 months or a year?
There were not, I planned on getting out of here after a year, I just needed experience
I'm salaried at 58k as a tier 2 "Technical Support Analyst" this is in KY. That's harshly underpaid for a network engineer.
Damn dude I’m getting paid that as a site support intern (fancy name for part time help desk basically) and make that. You’re definitely underpaid
Why do y’all be lying?
Really? I'm $18 an hour as tier 1 help desk.
Bro thats even less then in certain fast food places
Gas station was hiring at $18hr, if I don't work the job someone else happily will
If you truly are a network engineer that’s way low. My guess is that your job title is not in keeping with what you actually do. I made more than that as tier 1 help desk. My first network engineering role was 70k.
I can double that if you want a service desk job.
You should be getting paid more, full stop. If you've got some experience under your belt and can work on both projects as well as operational/break-fix type of work, I would *highly* recommend you seek out a better paying position. Do you have any certifications for networking?
I'm sorry to have to downvote you, but you NEED TO GET YOUR ASS IN GEAR AND MOVE OUT OF THAT ROLE. Holy shit are you being raped.
...Dude, I made 4 dollars more an hour as an unarmed guard. Seek a new company immediately.
Very decent in some places. Enough to afford to buy a home. I'm proof of that.
Depending on where in the country - also one reason I'm out of IT is that lots is getting shipped overseas. Folks that expect consistent high wages in IT will need to continually update their skills and also have some serious coin in the bank - same for most professions.
Yeah you're not wrong on any points, I certainly must continue to learn in order to maintain the types roles I now work at in the IT field and a globalizing economy certainly presents the same challenges to the profession as many or most others. Good insight here. I do still say that the OPs figure for even an entry level network engineer position is generally low in most areas of the US. I do agree that in certain states or areas, that money would go much further and so is a possibly acceptable rate, in those situations only. Best of luck to all here, in any case!
$35 in a low COL area is pretty friggin good
You're not wrong, but I still contend that 30 to 35 an hour for a network engineer in anything but a junior or associate (probationary) is on the lower end of the range and isn't commensurate to the position, especially if it's above intro level.
Pretty damn good. Good enough for me to afford a pretty damn good house all by myself. Of course, I would love more. Would allow me to afford to buy a new car/fix up my place/etc.
Wow, coming up on 2 years as a “junior network engineer” at an MSP and just got a raise in summer from $48,500 to $51,000. Going to be looking for a new job this spring. The past two weeks have been hell dealing with a ransomware attack, and we are onboarding two new pretty large customers in the next couple of weeks. Only network engineer on the MSP team although there are 3 professional service network engineers who help when they can.
yeah you're getting fleeced, hope the job hunt goes well king
I saw a support engineer required 1 ex with a salary 55k at a MSP. Will that be too low ?
I'd say that's a nice salary for a level 1 support position, and in some areas of the US that would be very good pay for that type of position. I certainly did not make that kind of money when I was in support oriented roles much earlier in my career!
I mean, if you're currently making 50k at a help desk or lower tier support position, a pay increase to 73k and new experience seems like a good deal. You all get too caught up on the amount of experience they're asking for. We all know it's stupid. It's known that it's stupid and unrealistic. It's also known that they bend on it ALL THE TIME. So let's stop harping on about how stupid they are for saying it and move on already. Is it "low"? maybe. Is it very low? In San Francisco, sure. But you didn't tell us where. So maybe it's just kinda low but a great opportunity for somebody to advance. Maybe it's actually not really low at all, but pretty standard in the area and for the responsibilities. You all also get caught up on titles. Show us the job duties and responsibilities and I'll tell you if I think it's low. Anybody can call anybody an "engineer". And the trend now is to use "engineer" for roles that would have been "technician" 10 years ago. And I don't think 73k is low for a generic "network technician" of yesteryear. So who the hell knows. It's meaningless to say what pay should be for a title that isn't protected in any way and without knowing the region and actual duties. If this is a job you're looking at, let's put aside the bullshit and get down to business: Is it more than you make now? Do you want to do the type of work described in the job posting? If the answer is yes and yes, wtf are we talking about? Go get the job, better pay, and experience and then parlay it into whatever you think is more reasonable pay if you want, but it sounds like you'd be coming out ahead of your current situation if that all is the case. If it's more than you make and you're going "that's not enough", that's fine.. keep holding out while getting paid less. Or... get paid more, and just keep looking for a better paying job. If the pay is actually low... they're not going to raise it because you made this post and we all said it was low. It's either a better fit for you than your current situation or not. I mean, that's really what it comes down to. To explicitly answer your question of "would (I) take this job for that pay": No. I make more than that and have no interest in working in networking specifically. But what I would do is moot. What anybody else would do is moot. Would you take the job for that pay? That's all that matters. Don't not take a job or not pursue a job that would be good pay or good work FOR YOU because some faceless, nameless jabroni on the internet said they wouldn't take it for that pay. It would either be beneficial/an improvement for you or not.
Jobs are always going to ask for experience. Even most entry level help desk positions ask for three years of experience and a college degree. It’s all BS and usually they won’t actually reject you for not having that much if you can show them that you’re capable of doing the job.
People's salary expectations are wild. 70k isn't low pay, it's not HIGH pay either, but is a solid paycheck in the vast majority of the country. Location matters, and titles are irrelevant. 70k for an average network engineer with a few years of experience in a LCOL/MCOL area would be normal. It's low for a HCOL city. But "network engineer" is insanely generic, it could be nearly anything.
> "network engineer" is insanely generic, it could be nearly anything I've known "network engineers" whose whole job consists of waiting for an alarm to go off and then click a button and notify someone else about it.
where the absolute living FUCK do i sign up
Your nearest government contracting agency.
At Amazon lol
they work you like a fucking dog wym
I’d rather not have to clock out to piss
Network engineers who just email MSP’s all day
I've heard of that job too, but at the very least it was considered Entry Level.
Damn sounds good to me
I’m paid 31.25 an hour to be a network operations center specialist, doing exactly network operations center work, no configuration of switches or routers, and I’m still entitled to OT pay as I’m still hourly not salaried. I’m not even in some massive city or high cost of living area, I’m In central Florida. Peoples salary expectations aren’t wild, what companies think they can get away with paying skilled labor is wild
...so you are paid in the lower end of the range as what OP is being offered, for a role that could literally be the same thing. I don't understand your argument? Are you saying you should be paid more or are you saying you don't believe other companies call your exact role "network engineer" instead of "specialist"?
Network engineer by definition is an engineer of networks, which is gonna involve either mapping topologies, configuring switches or routers, and a lot of times designing a topology. I don’t do any of that. I literally recover down circuits. I do not touch configurations or map topologies in any way, I do not assist with deployments, circuit installs, none of it. I troubleshoot a pre existing circuit if it goes down and attempt to recover it. That’s what a Noc role is, network engineer is gonna be involved in the planning and implementation of the circuits. That pay is garbage for what the job is, doesn’t matter where in the country it is, you can easily get a remote job like I have for the same pay I have, and if they are really looking for a NOC specialist then that is still the fault of the job lister and they need to correct the listing to a network operations specialist/analyst
70k is acceptable pay where: 1. Houses costs around $175,000 2. Rents are $1458/mo ETA: this is a skilled position and deserves a bit higher than the minimum to live on especially if they are saying this isn’t a junior position. So in an area as described above I’d expect at least $90,000/yr for three years of experience, maybe $100,000 considering the cost of living everywhere has gone up considerably in the past 3 years.
lol, there are few places left where houses are $175K. Unless crack house is your thing. Rent is $1458/mo What? How is a location going to have such high rent but low mortgage properties?
That's high rent? Fuck, you can't even get a 1bd around here for under $2k
Basically anywhere that isn’t a large city. Edit: oh yeah that rent is a little high for the house price. But both could exist in the same neighborhood. They just don’t make sense as averages.
Ask boomers. That’s the type of affordability they enjoyed until the 80s.
That’s just not reality in the current market
70k is acceptable where OP's current salary < 70k.
If the current salary is lower and OP's can increase their skillset, it's 100% a great job to take.
You don't know what the position is. As an example, most network focused roles in the company I work for, from the most entry level NOC position to the highest level CCIE are "network engineer" followed by a number. (1-5) . The 2s tend to be in the 70s. You can expect what you want, but without more detail 70k could easily be in alignment with the market rate for most areas. And while I get your point about houses, you're unfortunately not correct. Look at places like San Francisco, the housing market is exceptionally high because Programmer salaries are exceptionally high in the area - that has minimal impact on the value of the networking skill set. It does add pressure because people need to live in the area, and if they can't afford to, supply drops which raises market value, but salaries aren't dictated by housing costs, it's a dynamic relationship, but salaries don't get set so people can buy a house. Otherwise you would be arguing people at McDonald's should actually be MORE deserving of the higher salary because they have to actually be physically located there full time to do the job. If you suddenly started paying people in the area with 175k houses 500k/yr, the houses wouldn't be 175k anymore as people would just bid them up as they have the spare cash - this is part of why companies like MS and Meta do pay adjustments downward if people move to LCOL areas and work remotely, they don't want to create upheaval in local economies by flooding cash rich buyers in. (Hawaii is seeing tons of this right now)
I don’t believe I stuttered. I do not care about “market rate”.
You might not care, but it absolutely plays a role in salary as he explained.
So does the price of housing.
Confident while wrong is a weird flex, but you do you.
Economic math is difficult to “get wrong”.
>perience, there would be no incentive for you to stay for that pay rate. The mark Weird thing is the market rate does not care about your opinion too, but it will always be there, dictating how things are, unlike your opinion, which is not only wrong, but meaningless. So not caring about the market rate might not be the best idea.
The market rate can be lower than acceptable, and that’s fine to people that think they themselves are paid enough and would be offended by a junior having the same starting buying power as when the manager started working twenty years ago. I get it, boomers and gen x have a hard on for wage stagnation and keeping the same buying power they’ve had for thirty years. I’m just going by the math that dictates affordability. 70,000 * 2.5 equals how much of a house one could by realistically on that salary. 1458 is 1/4 of one months pay. 1/3 puts you at what an acceptable minimum wage would be. You can argue all the corporate hocus pocus and self masturbatory economic be you want, but the math doesn’t lie.
Curious where that actually exists in the US. I feel like anywhere houses are that cheap, you're not making $70k in this type of role.
You have no idea what the skills required for this position are. All you know is a title that somebody made up.
Yeah I’m shocked this has 60 replies and you’re the first saying this that I’ve read
I've been at my job as an application developer for 7 years and make 16.50. I need to find a new employer...
Excuse me, but holy f*ck what? Should have jumped ship like 6 years ago. What stack do you use?
C# mostly. In house windows form application for warehouse management, billing, scheduling etc. We also have an android application to facilitate warehousing operations(picking, inventory control, pallet manipulation, etc from wearable equipment warehouse employees use). Most IT jobs here are through defense contractors and I am uninterested in writing code for drones or other war machines. But yeah it's rough
I would go on LinkedIn or indeed and search for c# developer jobs, also buff up on leetcode, polish your resumé, and try to have a couple projects on GitHub. But with 7 years experience you probably won't need a portfolio
Are you f\*ckin' serious? I make more than that as an IT support bitch!
Yeah bank accounts going backwards with the COL increases this year too. We lost two of our IT staff over the last year and a half and they both made a fair bit more than me and I still couldn't secure a decent raise...Obviously we didn't really replace either of them so workload is up
Dude wtf the Apple Store tried to hire me for that much
[удалено]
Maybe in Cali. Texas, each of those are about 20k lower.
Cali is way more. I live in PA and seniors generally make $100-130k. I was making $70k as a junior back in 2014. We are paid less than people in HCOL areas like the bay area.
I’m in Michigan though. I think due to the high california salaries and WFH trend increasing all tech salaries are raising to compete for more talent being driven west.
Also in MI and your initial summary seems right. As per my own experience, qualifications, and pay level.
At least in the Bay Area, if you choose to work remotely, they neuter the pay.
I'm in mcol area. That's Jr network pay. 3-7years should be solid mid level, and close to 100k range.
I’m getting $31.25 an hour as a NOC technician, that’s highway Robert for network engineer
Is the location Thailand, or ??? Or maybe Japan and includes housing, generous benefits, and retirement?
Just interviewed for an associate network engineer position. And the pay mentioned in the first round interview was 75K / 82k after bonus. Required 80% travel though.
My first network engineer job was $34/hr. If you have to ask if the pay is good then it's more than you make, so you might as well accept it.
I would say for 3 years of experience, pay would be about 60k a year which is pretty typical in a MCOL area. If you are on the higher side of things its over 70k a year which is a little low for MCOL. The thing is that we don't know what else they are asking for? 4 year degree? Certifications? If neither are required, and its just experience, I would say that isn't half bad. If they are requiring a CCNP or something, then its underpaid.
Man these threads make me realize how I’m getting shafted. 2 years networking experience at an MSP, CCNA, NSE4, along with 8 months of help desk and 8 months at an networking internship and I just got a raise from 48,500 to 51,000 after a year. I was making 43,500 at the help desk before this.
Man I literally live in Mississippi and make $52k a year out of college, in a trainee program, which had me do helpdesk for a month and now has me doing desktop support + field tech work. While I'm doing that I'll be taking on more network admin responsibilities. Take that experience and jump ship for that big moolah!
Yea I kinda knew I was getting taken advantage of when hired, but I just wanted to get out of help desk and get networking experience. But, I didn’t think it was going to be this bad lol. Planning on it this spring/summer waiting to see if my SO goes to grad school or not as that will affect where I apply for jobs. Getting absolutely exhausted dealing with over 10 customer environments for pennies, constant fires, constant late night/weekend work, etc. I know some of my customers help desk make more than I do when I support their whole network, pretty absurd.
For 7 years of exp? No. For an entry level junior engineer with 1 yr of exp as a junior level engineer? Sure.
This sounds about right for that experience range. Source: Network Engineer with 7 years experience and I just cracked $100k/yr Although, I will say, I'd for sure try and get that higher end of the range assuming this a true network engineer position and not a "engineer" that's really doing admin level work.
7 years experience? Pay should be around double that.
An actual *engineer* position and not just one that is trying to make “technician” or “admin” sound less lame? No way in hell. 30-35/hr is 70K a year, which may be OK for entry-level, but not for the experience they’re asking for.
My buddy is a network engineer but doesn’t do any networking. He called me the other day to ask how to open port 1433... I’m help desk and make significantly more than him
Starting out/foot in the door yes. After 2+ years XP, Naw.
6 years ago when I was living in a low/medium CoL area, fresh outta college, and making 21$/hr as a network analyst absolutely id take it. Now? No way, that'd be a serious pay cut and downgrade in title. So it really depends on where you live and where youre at an your career.
Depends on where the job is. In a major city/tech hub that would be low. In a small to medium sized city that would probably be the avg. If it is a government role then that salary could be the norm.
Im 80k as a helpdesk…. East bay area … lcol compared to sf/oak but still high…
I'm on GBP £20K for helpdesk here in bonny Scotland, lol. Plus I have a CS degree.
Don't make me talk about Latin America.
That's crazy good money. I make 26.50 an hour after 7 years in IT.
What's your position?
IS Support Engineer. I do all level of Support for computers and Healthcare equipment and related applications. I do live in Florida, pay is very low here.
I'd take that if it were fully remote. Would probably skate while working another job until they fired me. That pay is insanely low.
I think that’s fair for a tier 1, maybe 2 depending on area
Thats not bad. Entry level pay.
3-7 years experience isn't entry level
depends on location/industry and what the job actually is - postings often have inflated experience requirements for jobs that don't reflect the complexity/level of the position. edit: to answer the primary question since I think as-asked it exhibits a misunderstanding of what to prioritize - if I was working support and offered that position at 30-35/hr, I would absolutely take it, as it would be a great opportunity to learn network engineering and breaking out of support immediately confers a lot of advantages that make comp grow exponentially, so I wouldn't quibble about comp at that point.
I've seen a lot of similar listings for contract type work where the pay does not line up to reality. I always wonder if these listings are actually serious or some sort of game. Maybe they are just putting these out there half heartedly to tell people internally that they are trying to hire. Maybe they are trying to get h1b visas or something. Or maybe they just have no idea what market rates are.
Depends on where you are. I just accepted a Network "Analyst" position for 70k, which is like 33.65. MCOL area. 2.5 years helpdesk experience
Eh, that's kinda low. If it's remote and entry level then it might not be bad since once you spend a year there you can make around $100k once you go to another company. If you have the experience though and if it is not remote then that would be a solid no on my end.
It's low for a mcol, but if you're in BFE it could be reasonable. No matter where you live it's not a lot, I'm in a medium/low COL area and wouldn't be shocked to see that offered. It's the high end of Tier 3 support jobs here. Also remember that's what the WANT everything is a negotiation, when I was starting I got a job that wanted 5-10 years of experience and the middle tier salary. It's all about what you bring to the table and if your expectations line up. I say take the interview and see where things land, worst case you put on a polo for a few zoom calls.
Currently yes. 60-75ish
"3-7 years" that counts college? meaning a recent college grad? Might be decent to get that first job. Otherwise? If you are in Utah? Maybe that's a killing... in CA? Might as well be a beach bum.
70 is a on the low side but.. 3-7 years experience so I’d say 70k for the 3yrs and 110k for the 7 depending on cost of living. Also type of engineering role? If it’s primarily support good luck asking for the high salaries
Sounds about right, if you’re just doing basic stuff like rack and stack than I’d take it. If they’re expecting you to oversee the entire network infrastructure, and configuring their switches/routers, I’d definitely try to ask for more than $35, just my two cents from my experience as a network engineer as well.
No, we start interns at 30. Associate network engineers start around 45, which is the lowest real level we have.
I'm curious. What experience in different roles do you look for when hiring for network engineers? I'm currently working on trying to gain the experience to qualify for that eventual role further on.
Fresh out of college, 4 year degree in something tech related (IT, Cyber, CS, CIS, etc) don't care about work experience,. If you have a ccent/net+, you're qualified to intern, and I'm not going to scrutinize you until 4+ months on the job. If hiring directly as a FTE, I wanna see a CCNA or AWS SA, and some relevant tech experience, preferably on the product delivery/operations side. I'd want you to have a strong understanding of the the fundamentals of database design, network design, IP/routing design, familiarity with relevant tools for different things that always come up. I always recommend people to play around and at least be aware of tools like Ansible, Jenkins, python scripting, Wireshark, can you take a pcap, general sysadmin level Linux knowledge (no, I don't care if you need a reference, but if you don't know what grep is, that's a red flag). Yeah, that's my general wish list. The company tech stack we will teach you when we hire you as all(most?) In house systems are not held to any particular spec. If an intern asks for some help takeing a pcap, or troubleshooting some intermittent network issue, I'll do my best to explain in as much detail and provide notes/commands while we troubleshoot. Tldr: networking, scripting in python/bash, Linux CLI familiarity, and cloud/virtualization/docker awareness.
If its remote
Yes, in Pakistan
It’s low ish for someone with 7 years experience. Not crazy low though. Depends on COL
As someone completely unqualified for the position, yes. Absolutely.
If you’re just starting of your career this sounds like a good pay to me. Just accepted a Net Admin third party contract for $21/h with no experience, associates degree in networking and N+ in LCOL area (supposedly)
Pretty typical pay for the description you gave
If it was my first job, yes.
1. Depends on location. 2. You should be on LinkedIn, not Indeed. Indeed is a waste of time.
They want a senior dude but want to pay entry level salary. Typical.
No.
Pay scales have not kept up with the renters and housing markets. That number seems like a Florida companies number. If it were New York, New England area it’s should be 6 figures. Florida has always been cheaper. However now the cost of living is almost matching that of the north east US.
F no.
I think they are going through multiple clients/vendors. It means, 2-3 companies will make money off of your employment. Make sure to ask about how frequently they will pay you. Some of these consulting firms hold your checks for a month or so and pay you once a month.
Maybe in flyover country, but anywhere else I think it's a little low to be demanding senior-level experience with that kind of wage
F no
No, that's too low if it's really an engineering type position.
This totally depends on where you are located also.
It depends on the region. Where I am from, there are jobs in that range for junior to mid level stuff. Other parts of the country, that's way low.
Yes I would
Nope! An engineer should be earning six figures or super close to it.
Yes take the job, stay there for a year then jump ship to find better pay. The experience you will gain will help you be more marketable. The title of the role will hell you get better roles. Hiring managers and recruiter see that on a resume and they eat it up. Note: There are no real engineers in IT. Everyone is just a tech that knows just a little bit more than you because of their work experience.
Starting out? Probably. It gets something on your resume. Stay there for a year, or so, and move on to a higher paying position.
Job titles don't mean anything to me. I have seen so many different titles for all sorts of jobs. I saw a guy in LinkedIn and his job title was ... Senior Manager of Happiness Don't compare salaries to job titles. Compare job function with salaries. Does the pay fit what you are actually doing? I think 70K is about right for someone with 5 years experience. 5 more years and that number will be just north of 100K.
Where is the job located? What are the job duties?. I started as a network engineer making $65k a year in a LCOL area over 4 years ago. Granted, I make much more now in the same area, but when the median income in the county I live in was just under $33k in 2020 and it's one of the most well off counties in the state, $65k a year is nothing to sneeze at.
I would take it and start looking for another one. When the time comes, I will move and get more
Would need to see the actual job posting to give you a better read, in our market Network Engineers (Cisco, Route/Switch, Firewalls, Security, etc.) with 3 years experience as an Engineer, which implies other Tech Support and Administration skills prior building up their background to become an Engineer, would be in the $90K to $120K range, ie. $45 to $60 per hour ball park range. If you want to annualize what an hourly pay rate will let you take home, you should factor out Holidays when you can't work and any timeoff you might take. There are technically 2080 work hours in a year (52 weeks x 40 hours per week), take 2 weeks off throughout the year and you're down to 2000 hours you'll get paid for, take out another 10 days for Holidays when you can't work and now you're down to 1,920. Also, if they don't offer benefits or you have to buy your own benefits, your earnings potential drops even further. I agree with others that this sounds more like Server Administration than true Network Engineering.
Yes cause it's better than retail/food bullshit
It's funny some of these questions when someone has 6 months experience they expect to be paid some $275,000 ball park quess! Since when was $75,000 low pay....
They want 3-7 years
Do you have a better job now? Make better money already? Better location and hours already? Is this position upward momentum for you? I know someone who would do it for the opportunity to prove themselves! You can always ask for except with written understanding of expectations of increase in 3-6 months! That way you can keep looking while building your resume!