Slashdot Mirror

← Back to Stories (view on slashdot.org)

What You Should Know When Taking a University Job?

Posted by Cliff on from the how-different-is-it-from-the-commercial-sector dept.

FyreWyr asks: "I've been working professionally for more than 10 years, and recently returned to school to refine my skills, and potentially, to change careers. In the meantime I'm seeking income from my University in the most practical fields, i.e., my old technical career (programming, networking, etc). So, a programming job has become available, and with it, questions. While I've done my share of business consulting, I've never worked within a University pay system, and further, project interviews have not revealed a clear project scope. Wanting to accept the project, I'm now working on a basic project overview WITHOUT compensation so that I can (get it reviewed, and) kick out an appropriate time estimate and salary. Can anyone provide 'wish-I-would-have-known' issues regarding the politics, expectations, and monetary realities of working for a major department within a large University?"

3 of 384 comments (clear)

  1. It's not what you know... by lheal · · Score: 4, Interesting
    it's what people think you know. But the biggest difference between a big University and everyplace else I've worked (small business, big business, military, and government) is that at a uni no one is looking out for your paperwork. Not your boss, not the people down at payroll, not your secretary, no one. It's not that they won't help you, it's just that they don't.

    Specifically, make double extra sure that your first paycheck is going to go through. Make sure your appointment paperwork gets from your boss to the department, from the department to the College, from the College to University Payroll, and that you're "in the system" at every step.

    Be a very squeaky wheel, but keep in mind that no one likes a pushy newcomer. I've you're too squeaky, you go from "squeaky wheel" to "boy who cried wolf" (for any future encounters with the paperwork gods and goddesses).

    --
    Raise your children as if you were teaching them to raise your grandchildren, because you are.
  2. don't work so hard! by Tharkban · · Score: 5, Interesting

    If you're working for the University, forget all that real world experience. Just do what you feel like, look busy, and program something crappy right before they ask for it. That's what I did. Actually worked out suprizingly well.

    I picked a new language for every project I worked on, learning java and perl while getting paid. Not to mention I learned how to raise levels on a mud while looking productive.

    Then again, I was young, not taken seriously, and underpaid. YMMV

    --
    Tharkban (It is a signature after all)
  3. Re:Same as any job by croddy · · Score: 4, Interesting
    What?

    I work in the systems division of the general libraries of a major research university, and it's easily the most exciting and positive environment I've ever worked in. We get to work on a variety of projects, of different sizes, and based on different technologies. A lot of our developers are making a living and pursuing research interests at the same time. We regularly make open source releases, and our student employees are very skilled.

    Your descriptions of incompetent management and poor priorities, honestly, are so foreign to me that I have a hard time believing you've ever worked in such an environment.