Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
Hi Waitnolonger
We are doing it to…moving to Seattle from St. Louis, my husband, daughter and myself. Hubby is flying out Friday and we leave next month - driving. I have a family support system out in Tacoma which we are very fortunate to have. Just know that you are going to have to make changes, it may be rough in the beginning but there is opportunity out there just be prepared for it. I wish you luck! Look me up when you get there J
Your answer is NO. The cost of living 'scares the living hell' out of us also, and we live here. Portland will not be cheaper, they just don't have sales taxes but they do have a state income tax and higher property taxes.
There is no such thing as the MCSE anymore. I mean, there is, but it's being phased out and is essentially useless. The new server cert is MCITP.
My recommendation (as someone who's been in this industry for close to a decade and a half now) is to pick a specialization and run with it. Having networking certs and server certs is all well and good if you're trying to find a small company looking for a generalist, but it's not the way to the largest paychecks - nor is it the most secure niche, as managed services have cannibalized the generalist field.
The CompTIA certs are essentially worthless, so he doesn't need to focus anymore on those. The CCNA is a good one to have. Adding a specialization to it, and then starting in with the NP exams would be a smart way to go. UNLESS he likes servers more, in which case he needs to focus more on the Microsoft certs and ignore the Cisco stuff.
Security pays the most, but it also takes the most skill. VoIP pays well, but has the unfortunate side effect of typically being a short term contractor's position, as once a VoIP network is set up and trust boundaries are established, companies rarely need a dedicated VoIP guy anymore. Wireless has some play, but you've really gotta dig for a position that requires it. Usually you'll end up working for a company that does a lot of conventions and trade shows, because they have to build up and then tear down wireless networks consistently. Or there's always the classic R&S (routing and switching). It's really all you need to get your foot in the door with most places.
The one thing to consider with regards to Seattle though, is that there are a lot of techies up here. Whatever he does, he'll have to augment his skillset with some one-offs. On the networking side, that typically means F5 certifications or SonicWALL or the like. On the server side, VMWare.
The guy above me stated he'd need a 4 year degree. That guy is dead wrong (and I find myself wondering if he really works for Google at this point, since I know for a fact Google doesn't care one lick about degrees, save for project manager roles or the like). IT is the one industry where your degree essentially means nothing. IT departments know that whatever you learn in college is only technologically relevant for about 6 years. Just about any job in tech you find will say "bachelor's degree...or equivalent experience". The latter is what they will prefer except in very rare scenarios with slow-adapting companies (PACCAR comes immediately to mind). Most hiring people don't even look at a person's education when they're hunting for an IT person.
Thanks so much for your thought out response. A couple of points from me:
The certs he was getting to this point have all been focused on working in this area, where being a "generalist" is more sought after than a specialist, especially when getting started somewhere. The move is the reason that he's considering getting straight to a specialty, because we realize that may be a better move in this situation.
As for what specialty he chooses, I think he basically just enjoys wireless the most, which is why he's leaning that direction.
Your statement about there being a lot of techies there is part of my trepidation about going there. On one hand, there's a lot more opportunity, but on the other, there is so much competition, a lot of which is very talented I'm sure, so it's a little scary. My husband is very smart, but like I said, he's still early in his career and will have a lot to prove wherever he goes. It's very intimidating to be such a small fish in such a large pond.
Also, just as a side note, he worked at his university for three years as their full-time all around IT guy while he got his degree. Since then he has worked for one year as a WAN System Analyst. This is the primary work experience he will be bringing with him when we get there. It's not much, but it's not absolutely nothing either.
Thanks so much for your thought out response. A couple of points from me:
The certs he was getting to this point have all been focused on working in this area, where being a "generalist" is more sought after than a specialist, especially when getting started somewhere. The move is the reason that he's considering getting straight to a specialty, because we realize that may be a better move in this situation.
As for what specialty he chooses, I think he basically just enjoys wireless the most, which is why he's leaning that direction.
Your statement about there being a lot of techies there is part of my trepidation about going there. On one hand, there's a lot more opportunity, but on the other, there is so much competition, a lot of which is very talented I'm sure, so it's a little scary. My husband is very smart, but like I said, he's still early in his career and will have a lot to prove wherever he goes. It's very intimidating to be such a small fish in such a large pond.
Also, just as a side note, he worked at his university for three years as their full-time all around IT guy while he got his degree. Since then he has worked for one year as a WAN System Analyst. This is the primary work experience he will be bringing with him when we get there. It's not much, but it's not absolutely nothing either.
I lived in the mid-west for several years and worked in the IT sector so I can speak to this. While you are correct that there isn't as much competition there, keep in mind several other factors:
1) In most of the mid-west, there are no where near as many opportunities as here.
2) Pay is less
3) Networking is harder
4) Not as prone to be on the cutting edge of technology
5) And lastly, because budgets are smaller, generalists are often preferred just to get the basic job done, as apposed to here where true specialists are more utilized.
To me, what it all comes down to is networking. I don't care how good you are or what your resume looks like (well, for 90% of folks at least), having a successful long-term career will typically fall on one's ability to network and become a part of the greater community.
If I were to lose my job today, I'm confident that I have at least a half-dozen leads/companies I could go to immediately and half of those would likely hire me immediately. Those executives/companies have never seen my resume, but they know me.
I've seen way too many "tech guys" struggle with the human element and then complain why they can't advance their career or get a new job when they have 5 master degrees and 15 certifications (an exaggeration, obviously). Simply put, get involved and meet people. That's what is truly needed for a successful long-term career as apposed to just finding a quick job (nothing wrong with this when you're moving 2500 miles, but certainly don't leave it at that).
Really? Because I have an @Google account, and I don't work for Google, nor have I except as a consultant. Came close once, but they wanted me to move to The Dalles, Oregon. Dealbreaker.
See, what you (and Capo) are talking about is the programming side of IT. When was the last time you had to go learn new C++ disciplines or the like? You don't, so a degree stays relevant longer. Plus that, comp. sci degrees require an absolutely absurd amount of math courses. Math courses which are completely useless on the hardware side of things, but essential to a programmer. But the OP wasn't talking about her s/o having a programming background - she was talking about him having a networking background. Which is a field that is *constantly* evolving and changing, and which requires a relentless amount of keeping up with those changes. Very little of what I learned in college is even remotely relevant today. I'd say maybe 5%. On this side, the hardware side, the degree is useless. I have one from MIT, and you know how many jobs it's gotten me? 1, my first one. Not a one since; it's all been on the strength of my experience and current certifications.
That was my point exactly. I think everyone saying "IT" while meaning drastically different things was causing confusion.
I think some confusion is coming from what one actually classifies as an "IT Job."
This is why is mentioned exactly what he does. I've done some searches on here looking for info and have just found that saying "IT" or "tech" is too broad for me to really get an idea of what's going on.
This is why is mentioned exactly what he does. I've done some searches on here looking for info and have just found that saying "IT" or "tech" is too broad for me to really get an idea of what's going on.
And you were smart to do so. Since his focus in networking, I think I'd more align myself with Xan's comments and really focus on a specialty and the top certs needed to support that specialty.
The only reason I might advise against it is if you have any longer term plans to end-up in a smaller city and/or part of a country where a generalists may be more desired.
Thanks so much for your thought out response. A couple of points from me:
The certs he was getting to this point have all been focused on working in this area, where being a "generalist" is more sought after than a specialist, especially when getting started somewhere. The move is the reason that he's considering getting straight to a specialty, because we realize that may be a better move in this situation.
As for what specialty he chooses, I think he basically just enjoys wireless the most, which is why he's leaning that direction.
Your statement about there being a lot of techies there is part of my trepidation about going there. On one hand, there's a lot more opportunity, but on the other, there is so much competition, a lot of which is very talented I'm sure, so it's a little scary. My husband is very smart, but like I said, he's still early in his career and will have a lot to prove wherever he goes. It's very intimidating to be such a small fish in such a large pond.
Also, just as a side note, he worked at his university for three years as their full-time all around IT guy while he got his degree. Since then he has worked for one year as a WAN System Analyst. This is the primary work experience he will be bringing with him when we get there. It's not much, but it's not absolutely nothing either.
There are a lot. I recently made the move late last year, and it was something I had some concern about, but it proved to be unfounded. What I uncovered was this (and this has been further backed up as I've been the one examining resumes to do the hiring of new guys): There were a lot of submitted applications for each job, but very few good candidates.
Example: Let's say there are a total of 100 Network/systems jobs available right now. It's probably closer to 200, but 100 will suffice for this. Now let's say one of those is mine, and I got 124 resumes for the position. Seems like a lot, right? First I'll take out the resumes that look like they were written by a 12 year old. That right there takes the total to about 70. Seriously. Then I'll take out the people who are obviously just wanting to leech off of unemployment and are doing their 3 job contacts per week in fields they have no experience in. I've gotten resumes from people with 0 tech background. Real estate agents, retail clerks, landscapers, and the like. You'd be shocked how many of these people there are. Let's drop the pool after this to 45. Then I'm going to purge the people who are in the right industry and have a nice resume, but lack the qualifications I absolutely need (not the ones I posted I want, the ones I simply cannot hire someone without). That'll bring the total down to 22 or 23.
So, OK, from an HR perspective, they go "great, we've got our choice of 23 different people for this job!" and that's as far as an HR monkey thinks, in my experience. However, with the advent of electronic resume submittal, one has to keep in mind that those 23 qualified candidates have also applied to the other 99 available positions that they are qualified for, which means it's still a dogfight to secure one of them, because the other 99 companies want one of them as well, and not end up with one of the 22 people who lacked the skills. Which means that 77 companies are either going to be re-posting the job or going home sad with a consolation prize. This is still very much a field with a lack of supply and a high amount of demand.
The only issue your husband will run into is the fact that he's light on proving certain skills because he lacks experience. The CCNA is lovely, no doubt. It will guarantee him a lot of interviews, but not necessarily a job. Which is a significant part of the battle right there, but he'll still have to dazzle and amaze in a technical interview. It's very hard to BS your way through one of those up here because you're going to be interviewed by a techie master, whereas in the Midwest it's probably pretty easy to do so because you're probably interviewing at a company that doesn't have a single techie in it, so they have nothing to go off of. If he got a CCNP, he could punch his own ticket. But the CCNP is a very advanced cert, and since he's just starting out, it's unlikely he would be able to pass that for a few years barring a braindump. Add another non-Cisco piece of hardware onto his resume and it'll do him a lot of good.
The only issue your husband will run into is the fact that he's light on proving certain skills because he lacks experience. The CCNA is lovely, no doubt. It will guarantee him a lot of interviews, but not necessarily a job. Which is a significant part of the battle right there, but he'll still have to dazzle and amaze in a technical interview. It's very hard to BS your way through one of those up here because you're going to be interviewed by a techie master, whereas in the Midwest it's probably pretty easy to do so because you're probably interviewing at a company that doesn't have a single techie in it, so they have nothing to go off of. If he got a CCNP, he could punch his own ticket. But the CCNP is a very advanced cert, and since he's just starting out, it's unlikely he would be able to pass that for a few years barring a braindump. Add another non-Cisco piece of hardware onto his resume and it'll do him a lot of good.
Well, getting interviews is at least half the battle, IMO, so that's good. And he's a pretty likeable guy who can talk tech with the best of them. Even things he might now actually know how to do, he knows what they are, and can probably learn how to do them faster than, well, just about anyone would be my guess. I'm obviously pretty biased though.
I will advise him about a non-Cisco cert. I don't think that's anything he was considering, so thanks for that advice. His goal is eventually some higher-level Cisco certs, but he was hoping for a few years of actual hands on experience first.
I'm from Seattle and still living here currently and I definitely think you can make it just fine up here. I read on yahoo that Seattle along with, NY & San Jose (?) were the best places to find jobs. And I completely agree. I know that ever where has been hit hard in regards to the economy, but I think Seattle was one of the luckier cities. We didn't feel the pain AS MUCH as some other places. This coming from someone who was laid off a few months ago, but is still working for the same company somehow LOL! Jobs just kept opening regardless of the lay offs so I'm still employed. And when I found out about the lay off I applied and was offered two other jobs that I skipped to stay at the company. I'm not worried at all and honestly you shouldn't be either Good luck
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.
Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
Since his focus in networking, I think I'd more align myself with Xan's comments and really focus on a specialty and the top certs needed to support that specialty.
