by OnlyJust » Sun Dec 14, 2014 12:08 am
Intro:
This post is long, so I've included headings for your convenience.
Background:
I left the day after completing my commitment, that's 3 years of employment. Now I'm working on a CS PhD earning exactly what my SMART stipend was (tuition + fees + healthcare also covered), but without any commitment. I've considered these topics extensively for several years. I even held a position at my SF specifically designed to facilitate communication between new employees and senior leadership, thereby effecting positive change.
My view on the problem:
I believe that the main problem relevant to SMARTs is the difference between the work environment they encounter and the one advertised by the SMART program. I'll add my working-for-the-government complaints, but really the problem is the difference between what was advertised and what was provided.
As far as I've seen, government facilities currently maintain a work environment that is absolutely incompatible with the type of employee SMART attracts. New SMARTs want to work with cutting edge technology, attack intellectually stimulating problems that have yet to be solved, participate in teams with intelligent, hardworking individuals, make a difference in the world, and increase their skills and marketability. We then discover that government employment requires dealing with out-of-date technology, working with teams of individuals who are lucky to have a job that pays over $45k/year, being a small part of a huge organization, and moving forward with projects at an extremely slow pace due to gratuitous bureaucracy and ineffective security/accountability policies. I spent the majority of my time getting approval to do the kind of work I was trained to do.
I jokingly (only partially joking) thought the solution would be for the government to hire one new person to replace every three current employees, and then double the standard salary. This increase in salary and decrease in employee numbers, combined with making performance affect your pay and making it actually possible to fire someone (*gasp*), would be a fantastic first step, in my opinion. In theory this would save money and time without sacrificing any productivity (I promise you that an employee worth $140k/year is better than three worth $70k), but of course in practice...
Anyway I initially saw this as an opportunity for me to make a difference; here was a problem that needed to be solved, an important problem, and I had some ideas about moving toward a solution. Of course I didn't actually suggest firing anyone, but I did work with senior leadership on improving morale and productivity. However, I quickly learned that change doesn't come easily, if at all, to a government facility. This was the most frustrating part. I'm happy to be presented with a challenge, but only when I can make progress toward a solution. During my talks with senior leadership I would hear time lines for changes that involved the word "years." To them this must have sounded reasonable, but I didn't want to spend that much of my life solving this particular problem. So I left.
Re: reporting lazy employees:
I want to respond to Larry's request that we report lazy employees. Of course I encountered many and never reported individuals by name. The reason was that it didn't seem fair to single one person out for doing something that nearly everyone is doing. The policies produce the laziness. You can't get fired. Period. Ever. Once you've been around for a year you have a job for life. Also, your performance has essentially zero effect on your pay. How can you expect someone to work hard in this situation?
I also don't think it's fair to report my organization because they were trying extremely hard to fix these issues and improve new-employee morale. I blame the nature of the system, not our organization or its employees.
Lawyers:
That's enough complaining about government employment. It has issues, yes, but like I said before, the problem relevant to us is that it was falsely advertised and we don't really learn what we agreed to until after signing the contract. I know absolutely nothing about law, but I bet a good lawyer could get you out of paying SMART back if you left early. But who can afford a good lawyer on a government salary?
Problem prevention:
I think requiring SMARTs to do an internship at their SF prior to signing the contract would go a long way toward solving this problem. But implement it right. It should not be optional; make sure it's required. Undergrads don't know enough about the situation to keep from making a decision they'll regret until they've been there.
Conclusion:
Thank you, Larry, for reading these posts. As I mentioned, I think false advertising is the problem. The type of students SMART attracts don't want to put up with the government work environment. Whenever I saw someone with a Master's degree in Electrical Engineering taking out the garbage, doing CBTs, or spending hours trying to figure out which signatures were needed on a justification of why we need to update to a new version of Eclipse, while someone else watched cat videos in the background, the phrase, "this is why we can't have good employees" came to mind.
I think the early internship idea (prior to contract signing) is great for new SMARTs, but it doesn't help those who are already trapped in the system. I suggest removing 1 year from every single current SMART's commitment as a show of good faith. Just to say, "we really weren't trying to trick you into signing your life over to us, and we are sorry for accidentally lying about your future." It looks like the website may have cut back on some of its promises about cutting-edge research/tech etc. That's good too.
Since starting graduate school I've worked about 55 hours/week, pulled about two all-nighters/month, been put under tremendous pressure to meet deadlines, and it's still preferable to working at my SF. I'm learning new things every day, participating in cutting-edge research, making a difference in the world, and when I need a new piece of software I can download and install it in 10 seconds rather than waiting 6 months for someone to sign a piece of paper pretending that they've evaluated it for security risks.
[b]Intro:[/b]
This post is long, so I've included headings for your convenience.
[b]Background:[/b]
I left the day after completing my commitment, that's 3 years of employment. Now I'm working on a CS PhD earning exactly what my SMART stipend was (tuition + fees + healthcare also covered), but without any commitment. I've considered these topics extensively for several years. I even held a position at my SF specifically designed to facilitate communication between new employees and senior leadership, thereby effecting positive change.
[b]My view on the problem:[/b]
I believe that the main problem relevant to SMARTs is the difference between the work environment they encounter and the one advertised by the SMART program. I'll add my working-for-the-government complaints, but really the problem is the [i]difference[/i] between what was advertised and what was provided.
As far as I've seen, government facilities currently maintain a work environment that is absolutely incompatible with the type of employee SMART attracts. New SMARTs want to work with cutting edge technology, attack intellectually stimulating problems that have yet to be solved, participate in teams with intelligent, hardworking individuals, make a difference in the world, and increase their skills and marketability. We then discover that government employment requires dealing with out-of-date technology, working with teams of individuals who are lucky to have a job that pays over $45k/year, being a small part of a huge organization, and moving forward with projects at an extremely slow pace due to gratuitous bureaucracy and ineffective security/accountability policies. I spent the majority of my time getting approval to do the kind of work I was trained to do.
I jokingly (only partially joking) thought the solution would be for the government to hire one new person to replace every three current employees, and then double the standard salary. This increase in salary and decrease in employee numbers, combined with making performance affect your pay and making it actually possible to fire someone (*gasp*), would be a fantastic first step, in my opinion. In theory this would save money and time without sacrificing any productivity (I promise you that an employee worth $140k/year is better than three worth $70k), but of course in practice...
Anyway I initially saw this as an opportunity for me to make a difference; here was a problem that needed to be solved, an important problem, and I had some ideas about moving toward a solution. Of course I didn't actually suggest firing anyone, but I did work with senior leadership on improving morale and productivity. However, I quickly learned that change doesn't come easily, if at all, to a government facility. This was the most frustrating part. I'm happy to be presented with a challenge, but only when I can make progress toward a solution. During my talks with senior leadership I would hear time lines for changes that involved the word "years." To them this must have sounded reasonable, but I didn't want to spend that much of my life solving this particular problem. So I left.
[b]Re: reporting lazy employees:[/b]
I want to respond to Larry's request that we report lazy employees. Of course I encountered many and never reported individuals by name. The reason was that it didn't seem fair to single one person out for doing something that nearly everyone is doing. The policies [i]produce[/i] the laziness. You can't get fired. Period. Ever. Once you've been around for a year you have a job for life. Also, your performance has essentially zero effect on your pay. How can you expect someone to work hard in this situation?
I also don't think it's fair to report my organization because they were trying extremely hard to fix these issues and improve new-employee morale. I blame the nature of the system, not our organization or its employees.
[b]Lawyers:[/b]
That's enough complaining about government employment. It has issues, yes, but like I said before, the problem relevant to us is that it was falsely advertised and we don't really learn what we agreed to until after signing the contract. I know absolutely nothing about law, but I bet a good lawyer could get you out of paying SMART back if you left early. But who can afford a good lawyer on a government salary?
[b]Problem prevention:[/b]
I think requiring SMARTs to do an internship at their SF prior to signing the contract would go a long way toward solving this problem. But implement it right. It should not be optional; make sure it's required. Undergrads don't know enough about the situation to keep from making a decision they'll regret until they've been there.
[b]Conclusion:[/b]
Thank you, Larry, for reading these posts. As I mentioned, I think false advertising is the problem. The type of students SMART attracts don't want to put up with the government work environment. Whenever I saw someone with a Master's degree in Electrical Engineering taking out the garbage, doing CBTs, or spending hours trying to figure out which signatures were needed on a justification of why we need to update to a new version of Eclipse, while someone else watched cat videos in the background, the phrase, "this is why we can't have good employees" came to mind.
I think the early internship idea ([i]prior[/i] to contract signing) is [i]great[/i] for new SMARTs, but it doesn't help those who are already trapped in the system. I suggest removing 1 year from every single current SMART's commitment as a show of good faith. Just to say, "we really weren't trying to trick you into signing your life over to us, and we are sorry for accidentally lying about your future." It looks like the website may have cut back on some of its promises about cutting-edge research/tech etc. That's good too.
Since starting graduate school I've worked about 55 hours/week, pulled about two all-nighters/month, been put under tremendous pressure to meet deadlines, and it's still preferable to working at my SF. I'm learning new things every day, participating in cutting-edge research, making a difference in the world, and when I need a new piece of software I can download and install it in 10 seconds rather than waiting 6 months for someone to sign a piece of paper pretending that they've evaluated it for security risks.