The first 1/3 of the video is this dude with whack glasses complaining about the drive to D-town. Counting the lame intro/outro, a full 1/2 of this video is complete fluff. Thanks for wasting my time/.
I'd have multiple people look at your resume. People with engineering jobs like the one you are trying to get. It can be a humbling experience (trust me, I know) and you don't have to necessarily take all their advice but it can make a huge difference.
We hired a new grad for one of the positions we filled. He is from Beijing and graduated from Indianna University. Only one of the positions was Jr level enough to do that
Um yes, you need to live here to work here, cause you have too, you know, go into the office sometimes for meetings, get hands on in the lab, and like be part of a team of people that work together to get stuff done (poor team integration is a common trait in the people we have been talking too, engineers seem to think they can be loners, or naysayers, and still do their jobs well. That isn't the case on our team.).
If the last time you programmed in a language that a dev position is hiring for was 15 years ago, you probably aren't qualified. I recommend doing some serious homework pre-interview if that's the case. If you can learn it in a few days, prove it by getting prepared before the interview. That's the best advice I can give...
Despite your negative comments I will answer you questions...
I work in a QA offshoot so our team isn't actually hiring devs right now, but the company is (and I could potentially refer people for those positions). I can speak in more detail about salary for the QA openings we have been trying to fill for over a year though...
-The team hired me two years ago. At the time, I had a bachelors degree in History, 6 years experience in QA, some of that doing a similar type of testing, and I had worked with one team member before (that's how I found out about the opening).
-The salary is in the six figure range. As it should be for a senior QA engineer in California.
-It's a large public company, so yes.
-I averaged 40 hours a week in 2011, 50 during crunch times and 35 when it's slow (like now). And I'm on/. chatting with someone who has semi-insulted me already, so obviously I have time to screw around.
Anyway, thanks for the well wishes hamster. I will offer a piece of advice. I have a cool team right now, and attitude plays a big part in the people we chose to work with. Negative people are simply not welcome (in fact, I replaced a guy that carried a lot of angst around with him, he was demoted to standard QA dept doing less interesting work). I recommend you find something that puts you in a good place mentally before trying to join an engineering organization. It takes more than hard tech skills (although these are def required) and long hours (these shouldn't be needed) to be a good engineer.
Where is he? Because we are hiring. Unless he expects to sit in his cube and eat spaghetti for 4 days in a row, not writing code. Because that seems to be a recurring theme among our candidates.
Oh sorry, and we need people that can do some statistical analysis. That has been a stickler for several candidates and almost kept me out of this job... But I did some homework before the interview (unlike the majority of people we talk too).
They aren't qualified. Many came in through recruiters, most of the resumes didn't make it to phone interviews, those that did usually didn't know the things on their resumes. 4 out of 5 applicants are foreign nationals because there are so few qualified American engineers in San Diego that are looking for work. We have been looking for people that: understand the in and outs of HTTP and general network stack, have experience doing performance testing, and have QA experience, And we are motivated, unlike most of the people we end up talking too.
I'm just saying that if you can't get hired in the tech industry in CA right now, you should probably find another career. Personally I have been recruited heavily the last 2-3 years just from a out dated linkedin page and former colleagues that are in the same position as we are, i.e. searching for decent people to do the work.
Note the title of the orig post. I'd focus on real world skills, and when you do see an opening you are interested in do the following:
-Study up on the particular technologies they use at the job you are applying for - By this I mean, do more than read a wikipedia article. Go out and actually deploy something on your home network. Really get in there and mess with it.Figure out if it is something you are truly interested in or are just doing it to get a job.
-Re-write you resume for that particular position - Have it reflect things that are related to the job description. And have SEVERAL other people look at your resume and use their input to make it good, but don't let them write it for you.
-Actually know the things that are on your resume - This is a big one, and is referenced in the parent. As a college grad you are not an expert on anything so don't claim to be. Just explain clearly what you know and your previous areas of strength (that hopefully align with the job you are applying for).
-Study more - This is kind of a cheap trick but it totally works to get into a job. Just like a series of tests at school, you need to study before each part of the interview process (see the job desc, do a phone interview, then multiple face to face interviews). Use the information that you glean from the different parts of the interview process to go out and do more research for the next round. Try to know more about the tech you will be quizzed on than the person asking the questions.
-Relax - Seriously. Don't stress too hard about the whole interview process. Think of it as a learning experience for yourself, rather than some pressure situation that you must perform in. If you are well prepared and suited ot the job, things will go smoothly. If not, there is not point in stressing out during the process.
-Don't forget that you aren't the only one being interviewed - You should have questions lined up for the people interviewing you. Ask the HR lady about time off benefits, 401k, dress code, etc. Ask the hiring manager about team dynamics, basic company financials (are they making money? investors? etc..) and management structure above them. This can be dangerous so be careful as some companies are different from others, but you should definitely go in with some question prepared.
Anyway, that's pretty much all I got. I find that being prepared, being myself, making jokes etc, and not stressing out too bad has worked well for me. I have a good engineering job at a large company now, maybe it's all luck but I kinda doubt it. Also, there are a TON of open engineering positions in CA right now. People who say they can't get a job either don't have any skills or aren't trying.
Welcome to the club. We've been trying to hire some capable network engineers in San Diego for two years... And the pay is good! Probably a hundred resumes, dozens of phone interviews, and a few face to face interviews later and we still have only filled 2 out of 3 open positions.
Heh yeah. That's why I changed my major and got a History degree. I could go to school stoned every day, do almost no work outside of sitting through lecture, and I graduated with a 3.7 GPA. As a CS major I was barely squeaking by and it was no fun. My fellow classmates were total lame asses too...
Lucky for me I have some tech skills and grew up around computers so I really didn't need the degree to get into engineering. I already had most of the skills before I graduated high school and have learned everything else on the job (probably a more efficient way of learning than in a classroom at the pace of the slowest student in the room anyway).
All that said, I think there are other things that are sinking this ship faster than lack of quality engineers. For one, the federal reserve. We are printing money so fast, there is no way the dollar will be able to hold it's value in the next 20+ years. Hard times, they are a comin'. I'm just glad I have some marketable skills that will always come in handy for a price (unlike say, a mortgage broker or sales guy). People will always need help with their computers...
Do you often experience awkward silences when you explain to people how you aren't doing something because it costs more than your monthly netflix bill? It's because they are being polite. Stop being a cheap ass.
Other than the occasional straggler, I never see people in the office more than 8 hours a day (large-ish software company in California, ~1500 employees). And that's in Engineering, where we generally work longer hours than any other department (sales people here only work 5-6 hours a day on average). This was true at my last two jobs (medium sized software companies, 200-500 employees, both in CA) as well, unless it was crunch time and then people got OT and/or bonuses to get things done but never work more than 50 hours a week. Anything else would be asinine...
Slashdot Mirror
I will never buy NFL licensed anything.
TROLL
My 1993 Honda Nighthawk 750 is doing pretty well. And still a lot of fun to ride... :)
Or maybe it happened in 2001, since the only started monitoring this in 2002 when the new satellite went online.
Indeed.
The first 1/3 of the video is this dude with whack glasses complaining about the drive to D-town. Counting the lame intro/outro, a full 1/2 of this video is complete fluff. Thanks for wasting my time /.
http://www.websense.com/content/careers.aspx
Indeed.
http://www.websense.com/content/careers.aspx
Heh. You'd be surprised how many people with CS degrees don't know what standard deviation means. I know I was after the first few interviews!
I'd have multiple people look at your resume. People with engineering jobs like the one you are trying to get. It can be a humbling experience (trust me, I know) and you don't have to necessarily take all their advice but it can make a huge difference.
We hired a new grad for one of the positions we filled. He is from Beijing and graduated from Indianna University. Only one of the positions was Jr level enough to do that
Um yes, you need to live here to work here, cause you have too, you know, go into the office sometimes for meetings, get hands on in the lab, and like be part of a team of people that work together to get stuff done (poor team integration is a common trait in the people we have been talking too, engineers seem to think they can be loners, or naysayers, and still do their jobs well. That isn't the case on our team.).
If the last time you programmed in a language that a dev position is hiring for was 15 years ago, you probably aren't qualified. I recommend doing some serious homework pre-interview if that's the case. If you can learn it in a few days, prove it by getting prepared before the interview. That's the best advice I can give...
Despite your negative comments I will answer you questions...
/. chatting with someone who has semi-insulted me already, so obviously I have time to screw around.
I work in a QA offshoot so our team isn't actually hiring devs right now, but the company is (and I could potentially refer people for those positions). I can speak in more detail about salary for the QA openings we have been trying to fill for over a year though...
-The team hired me two years ago. At the time, I had a bachelors degree in History, 6 years experience in QA, some of that doing a similar type of testing, and I had worked with one team member before (that's how I found out about the opening).
-The salary is in the six figure range. As it should be for a senior QA engineer in California.
-It's a large public company, so yes.
-I averaged 40 hours a week in 2011, 50 during crunch times and 35 when it's slow (like now). And I'm on
Anyway, thanks for the well wishes hamster. I will offer a piece of advice. I have a cool team right now, and attitude plays a big part in the people we chose to work with. Negative people are simply not welcome (in fact, I replaced a guy that carried a lot of angst around with him, he was demoted to standard QA dept doing less interesting work). I recommend you find something that puts you in a good place mentally before trying to join an engineering organization. It takes more than hard tech skills (although these are def required) and long hours (these shouldn't be needed) to be a good engineer.
Where is he? Because we are hiring. Unless he expects to sit in his cube and eat spaghetti for 4 days in a row, not writing code. Because that seems to be a recurring theme among our candidates.
Oh sorry, and we need people that can do some statistical analysis. That has been a stickler for several candidates and almost kept me out of this job... But I did some homework before the interview (unlike the majority of people we talk too).
They aren't qualified. Many came in through recruiters, most of the resumes didn't make it to phone interviews, those that did usually didn't know the things on their resumes. 4 out of 5 applicants are foreign nationals because there are so few qualified American engineers in San Diego that are looking for work. We have been looking for people that: understand the in and outs of HTTP and general network stack, have experience doing performance testing, and have QA experience, And we are motivated, unlike most of the people we end up talking too.
I'm just saying that if you can't get hired in the tech industry in CA right now, you should probably find another career. Personally I have been recruited heavily the last 2-3 years just from a out dated linkedin page and former colleagues that are in the same position as we are, i.e. searching for decent people to do the work.
Note the title of the orig post. I'd focus on real world skills, and when you do see an opening you are interested in do the following:
-Study up on the particular technologies they use at the job you are applying for - By this I mean, do more than read a wikipedia article. Go out and actually deploy something on your home network. Really get in there and mess with it.Figure out if it is something you are truly interested in or are just doing it to get a job.
-Re-write you resume for that particular position - Have it reflect things that are related to the job description. And have SEVERAL other people look at your resume and use their input to make it good, but don't let them write it for you.
-Actually know the things that are on your resume - This is a big one, and is referenced in the parent. As a college grad you are not an expert on anything so don't claim to be. Just explain clearly what you know and your previous areas of strength (that hopefully align with the job you are applying for).
-Study more - This is kind of a cheap trick but it totally works to get into a job. Just like a series of tests at school, you need to study before each part of the interview process (see the job desc, do a phone interview, then multiple face to face interviews). Use the information that you glean from the different parts of the interview process to go out and do more research for the next round. Try to know more about the tech you will be quizzed on than the person asking the questions.
-Relax - Seriously. Don't stress too hard about the whole interview process. Think of it as a learning experience for yourself, rather than some pressure situation that you must perform in. If you are well prepared and suited ot the job, things will go smoothly. If not, there is not point in stressing out during the process.
-Don't forget that you aren't the only one being interviewed - You should have questions lined up for the people interviewing you. Ask the HR lady about time off benefits, 401k, dress code, etc. Ask the hiring manager about team dynamics, basic company financials (are they making money? investors? etc..) and management structure above them. This can be dangerous so be careful as some companies are different from others, but you should definitely go in with some question prepared.
Anyway, that's pretty much all I got. I find that being prepared, being myself, making jokes etc, and not stressing out too bad has worked well for me. I have a good engineering job at a large company now, maybe it's all luck but I kinda doubt it. Also, there are a TON of open engineering positions in CA right now. People who say they can't get a job either don't have any skills or aren't trying.
Welcome to the club. We've been trying to hire some capable network engineers in San Diego for two years... And the pay is good! Probably a hundred resumes, dozens of phone interviews, and a few face to face interviews later and we still have only filled 2 out of 3 open positions.
Heh yeah. That's why I changed my major and got a History degree. I could go to school stoned every day, do almost no work outside of sitting through lecture, and I graduated with a 3.7 GPA. As a CS major I was barely squeaking by and it was no fun. My fellow classmates were total lame asses too...
Lucky for me I have some tech skills and grew up around computers so I really didn't need the degree to get into engineering. I already had most of the skills before I graduated high school and have learned everything else on the job (probably a more efficient way of learning than in a classroom at the pace of the slowest student in the room anyway).
All that said, I think there are other things that are sinking this ship faster than lack of quality engineers. For one, the federal reserve. We are printing money so fast, there is no way the dollar will be able to hold it's value in the next 20+ years. Hard times, they are a comin'. I'm just glad I have some marketable skills that will always come in handy for a price (unlike say, a mortgage broker or sales guy). People will always need help with their computers...
And detonating the bombs at the security checkpoint...
If I had tekn down the DOJ website I'd have stuff in my pants too. It'd be brown and stinky.
I said they are polite, not me... I'm a dick. ;)
Do you often experience awkward silences when you explain to people how you aren't doing something because it costs more than your monthly netflix bill? It's because they are being polite. Stop being a cheap ass.
I use my sick days for the weekend trips etc to save the vacation days for a big trip...
Dude. What are you talking about?
Other than the occasional straggler, I never see people in the office more than 8 hours a day (large-ish software company in California, ~1500 employees). And that's in Engineering, where we generally work longer hours than any other department (sales people here only work 5-6 hours a day on average). This was true at my last two jobs (medium sized software companies, 200-500 employees, both in CA) as well, unless it was crunch time and then people got OT and/or bonuses to get things done but never work more than 50 hours a week. Anything else would be asinine...