Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

state it jobs

Ranch Hand
Posts: 138
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Im asked to come for a interview for a state job. The starting salary is

is very less very less what i get now. So im confused to whether to go for it.

The reason i applied is health insurance and my current boss is a pain in the neck for me. So kinda limbo now . I appreciate your valuable opinions

Posts: 6049
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
State jobs (I assume you mean as in one of the 50 states in the US) are stereotypically known for the following characteristics:

- 40 hour work week, firm (no on works overtime except in the most rare of circumstances, e.g. the president is coming to meet with the government who wants to show off his new pet project)
- good benefits
- difficult to be fired (can get away with little work)
- can be frustrating to see co-workers do little work
- pay significantly less than industry
- plodding pace to projects
- rarely on cutting edge
- seemingly capricious budgets from year to year

Did you just should on me? You should read this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
    Bookmark Topic Watch Topic
  • New Topic