Taking my first step in the Job world

I was in that situation

I have found that a good CV is the key to getting interviews.

The presentation and content are taken into consideration.

Prep on interview techniques as this is the key part of getting a job.

There are lots of sites to help you prep for this and lots of available questions ad answers.

If you are lucky you will be interviewed by a tech minded person who you can talk to regards IT type stuff. Otherwise if its a Human Resources type the interview technique and CV are all that seems to matter.

MB - Bytes Ahead.

If you want to earn a little money and have any VB coding skills give me a shout.

hmm well my instructor once said "If you think you know it all just coz u are top of the class.. wait till you start working. You would know absolutley nothing at all till taught." and boy he was right.. LOL

i knew da ins and outs of networking but when i started on a field test in my insititute, i didnt knew da slightest thing to do, i had to be coached.

Well ... here's what I would do.

[sarcasm]

Start out by being rediculously late. Come in around 9:30 or 10:00 and say "boy, traffic was hell". Sit down at your desk and pretend like you were right on time.

Get some coffee and brag about your late night of hax0ring your buddy's Dlink home firewall. Say things like "that guy's such a n00b". This process should last about an hour.

It's now lunchtime, so cook something in the microwave that smells horrible ... like fish ... and eat it at your desk. Extend your lunch break by conversing with your now very pleased co-workers. If you don't know what to say, try asking them if they're "1337". They'll be so impressed with your control of hax0r jargon, they'll be wrapped around your little finger.

It's around 2pm now and you haven't gotten anything done. Time to log in to the server. By now you should have a r00t account, so first things first: change all the passwords on the system. This way, you ensure your own job security. They can't fire you if they can't log in. Make sure you use really short dictionary words so john the ripper will be able to plow through them all with ease in the future.

Once this is complete, it's time for some real work. Go to http://www.counter-strike.net and download the latest server. Install that bad boy on the most beastly box you have there. Kill any other little processes that may bog that server down ... we wouldn't want any choke or framerate problems now would we? Processes like "httpd", "oracle", "kswapd", "bash", and "init" can really get in the way of a good LAN game.

By now it's around 3 or 3:30 in the afternoon. Time to pack up! Start opening and closing droors randomly. Shuffle paperwork on your desk while chatting with your buddies on IRC and surfing through your ssh proxy for pr0n. Re-compile a kernel in a terminal in the background and make sure you have your alt-tab combination down to a science in case your boss comes up behind you. He'll never know that the text scrolling in your terminal isn't really some magic code you're running to fix all their problems.

As soon as the boss walks off, grab your gear and jet out of there. Leave notes on your desk like "meet Jim RE: portscan @ 4:00" so that if anyone checks your desk, they'll think you're still around doing something.

Hurry home to catch the sitcoms. Pat yourself on the back for a hard day's work.

[/sarcasm]

:P

First i would like to say "Thank you very much" "I appricate how many posts this has attracted in one night. I had a paper and pen down jotting things in my journal. and this has been wonderful how much every one helped.. thnks Thread Killer for all your advice as well, and everyone who put your chunk in.

as for this this post above me, i must say.... I ll try to avoid that... but it does have a point... lol just playing! ill see you guys around thanks for all your help!!

Quote:

---

Originally posted here by thread_killer

Take a little time to get to know your network. First, ask for all documentation that was done by your predecessor. Then read it. It may help you figure out why some of the decisions have been made in the past. Check out your server rooms and wiring closets. Make sure you know where all your key pieces of equipment are and what they do. It sucks to make what you think is going to be a "minor repair" on something unimportant and find out that you just bounced the server that payroll was using to print everyone's checks. Users don't like things like that too much.

---

I couldn't agree more with that!

Knowing your network in and out is probably the most important thing for an admin. If you're lucky, the network is already well documented and you can start by studying the docs and maps. If you're unlucky there's no doc at all or it's as pitifull as a network drawn by hand on the back of a recycled piece of paper (pretty much what I had when I came in:rolleyes:!). In the latter case, start by documenting the network yourself; try to understand the rational behind choices that have been maid in the past so you don't screw yourself changing things to what seems to be the better/right way and find out it can't be done for some reason.
Besides, personally, I find documenting the network to be actually an interesting job to do.

Ammo

I can Agree with that ammo, Documentation is very important... almost as important then air.

Quote:

---

Originally posted here by ammo


If you're unlucky there's no doc at all or it's as pitifull as a network drawn by hand on the back of a recycled piece of paper (pretty much what I had when I came in:rolleyes:!).

---

He he....that's exactly what I had when I came into the job I have now. For about three months, I'd have to go to this guy who had been there forever and say "How is this put together?" He'd grab a napkin or old fax, and doodle out some of the most illegible crap you've ever seen in your life. It was pitiful.