How did you find your current job? [closed]
I simply applied to anything that looked interesting to me. Whenever you go on an interview for a job there's one thing that you really ought to be keeping in mind; and that is that you are interviewing the company to find out if they are right for you just as much as they are interviewing you to make sure you are right for the company. It's more complicated when you are desperately seeking a job for whatever the reason - but if you have the time to be picky then browse around and go on interviews until you find what you're happy with.
EDIT: In light of further information, my initial post is a little lacking. If experience is what you need, then there is one simple and reliable solution: volunteer. Pick a charity in your area that you agree with and offer your services for free. You'll get hands on experience in no time. I speak from my own experiences. Not all non profits are poor beggars leaping at what ever crumby IT skills drop from the larger table. However, most are ready and willing to let you help out and you will frequently have much greater responsibilites given to you in much less time than if you were in a paying job with a static title. Of course, you have to figure out how to finance a few frivolities like food and housing while youre working for free. But that's what soup kitchens and your parents' basement are for. =)
And now back to the previously posted entry...
My advice might be slightly controversial. Your mileage may vary.
Ditch the Monsters, Dice, Ladders and whatever else. Hang out at local user groups for technologies that you work with and are interested in, go to vendor sponsored events that interest you (In my case, A lot of Microsoft TechNet/MSDN events and some VMWare stuff). Get to know people, talk, ask around. There's a whole shadow job market out there that isn't listed... or is listed, but just waiting for someone to slip in the backdoor. Does that mean you have to forgo a social life that is apart from geekery just so you can spend your free time at user groups and etc? Never let it be said. However, if you're just trying to get your 40 hours in (or 35, as the case may be in some countries), then there are some additional challenges beyond just finding a job. I don't suspect that with you, I'm just saying that so that it's on the record.
If you've never done any of the above before, then you're going to be going uphill against the wind. The goal is to do this before you need it. Furthermore, don't be slimy about it. Do it because you want to, because you like it, because this job is a career... not just a job. The job offers and etc. roll in as a natural consequence of your being active and productive in your field. I've never applied for a job in IT. I've been working steadily for 5 years. All in places that I like. In fact, I just got a new job a few weeks ago.
$0.02
I graduated college in 1998 with a degree in philosophy and creative writing. Graduation was on a Thursday; on Monday, I was working as a Unix systems administrator at a university down the road.
How did I get this job? Experience and networking. I worked in the college IT department as a student, and was for a time the only Unix admin they had(!) But, more important than experience was I started participating in the local sysadmin group. (In those days, it was SAGE affiliated; today's equivalent might be LOPSA affiliated instead or in addition.) I attended meetings for about six months, and even presented. When graduation neared, I started bringing my resume. I got several interviews, and if I recall correctly, several job offers from the folks at the meeting.
Three years later, a local ISP hired me. I had friends who worked there (networking, again), and they had a manager who was very impressed with the Unix book I'd written and published not long before. I only worked there about nine months before I was laid off in the dot-com crash.
From that point, I worked for five or six years as a consultant. I knew a bunch of people from my sysadmin involvement (as well as my involvement in the DC Cypherpunks), so I leaned on those connections to get a business started.
In the end, I decided that I didn't like consulting -- I loved the work, in its variety and high levels of engagement, but I hated having to sell myself over and over, and statements of work aren't much fun to write. So I got a contract position to see if I really wanted to get back into an office.
While I didn't want to work where the contract position put me, I did decide I wanted to work for someone else -- if it was the right job. So I put out feelers to friends, and a former Unix sysadmin I knew was working in Support at a small but growing company. They were hiring, and while I didn't really want to do support it seemed like a great place to be, so I interviewed and was hired.
Four years later I'm still at the same company, solving customer problems from the Engineering side of things.
So how did I get every job? Networking, networking, networking. Ability and experience are helpful, as is your ability to self-promote (these days, by blogging or such is probably the best way to get started), but in the end it's who you know and how they feel about you that matters. Cynical, maybe, but my experience.
The other side of the equation -- where you want to work, if they want you -- is a lot like dating. You have to feel it's a good fit: that you provide something they need or want, and they reciprocate by providing something you need. (Not just money, usually, but a sense of accomplishment, satisfaction, and ongoing growth.) It should "feel right" to you, something you can get comfortable with and that can grow with you. Like a relationship, you'll know when you've found the right one -- or at least the right one for now.
Job ads are only very rarely written by those who know what they should say. Even more so in any technical field. Nevertheless, if you find job ads complicated you're really going to freak out when you need to read system logs for something less than abvious.
As for how I found my job, it was by looking through the job ads. Start by filtering out any that are clearly not for you, which should result in a rather short list for anyone wanting entry level work.
Don't worry about applying for a job that may not be quite what you're after, as even the process of applying for a job and going to interviews is extremely valuable experience and will help you greatly when you find the right job.
Finding a job pretty much comes down to hammering everything on monster/dice/careerbuilder/etc. that looks appealing & then figuring out if it's really as appealing as it sounds. Also post your resume publicly on Monster: I've found jobs via recruiters calling me based on my resume.
Factors to consider when picking the company:
Size
If you're just starting out in the field, smaller is probably better (within reason: You don't want to be the only systems guy for a tech-heavy startup if you've got no experience, you'll wind up in over your head FAST).
50-100 people with an established IT staff is great: They'll be willing (and hopefully have time) to teach you new things.Type of Company
If at all possible, try to get into an ISP or Managed Services Provider. You will learn more and get to see/work with a wider variety of technologies in these environments, and they're great growth/learning experiences.
During my time at an ISP/MSP I sucked up a wealth of practical knowledge, and I passed most of it on to the junior admins we brought on as we expanded.Personality Fit
You'll get a gut feeling about the place after a personal interview: Either you'll like it, or you won't. As Dave said, if you're not comfortable with the place (and not desperate for the work) don't feel bad about politely passing on an offer (or asking for a week to consider other offers you may have waiting).