Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Businesses Education

What You Should Know When Taking a University Job? 384

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?"
This discussion has been archived. No new comments can be posted.

What You Should Know When Taking a University Job?

Comments Filter:
  • by saleenS281 ( 859657 ) on Thursday June 09, 2005 @05:23PM (#12773971) Homepage
    Always have a scapegoat it's the motto of universities. Always have a fallguy. Someone you can point the finger at, because realize you will be blamed for something that has absolutely NOTHING to do with you at some point.

    "The program doesn't run on windows."
    "You asked for a linux platform, it's running flawlessly on linux."
    "TOLD YOU GUYS, IT'S JOHNS FAULT IT DOESN'T WORK!"

    believe dat!
  • by codergeek42 ( 792304 ) <peter@thecodergeek.com> on Thursday June 09, 2005 @05:26PM (#12773995) Homepage Journal
    Make sure you have a written agreement about policies and what you're job is in explicit details and what they are giving you and have it signed by yourself and a Uni representative. This way if they say "oh we never said we'd do that for you", you can save your ass and whip out your contract, saying, "Yes. You did." :)

    Oh yeah and don't forget about the partying ^_^
  • Tuition (Score:5, Informative)

    by Registered Coward v2 ( 447531 ) on Thursday June 09, 2005 @05:29PM (#12774043)
    If you are or plan to attend school there, find out what the tuition practices are - some schools significantly cut tuition costs, which will more than compensate for the lower salary (especially since, if I recall correctly, the tuition break is tax free). Also ask about the ability to get in there - when I was looking at a Uni job, they basically said "we can't guarantee it, but we do know a lot of people in the school"

    A lower salary, counterbalanced by tuition and other benefits, may be reasonable trade off. Just make sure you will get the benefits before you take the job.
  • Re:Same as any job (Score:5, Informative)

    by Rei ( 128717 ) on Thursday June 09, 2005 @05:34PM (#12774094) Homepage
    If it's anything like where I work:

    1) The stress level is a lot lower than commercial work. You're not going to get mandatory overtime, people have more of a sense of humor (sometimes, myself and others will randomly add drawing onto a whiteboard in the break room during our lunches, so the next time you see it the image has evolved), and you generally don't have an axe hanging over you all the time (although, if you're paid from grants, there is more risk). True flex hours are common, dress codes are more lax, etc. The main issue that people care about is that you get the job done, and do it well, within the deadline.

    2) The administration is a huge bureaucracy. It will take forever to get travel reimbursements, requested information, and even changes in employment status. It limps along, though.

    3) Salaries are low. Benefits are high. Workplaces tend to be tolerant (race, sexuality, etc) and in general liberal (depending on your views, this could be a good or bad thing; for me, it means I can adorn my office bulletin boards with antiwar/pro-civil-liberties posters, and only get good comments about them :) ).
  • by Curate ( 783077 ) <craigbarkhouse@outlook.com> on Thursday June 09, 2005 @05:41PM (#12774176)
    I'm in pretty much the same boat you are in. After working for 8 years, I decided to go back to university to finish my Bachelor of Computer Science, which I pissed away (read: failed out of) the first time due to laziness and having too much fun. One difference this time around is that I'm more mature, and so I'm doing much better academically. The other major difference is that tuition here costs about 2.5 times as much now as 10 years ago! So I, too, am working at the university in the summers to earn enough dough to pay myself through school. I'm doing coding and research for a CS prof, and enjoying it. I don't know what you're so hesitant about. Take the job (if they'll give it to you) and have fun with it. Politics? Who cares? Every place of employ has politics. It really shouldn't be too bad for you, because a) you're not very important; and b) it's just a temporary job, not a career. As for salary, don't expect to make anywhere close to what you would in the real world, despite your qualifications. I'm making about half. If you demand too much, you might be passed over for any one of a hundred eager young students. Go into it thinking of it more like a co-op job than some kind of high-paying consulting job. This is still much better than the alternative, which is a low-paying deadend job like McD's. It's also much more interesting work, and it will look good on a resume. Stop talking about it and just do it. You really have nothing to lose. Working for a prof is not too bad. My boss is pretty easy going. He's flexible about what I do; I get to lead as much as follow. The pay is not coming out of his pocket, so he does not put too much pressure on me. Also, he's pretty busy, so I only talk to him 1-2 times per week. The rest of the time I'm doing my own thing, working at my own pace. Oh, one other advantage is that this can give you a taste of what research is like. This will help you decide if you want to go on to post-graduate studies. I know I don't; I'm itching to get back into the workforce. But this has still been a good experience. Feel free to e-mail me if you have any specific questions.
  • by theurge14 ( 820596 ) on Thursday June 09, 2005 @05:51PM (#12774269)
    This also happens when undergrad's parents show up.
  • by Anonymous Coward on Thursday June 09, 2005 @05:51PM (#12774273)
    In some states, such as Texas, university workers (and schoolteachers) do not pay Social Security; instead they pay into a state-run pension fund.

    The problem is that the Social Security Administration will dock you for the time you have worked for the state.

    If you work for a state-supported university or grade-, middle- or high- school be certain that you understand how pension is paid and whether or not Social Security benefits are affected. I know of several people who lost benefits because they were unaware of this loophole.

  • by itallushrt ( 148885 ) on Thursday June 09, 2005 @05:52PM (#12774275) Homepage
    Why are you asking a bunch of 17 years that have never held a job in their lives these questions?

    Consult current, and if possible previous employees, at the university. I'm also not referring only to people in the same or similar departments. Go talk to a ground crew guy, a student aid who might have some insight into how things work around there, etc.

    Go to the source instead of getting 100 replies on here that only tell you to build a beowulf cluster using old servers the engineering department dumped in a closet 5 years earlier.
  • job at a university (Score:2, Informative)

    by Anonymous Coward on Thursday June 09, 2005 @06:02PM (#12774379)
    As somebody who actually work for a university, here is my take.

    First, remember one important fact: the university exists for education. While I have no idea what kind of position you are really taking, if that is a support department job for teaching/research, remember your job exist so that you can offer the service for researchers/faculties/students so that their educational (or research) experience is more enhanced.
    While this seems a logical simple idea, many non-academic departments have no idea on this at my institution (and many other ones). Often, purchasing department have all the sorts of crazy rules that we must comply, and ordering sometimes takes as long as 6 months here. Worse, sometimes, the order we made somehow gets lost in the system that we have to re-do the order (2-3 months after we originally make the order). Those people prevent us from doing our research and teaching sometimes. Coming from an academic department stand point, that is completely screwed up.

    Second, don't expect much in pay. When we were interviewing candidates a few months ago for one of our staff position, the top candidate (and he was really good) didn't take the job in the end, as the pay isn't good.

    Third, for the most part, staff jobs at a university could be very flexible. Many people work less than 40 hours/week (and getting paid for 40 hours). I swear our secretary works only 25-30 hours/week (she comes in often late, leaves early, takes several breaks throughout the day, takes 1.5 hour lunch at least, etc). Of course, some of us work very long hours, too (I work 60-80 hours/week at work, plus many hours at home). However, in my case, it's not like I have a set hours I need to be in my office and around. I just work that much willingly. Also, during the summer months, some days, I would go home as early as 2 PM.

    Fourth, as far as the job goes, it could be very flexible. My job consists of many different things: I am a chemist, network administrator, engineer, programmer, mentor (to students), consultants (to my colleagues), researcher, graphic artist all at in one day. I have learned how to do a lot of things that I doubt if I would have never been able to outside. Of course, I suppose this could change a lot depending upon what exactly is your position is (It appears that in non-academic departments, there are less job flexibility).

    Fifth, in many cases, you can dress very casually in academic jobs. I don't think I ever had to wear a tie entire day at my work (although I keep a set of clothes including a tie in my office just in case when I have to). During the summer months, I often go work in shorts and sandals, and nobody question me on that. During the school year, I normally show up work wearing jeans. I don't even own a suit any more (although I have a few jackets).

    Sixth, be prepared for some (incredibly) imcompetent and lazy people. I don't mean students. I mean other staff/faculty members. It's relatively hard to get fired in a university (in many places). We have a guy in the accounting who just did not bother to process any payments to the venders for 3 months last year. This guy's primary (and only) responsibility in his job is to pay the bills to the venders, but he did none of that for 3 months last year. This actually screwed up our budget a big time last year (not surprisingly). Well, this guy still has his job in the accounting office, believe or not.

    Would I ever give up my job for anything else? I don't think so. I love my job. I worked for a company for a while, and that sucked. My current job is a dream as far as what I concern. Politics could get bad in some places sometimes, but often I can get away with steering clear away from that. If you feel a need for the freedom in your work, academic job could be the greatest thing in the world.
  • by Anonymous Coward on Thursday June 09, 2005 @06:20PM (#12774542)
    I would like to second just about everything said by the parent poster, and add some amplification. At large public universities whose faculty are unionized, without a PhD you are automatically a second-class citizen. My eldest brother was the sysadmin of a large well-funded research group, and without a PhD, he was restricted to a salary that was lowest than the lowest-paid faculty member. That was a result of the contract that the faculty had as union members --- an enforced pecking-order based on degree and years of service.

    Salary is not the only way you would be a second-class citizen at the university, but it is a very obvious way.
  • My Experiences (Score:2, Informative)

    by fwice ( 841569 ) on Thursday June 09, 2005 @06:31PM (#12774635)
    I work as an undergrad on a co-op [wikipedia.org] for a major office in my university [neu.edu]. I do a ton of research work and programming and work in a very competetive, research driven environment.

    The pay isn't the best (I had received offers for more money), but the people I work with and the opportunities I've received are outstanding.

    Expect to work closely with a professor, a post-doctorate, grad students, undergrads, and all sorts of folks... and forge good relationships with all of them. that reference from the professor, or the good word from the post-doc when he starts working for IBM (or another random large company) can go a long way.

    Look into cheaper (or even free) tuition. I know that the guy next to me gets free tuition in exchange for his work week, so he stocks up on night classes, and has gotten his masters and is working on a PhD.

    The work environment is going to be very casual -- as long as you get the job done. I am assigned 40 hours per week (on my word -- no timecard), and I can work whatever hours i want. I've worked nights, weekends, whatever, to fit my schedule best. Eventually I settled into a 7-3 shift (I like mornings) and it was embraced by all my coworkers, who took it to mean that I was very hard working :]

    Make good friends with the office accountant (or secretary, if there is none). Get her/him gifts and engage in conversations. Basically make them a buddy, because you need to make sure your paychecks come through, as well as your reimbursements and travel costs.

    My 6 month co-op term is up, but I'm going to be staying on and working for another project. The office got a new project, and was interviewing undergrads for it. They didn't like any of the candidates, so they grabbed me and interviewed me, and asked how I'd like to work for them some more. I accepted and now have another term of work with them, doing some really amazing research work. In fact, we're competing for a very large government check, and if they choose our design and buy our IP, I reap a dividend check, as an undergrad (and my chunk will be large enough to pay my tuition and buy me a house afterwards). So I've got some pretty good inspiration.

    To sum it up:

    1) make friends with everyone
    2) follow up on paperwork, especially with the accountant
    3) don't bs anyone -> there are people in the office who know much more than you and, most likely, can call out your BS by pointing to a white paper that says the exact opposite of what youre saying
    4) deadlines are going to come. ask for help from your coworkers if you need it. finish early.
    5) find a way to get cheap/free tuition. school is expensive. take nightclasses and cheat the system.

    hope that helps
    -mike
  • by dustymugs ( 666422 ) on Thursday June 09, 2005 @06:49PM (#12774825)
    I have worked at a major public university for about 5 years now and what have I learned? 1. If you're working for a public institution, pay raises are far and few in between, especially these days. They're like rumors that are about 0.1% truth. 2. Unlike a private firm of any size, a university's primary goal is academics. As such, employees -- staff and faculty -- have lots of freedom to do things as they see fit (as long as its in accordance to the institution's objectives) and most bosses are open and encourage employees to further their education (besides the fact that most places will pay for it). 3. Pay systems differ depending where you are. I get paid once a month on the first. Its a definite shock especially when you're used to biweekly infusions. I've gotten good at budgetting because of that. 4. Unlike private companies, public institutions don't run on efficiency. Hell, I don't think efficiency is in the top 5 operational priorities. As such, monetary matters can drag on. I know, it takes way too much paperwork to get anything reimbursed. If I were you, don't work for free unless its for some course project or for some research group. 5. Along the lines of academic freedom, projects really aren't planned out when they're assigned to you. Rather, most people care about the destination, not the journey. The method in getting there is up to you. Lots of freedom for you to tinker and try different routes out. I do it all the time for various projects. 6. Make sure to take advantage of the benefits that the university gives you. If you compare the health, vision, dental, and all the other insurances that the university gives versus private companies, you're almost getting everything for free. 7. Universities are much more flexible in terms of work hours and how you work. Granted, this does depend upon your boss but most are quite flexible. I know people that do 4 10 hour days so that they can do 3 day weekends and other more odd schedules. Just make sure you're getting paid and enjoy the ride. The level of stress I have from my job is several degrees lower than anything I had before.
  • by Stanistani ( 808333 ) on Thursday June 09, 2005 @06:51PM (#12774858) Homepage Journal
    >Why are you asking a bunch of 17 years that have never held a job in their lives these questions?

    ...maybe because some of us are well-traveled 50-year-olds with 35 years of experience?

    I ask a wide variety of people for feedback on most questions.
  • Things to know (Score:1, Informative)

    by Anonymous Coward on Thursday June 09, 2005 @07:00PM (#12774947)
    First, and most importantly, the hardest thing to get used to is that in a university environment the amount of experience you have means *nothing*. I mean *nothing*. If two people are going for a job in a group, and one guy has a PHD and the other guy doesn't, it ALWAYS goes to the guy with the PHD. *ALWAYS*. The guy could be out in the real world of one year, be in a completely different field (like history....seriously), but if he has a PHD, that's it. Doesn't even matter if they know what they're doing. That PHD is the only thing they pay attention to.

    Second, be prepared to deal with the biggest egos you've ever seen. You might think things were bad in corporate, but you won't believe what happens in universities. Some of these people are real bastards; just steer clear... if you end up working for one, just switch departments when you can. The bastards just won't change. The inter-department politics between professors is something to behold.

    Be prepared for people that take credit for things when they go right, but deny all responsibility when they go wrong. I know a few of 'em that would never ever admit they made a mistake or made a bad decision.

    Be prepared for a boss taking all the credit for projects during demos and things like that, and who won't even acknowledge that you did the work... this happens less often, but does still happen. When others refer to the project it's usually "XYZ's project" where XYZ is the boss, not you.

    If you ever work on an academic paper, be prepared that your boss will likely throw their own name on it, even if they haven't written a word. This seems to be a universal practice for some reason.

    Some other things:

    Salaries vary WIDELY. When I worked for a university, I was very well paid (at least I thought so). Other people weren't. A lot of this depends on who you're working for; I've worked for people that give good raises, and I've worked for people that don't.

    Vacation time is pretty good. Usually between 4 and 6 weeks; that's not counting holidays, or sick time.

    You'll have to pay for parking. So does everyone else. It sucks, but you'll have to do it.

    If you work for a academic department (as opposed to an institute), you may get a nice office, you might not. You're always the low guy on the totem pole in academic departments, so if a new faculty member shows up, and they need office space, you might lose your office and get a worse one, or you might have to share with someone.

    No matter what they say the work is going to be when they interview you, be prepared that things won't be exactly as they stated. It's usually much different.

    Take advantage of the eateries around campus; they're usually pretty good.

    Take advantage of university discounts on computers and software. Some universities have site licenses that include your computers at home.

    Just be prepared to be called "sir" by the students; you might not feel all that much older than they are, but you are, and they'll treat you that way.

    Be aware of the politics around the groups or your department, but steer clear of it if you can. You won't be able to win those battles; those other folks live for it.

    Some of that sounds bitter (and, well, it is), but a good department with good co-workers and a good boss makes for a fun job, just like corporate.

    Good luck
  • my $.02 (Score:4, Informative)

    by fool ( 8051 ) on Thursday June 09, 2005 @07:07PM (#12775007) Homepage
    i've worked at the university of texas at austin [utexas.edu] in several departments for about 8 years doing technical work, and still work for the university now. i have worked for about a year and a half in a couple of startups, and done some conslutting on the side over the past 10 years, so i am not speaking totally from within a vacuum of outside experience.

    i started out as a student worker, with very little (3 months) outside experience, but with a healthy curiosity and a few years of hacking on stuff on my own time. i have since graduated, been promoted 4 times, achieved approximately an 5-fold salary increase, and changed departments twice. i've had a net very positive experience working at the university, and recommend it to anyone who is not already on the dot-com-dollars treadmill.

    however, i think it's a lot like any other job, for the most part--if you can stand the salary, and you like your boss and co-workers and most importantly enjoy what you do, all the piddly shit like appeasing the bureaucracy and occasionally getting trumped by a PhD kind of falls by the wayside.

    since i'm basically getting paid the same thing i was as a worker at the startups i was at (minus sometimes worthless stock options and signing bonuses), i include only the pros and cons that are university specific--for instance, i've always had flex time and an extremely casual dress code (tshirts and sandals have always been allowed), both in industry and in academia. and of course, you have to evaluate your situation; i've always worked for research-heavy departments, but a job at the student union (doing the same kind of work) carries a different sort of interaction potential--not so many people who are actually into learning, more morons and bureaucrats.

    pros:
    - 40 hour work week. i love my work, but even more than that, i love having a life outside of work. i actually get *paid* for any overtime and it is almost never mandatory.

    - great job security. if they even want to fire me for any reason not related to breaking the law, they have to give me a year's notice (they have to lodge a complaint that i am told about, and let it sit for a year before i can be dismissed).

    - cool toys. we get donations of the darnedest things. i was probably the first person in my state to run linux on a pentium pro (got a prerelease box from intel to do benchmarking on. that took a researcher one day, after which he told me to do whatever i wanted with it). we have some huge clusters, and sun is constantly trying to donate interesting (if not amazing) things to us, like a cluster of thin clients and a beefy server to back them up.

    - very relaxed atmosphere; there are deadlines but there aren't many of them and they're rarely hard. nobody has ever said "your failure to deliver on time is costing us $X!"

    - some free tuition (currently a $6000/year value if you play the system for all it's worth), potentially leading to a degree if you want it to.

    - working in an environment where the value of learning is well-understood, and continued education is encouraged and to some degree funded.
    i mostly just enjoy working with smart people, and with people who are motivated to learn about solutions to their problems instead of having me solve the problems for them.

    - access to all of the resources of the university: gym, olympic swimming and diving center, libraries, libraries, libraries, museums, university-only events (mo rocca once came to speak; you needed a university ID to get in, for instance. usually concerts, plays, sporting events, etc are cheaper for university personell in addition to students). as well, the university subscribes to a lot of services (lexis nexis, encyclopaedia britannica online, OED online, online magazine/research repositories, etc) to which i automatically get access.

    - best 401k plan i've been offered. vests after a few years and gives a 2.3% * (years employed at any salary) * (highest average annua
  • by CPhelan ( 710619 ) on Thursday June 09, 2005 @07:33PM (#12775227)
    I work for a large Canadian University doing LAN admin support for 14 libraries and it works for me. I won't get rich working here but when I consider the pros and cons compared to public sector jobs couldn't think twice my decision to stay in a university environment. Some of the benefits, 4 day work week in the summer months, 3 weeks vacation a year (compared to the lousy 1 or two week vacation you might get in pub sector), not including the extra week off between xmas and new years, Knowledgeable and reliable team, Good honest managers, centralized it management, I'm even in a frikin union they have to pay me overtime if they want me to work extra. Some of the cons, yes they have committees and useless meetings there is a type of hierarchy but its no worse then anywhere else. Working University is no picnic you have still have deadlines, projects, testing, implementation phases, and people (loosers) can still piss you off. In the end I guess it helps if you work for a big university with a lot of money
  • by Anonymous Coward on Thursday June 09, 2005 @07:54PM (#12775395)
    Yes then, but today ...

    Toward the tail end of the boom Caltech reslotted their non-PhD technical staff into new paygrades for technical work. Word on the street was that they couldn't keep admins and software people from leaving to industry jobs when the paygrades were scaled to reward people for advanced degrees. I saw my bachelor's only programmer salary raise 10% at that time.

    The rest of parent's experience is mostly still true, except that benefits are eroding in academia too, and there's less security than there once was, when you're working on government money (well NASA, NSF, NIH money anyway).
  • by Breakfast Pants ( 323698 ) on Thursday June 09, 2005 @08:29PM (#12775693) Journal
    Nice pathetic generalization. Slashdot is full of university types.
  • by davidgay ( 569650 ) on Friday June 10, 2005 @12:14AM (#12777168)
    I recall an interview at Stanford when I was just starting out in my career. I'd only ever worked at MIT as research staff since graduating with my Bachelor's, and I was interviewing with a PostDoc there. He was very arrogant and said to me, "I can't tell you what you'll be making, but I can tell you what you won't be making, which is $39K."

    A confused postdoc. Postdocs have shitty salaries (approximately 2x a grad student salary), at universities at least. I'd expect staff to be paid better tham them.

    But back to the University and Politics, the other thing is that if you're not a PhD, then you probably won't get to be Principal Investigator on grant proposals, and that means you'll be constantly in the shadow of someone else no matter how good the work you do is.

    A confused poster. Principal investigator is a research position, and for various rather obvious reasons (e.g., the funding agency will expect it...), it's expected to be filled by a researcher. A PhD is a "token" that others believe you can do research, without one you'll need some other evidence that you can do that job (e.g., you're famous in the field). A bit of a catch-22 of course, but what do you expect?

  • Hated It! (Score:3, Informative)

    by Hasie ( 316698 ) on Friday June 10, 2005 @03:11AM (#12777846)
    I worked as a lecturer for 2 years and ended up hating it with a passion for a number of reasons. This is a bit of a rant, but most of the posters above are very positive, and I think it is important that the other side of university employment is raised.

    One of the posters above hit the nail on the head: Universities sell degrees. What this means is that the pressure is on to pass students no matter what. This means that students that know nothing get degrees. I heard of a case where a student went to one of the senior staff members and asked to give his degree back because he had realised that he had learnt nothing! I eventually got sick of being told to adjust the marks to pass more students. We were given "guidelines" about the average number of students that had passed in previous years. These guidelines then became the minimum required pass rate. Even the senior staff who had been presenting the same course at the same level for decades were forced to adjust marks to lower their standards. My conscience could not let me be part of a system where second year electronics students still do not know the difference between series and parallel circuits.

    Publication pressure was a major issue. Teaching chewed up most of our time, so there was very little time for anything else. Yet we still had to publish 1 publication credit per year. But there was a catch! A journal paper is only 0.75 credits. And the credit for a paper is split equally between the authors. This meant that a person studying towards a degree (anyone without a PhD) had to produce 3 journal papers per year because half of the credit went to their advisor. The senior staff loved this idea because they got lots of journal publications for an hour meeting a week. The young staff had no opportunity to progress because they always had too much work to ever produce enough publications to be promoted.

    Universities are mad about patents and intellectual property at the moment. The upshot of this was that my contract with the university said that anything I thought of in my field of specialisation belonged to the university. Sounds fair? Except that being a lecturer in the department of electrical, electronic and computer engineering meant that that was considered my SPECIALIST field. But that was still not broad enough! The dean of the faculty told me that I was also a specialist in mathematics! The upshot of this is that ANYTHING I did belonged to the university.

    And this included consulting - compulsory to establish university credibility and the main way to supplement one's salary. The university forced us to work through their company for anything we did, and that company took 20% of the turnover (not profit) of the project. The problem was that this included nothing. We still had to pay for lab time, equipment usage, lawyers to set up contracts, accountants to sort finances out, etc.. The best bit was that they collected payment from the client, and only way to get our money out of them was through the university's bureaucracy. Basically to do the compulsory consulting we ended up having to jack our prices up by 20% making us uncompetitive, and having to fork out the money to fund the project until the university decided it was time to pay us the money we had earned. It was basically a way for the university to make money for doing nothing while passing the risk to its staff.

    In the end I was glad to leave. I do more interesting work, work less hours, get credit and pay for the extra effort I put in, and do not have to deal with the bureaucracy and politics any more.
  • My experiences... (Score:2, Informative)

    by Gaxx ( 76064 ) on Friday June 10, 2005 @07:10AM (#12778513)
    OK - here's what I've experienced working in Higher Ed for 7 years now...

    There are a lot of similiarities and a few notable differences. The biggest difference comes from a general difference in direction for the organisation. HE institutions aren't profit-focused and as a result a few things happen:

    1. The dynamics of the politics is somewhat different - without profitability driving everything forward the prestige is shared out between different departments on very traditional views of their worth rather than any realistic impression of their contribution to the organisation. The main point for you here is that IT gets less prestige in HE than in most profit-chasing organisations.

    2. A lot HE places don't run projects on the people+plan+leader+timescale+resources model. They run it more along the person+er??? model. It's really worth checking how a place puts its projects together before signing up or you can end up being lost in an under-resourced project that goes on forever.

    3. Resourcing... HE isn't rich but it has access to some resources very cheaply. So - research grads to help out, books, network access, training, labs etc are all likely to be relatively readily available whilst some of the more traditional resources (money, equipment etc) may be a little more scarce.

    4. The head-honchos. Working out who you need to impress in a HE institution can be trickier than it looks. Often the people with the power are very much behind the scenes. We love our figureheads and we love, even more, for them to have no real power whatsoever ;) If you're looking to impress and move on to bigger things within the sector make sure you put some effort into working out who really holds the power (usually people like academic standards boards, research committees etc).

    Hmmm... hope the above is helpful :)
  • Interview (Score:2, Informative)

    by Rekkart ( 589508 ) on Friday June 10, 2005 @08:11AM (#12778684)
    We just interviewed for an IT job at our University and I was on the search committee. Only ONE candidate emailed us back to say thank you for taking the time to meet with them and interview them. They appreciated meeting us, etc... Guess who got the job? Most of the IT folks who interviewed had the same skill sets. It's the people skills that are lacking. One of the best things you can do is buy a book about interviewing and what to do/not do.
  • by Art Deco ( 529557 ) on Friday June 10, 2005 @01:55PM (#12781774)
    I worked for a University for 7 years. 1 year as a research assistant, 1 year as a research programmer, and 5 years as a UNIX system administrator. As UNIX admin I had from 2 to 6 student employees working for me. Sometimes my help was amazingly good and other times it wasn't so hot. Some years we were swimming in money and I could buy anything I needed but other years research grants were lean and I had to make due. One boss was a techie himself and gave me reviews that made it sound like I walked on water, my next boss didn't trust techies and gave me scathing reviews. First the good: there is lots of stuff to learn. Instead of having only one or two different platforms like most companies my department had a few of almost every UNIX box known to man. It was a support nightmare but it was fun to have so many different kinds of toys. Much of the work I did was very cutting edge/early adopter; we were doing stuff years before most businesses were. After my years working in a university I was so strong technically that future "real" jobs were a piece of cake. I did have to scale a learning curve on business and proceedure stuff though. Now the bad stuff: pay, expect to make less than half what you would elsewhere. Speaking of politics, there is an old saying, politics in acadamea are so viscious because the stakes are so low. At universities there is a lot of dead wood. Some managers measure their worth by how many people are under them so they create useless positions to fill. Little wars erupt between rival departments, rival colleges, departments and colleges, deans and their departments, etc. When I started out my attitude was that I was there to help everyone else so I never took sides in any of these little wars. This strategy worked well for the first few years but later when my position was in jeoparty I had no allies to call upon. In my case my job description included a lot of non-technical stuff. I ended up spending half of my time doing procurement, inventory and clerical stuff which was a drag. Before you accept a job be sure you know exactly what your responsibilities will be.

"If it ain't broke, don't fix it." - Bert Lantz

Working...