Looking for guidance in obtaining a job in Unix Administration Post: 44164

Sponsored Content

Operating Systems SCO Looking for guidance in obtaining a job in Unix Administration Post 44164 by rhfrommn on Monday 1st of December 2003 03:33:03 PM

12-01-2003

Registered User

The short version is that networking is what gets you Unix admin jobs. There are very few times I've ever heard of somebody getting a job through a want-ad, online posting, or anything like that. It is almost always either referrals or recruiters who hook you up.

Here's the longer verison:

The most important (and for somebody just trying to break into the field, hardest) step is to get to know people in the field. The first IT job I got was as a help desk analyst and I found that answering a web job posting from a contracting house. From that point on every single job I've gotten and almost every interview I've gone on has come from either a recruiter I knew or a referral from somebody that knew of the opening.

The best bet is to find one or two IT recuriters in your area and talk to them. Introduce yourself as somebody trying to break into the field and let them interview you. They will know the market in your area, and reputable ones will give you advice and help even if you don't fit any of the specific openings they have currently. They make their living knowing admins to place in jobs. Thus they are usually pretty receptive to meeting new people. And doing you favors when you're getting started can come back to help them later. I've gotten jobs from being called months after visiting with a recruiter about something completely different, just because they remembered me from that initial visit.

I know nothing of Detroit, but a couple of the national IT firms are RHI Consulting and Sapphire Technologies. I've talked to recruiters from both and found them acceptably good. That might be a place to start. My favorites have all been from smaller local shops though. If you know any Unix admins ask them what recruiters the've worked with and would recommend, anybody in the field a while will know some. That way you might get exposure to some of the local recruiters that will know the market in your city best.

rhfrommn

View Public Profile for rhfrommn

Find all posts by rhfrommn

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

freeBSD Unix Administration...

Hello there ! I am little bit confuse about freeBSD and Sun Solaris, Susue, Mandrake. Is freeBSD is same like Sun Solaris ? i mean if i will have freeBSD software, i can administrator same like i am administring Unix O.S ? I want to be Unix Administrator, so if i will install freeBSD and...

2. Solaris

Unix Administration doubts ********

Hi, Can anyone tell me the correct answers for these: 1. You have 4 instances running on the same UNIX box. How can you determine which shared memory and semaphores are associated with which instance? 2. How do you increase the OS limitation for open files (LINUX and/or Solaris)? Thanks:p

3. Shell Programming and Scripting

killing unix job after the job process completes

Hi, Thanks in advance. i need to kill a unix background running job after that job process completes. i can kill a job by giving the following unix command kill -9 processid how to kill the job after the current process run gets completed ? Appreciate your valuable help. ...

4. Solaris

killing a unix job after the job process gets completed

5. IP Networking

Obtaining your external IP address using a Unix Utility

Hello, this is my first post on the Unix forums. This is something that's been bothering me for a while, is there any particular UNIX/Linux application that will allow you to see you external IP address? :confused: ( The address beyond your router ) Thank you in advance, I could not find a...

6. UNIX for Dummies Questions & Answers

What are the career options in unix apart from unix system administration?

7. UNIX for Advanced & Expert Users

Unix administration commands

would like to know whether there are commands by which we can monitor these user activity 1) How many files are deleted by a user 2) How many files are FTP'ed by a user I am looking for commands in unix/Linux environment.

8. UNIX for Beginners Questions & Answers

Grep a section from an UNIX file obtaining only part of the data

Hello, I have a log file that has several sections "BEGIN JOB, End of job" like in the following example: 19/06/12 - 16:00:57 (27787398-449294): BEGIN JOB j1(27787398-449294) JOB1 19/06/12 - 16:00:57 (27787398-449294): DIGIT: 0 number of present logs : 1 19/06/12 - 16:00:57...

LEARN ABOUT OPENSOLARIS

queuedefs

queuedefs(4)							   File Formats 						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

       q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q	The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
		at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob	The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
		njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice	The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait	The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
		queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1 A sample file.

	 #
	 #
	 a.4j1n
	 b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All	other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs	queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.11							    1 Mar 1994							      queuedefs(4)