Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Think about your question, for a moment, from the interviewer's point of view.
The first thing that you will (or should...) realize is: every job requisition is different. The business needs are different. Thus, the expectations (and the standards) of "the ideal candidate" are different.
When you look at a job-requisition, try to imagine what the businessrequirement might be, that is driving the company to be searching for "someone to hire" at this time. (If you're not sure, and if you get the opportunity, by all means ask! Make that "interview question number one.")
A job interview is not at all like "an exam at school." There are no "right" answers. All you've really got is, "someone who knows that he needs to buy something." And you are a potential seller ... who, it is presumed, does not know a blessed thing about selling. Hence, the interview. The buyer knows that he must ask.
If you suppose that "the interviewer is going to ask me lots of obscure technical questions, and I'd better know the 'right' answers," then I automatically know that you either are not yet out of college, or that you have been out of college for no more than five years. (Or, that you have been working at the same "career" for ten years or more and therefore haven't got a blessed clue about how the business world actually works.)
The real question, as any salesman will know (and if not, Chester Karass will tell you ... for a price...) is: "where is this business objection coming from, and why?"
Think like a salesman. If you don't know what that means, go buy two or three good books on selling. And, go rent a DVD of the stage play, Death Of A Salesman, and watch it straight through at least three times.
No, I am not kidding...
Last edited by sundialsvcs; 01-28-2009 at 06:47 PM.
I appreciate what you're saying, but in fact people still do sometimes ask tech qns at interviews for tech jobs. They don't want to just take your word that your cv/resume is accurate, and its usually not 'complete' ie detailing every tool you've used and how deeply.
I've been in IT (Perm & contract) for 20+ years... sometimes they ask tech qns, sometimes not... Its as well to be prepared just in case. Some places even give written tests.
Note the proviso 'tech jobs' in my 1st sentence. In senior jobs they may just ask generic qns about to solve a problem/requirement. You just never know.
Ideally ask the agent (or company if direct) what the interview content is going to be like.
We beat the crap out of our interviewees with lots of technical questions and an actual lab. It's about 5 employees in the room with the interviewee. We set them down in front of a computer and have them run through some errands, answer questions, watch them google stuff if they dont know something, etc.
It's a great way to find out if a person is going to be a good match for the existing team. Not only do you get to find out what their technical strengths or weaknesses are, but you also get an idea how well their personality fits in with the rest of the group.