From: clifto@indep1.UUCP (Cliff Sharp)
Newsgroups: misc.jobs.misc
Subject: Re: ATTENTION! Software Engineers!
Date: 7 Nov 92 22:05:15 GMT
Organization: as little as possible

In article <1992Nov4.115450.2022@ucbeh.san.uc.edu> smithdv@ucbeh.san.uc.edu writes:
>Questions:
>
>	1.  How is the organizational structure( layers of control )
>            in your company?  Doesn't have to be detailed. Just in
>            reference to your job.

   In the last two "jobs" I had, ULTRA_MILITARY bureaucracy.

>	2.  What do you think is the key criteria for advancement
>            at the entry level?

   None.  The last two "jobs" I had didn't hire entry-level people.
   One job I had that DID hire entry-level people had policies that varied
by individual manager.  I had one manager try to raise me to $16,000/year
while I was getting job offers from the outside at over $20,000/year.  Find
a GOOD headhunter and ask HIM what he can get you, based on your experience.

>	3.  What is the most rewarding aspect of your profession?

   Being able to create programs faster, better, and more complete than my
colleagues.

>	4.  What is the most disagreeable aspect of your profession?

   Having to put up with the bureacracy.  (Solved by becoming an independent
consultant; they don't want to pay $35-65 for paperwork.)

>	5.  What might be some restrictions of this career?

   One, if you're not damn good at what you do.  Two, if you're not ready
to deal with bureaucracy.   Three, if you're not ready to follow orders
unconditionally, whether they hurt people or not.  Four, if you're not
willing to admit that your college training simply will NOT keep you up
with the world of computer programming/systems analysis.

>	6.  What might one expect in salary at entry level?

    Depends on area.  In Chicago, $16000 to $22000 is about right.

>	7.  What are the skills and abilities required to become
>            a software engineer?

   If you can't read a National Semiconductor databook and figure out how
to program the registers of a 16550AFN, lose the idea altogether.  (It's
simple; just takes a logical mind.) Some hardware background helps, but isn't
necessary.  Think simple; things like robotics are nothing more than sending
instructions to the robotic arm to turn left 45 degrees, move down and close
the claw; the only field you're likely to find difficulty in is DSP, where
you need a LOT of math.  Most "software engineering" is nothing more than
being able to figure out a simple problem and look through the data books
to find the answers.


>Again thanks for any cooperation and if I posted this in
>the wrong area, I apologize.  Once again this applies only
>to currently, or passed, employ as a software engineer.
>And remember to send your name and the company you work for,
>and the answers to questions above, to smithdv@ucbeh.san.uc.edu    

   I'm an independent contractor, d/b/a/ Clifto Software.  I'm not exactly
prosperous in these rough financial times, but I do okay.  And I can say
honestly that I've _never_ failed to meet a client's requirements in a
short time.

-- 
+------------------------------------------------------------------------------+
|   Cliff Sharp  |      clifto@indep1.chi.il.us   OR  clifto@indep1.uucp       |
|     WA9PDM     |                 Use whichever one works                     |
+------------------------------------------------------------------------------+