She's got a CompTia Security+ certification. That is not a trivial amount of specialist education. You certainly aren't expected to have a college degree to be an "engineer" if that's the thrust of your argument.
Tbh it sounds like other ulterior motives are clouding your judgement here. She seems like exactly the sort of engineer who would benefit from unionization and while I might need it less, I fully support her and I'm disappointed in Google for firing her.
As I've said elsewhere, these sham reasons for firing folks adjacent to union activity are opening up the company to massive liability and imo the board and shareholders should hold more people accountable.
A CompTia Security+ cert is actually pretty trivial. It's complete regurgitation, and not even of industry standard best practices, but of CompTia defined "best" practices. It's the lowest and most basic tech cert you can get. It certainly isn't evidence of any engineering discipline.
The board and shareholders will have to decide whether this action was, or was not, in their best interests. But history has shown that Wall Street would generally agree with this one. It's certainly not a "massive" liability. Should the employee prevail, years from now, in a wrongful termination suit the cost to google will be trivial compared to the employee.
That's why other companies often flagrantly intentionally ignore NLRB protections. It's a very limited civil liability with a very high burden of proof on the employee.
> It's the lowest and most basic tech cert you can get.
As opposed to... what? Do college degrees promise engineering discipline? Surely not. Many successful engineers have nothing more than a high school diploma and industry experience.
This has clearly gone into sexist territory now. She's a she, and therefore her experience and education is going to be audited by arbitrary and increasingly vague standards to make sure she's considered valueless.
> It certainly isn't evidence of any engineering discipline.
There is literally no credential that does this. It's a ridiculous standard to offer forward. Engineering discipline is a property of teams and organizations. On an individual level there is no distinct standard of it.
You are moving the goalposts outside the stadium.
> It's certainly not a "massive" liability. Should the employee prevail, years from now, in a wrongful termination suit the cost to google will be trivial compared to the employee.
I disagree. With the rash of these firings, we may start to see a collective lawsuit. Should systemic problems be found, Google is in genuine danger of both large fines (both the left and right in the US and other countries are eager to give Google a black eye for perceived wrongs) and of severe reputational damage putting it at a competitive hiring disadvantage.
> It's a very limited civil liability with a very high burden of proof on the employee.
Right up until you get enough claimants for various collective actions, I agree this is the sad case for American enforcement.
OK, I have to rebut some of this. I have no axe to grind about whether the engineer is male, female, trans, white, black, whatever. Fact is that when I wrote this I didn't know she was a female. Don't care.
How insane to claim that simple negativity toward a member of a protected group is an -ism. I'm not saying she isn't an engineer because of ANYTHING related to her sex.
She's getting raked over the coals because what she did was stupid and shows incredibly bad judgement. To imply that this is less bad, or maybe we shouldn't discuss it, or maybe we'd have a different opinion if she was not female is itself far more sexist.
I fully support non-degreed engineers. Yes, I agree there is no litmus test for "Engineer".
I'm clearly stating that a CompTIA+ is not sufficient to call someone an engineer. Regurgitating questionable facts does not make you an engineer. I didn't move the goalpost. But I can recognize something that isn't one.
She screwed up bad, because if there is ever any collective action, her case won't be in on it. She gave google an ironclad excuse to be fired. I'm not even arguing right vs. wrong but the way employment lawsuits work, she has zero chance.
> How insane to claim that simple negativity toward a member of a protected group is an -ism. I'm not saying she isn't an engineer because of ANYTHING related to her sex.
If the only way we can distinguish your actions from sexism is via your internal state, you have a problem larger than this conversation and you should expect pushback.
> I'm clearly stating that a CompTIA+ is not sufficient to call someone an engineer. Regurgitating questionable facts does not make you an engineer. I didn't move the goalpost. But I can recognize something that isn't one.
But just before this you said there isn't a clear test. So really, it's just your feelings.
> Yes, I agree there is no litmus test for "Engineer".
This is more arbitrary goal setting to gatekeep a word. The debate is not if she is somehow an amazing engineer or a mediocre engineer, a well trained engineer or a rushed training job, well paid or not. No, that's not the debate.
The debate is, "was she given an engineering position in which she had autonomy to make changes and when she made changes a union buster didn't like, she was fired in retaliation.
If her job was strictly to type things that were handed to her in a field, this might technically evade the law. But that's obviously not her job.
You're obviously eager to categorize her as a not-engineer because (despite protestations) you're obviously eager to shut down any pro-unionization messages, even legally protected ones.
> She screwed up bad, because if there is ever any collective action, her case won't be in on it. She gave google an ironclad excuse to be fired.
I don't think this is true. She acted within her job capacity. She wrote a true and (importantly) legally protected statement. It was in a system that was specifically mean to advise workers about rights, options and obligations.
And unless she was already being evaluated for poor performance, even a single infraction is an extremely rare circumstance for dismissal in modern corporate America.
I think you're missing the larger point. It's mostly the large companies and those in power that create these rules. I'm not siding with either side here, but simply saying that "the rules are the rules" is not enough if the rules themselves are wrong.
If we want to make it harder for unions to organize, then she was rightly fired. But ff she was fired for union organizing and we want to protect that activity, then she was wrongfully fired.
I don't disagree, but you're talking about right/wrong from a moral standpoint, one that many people probably agree with, but it's not an absolute.
The right and wrong I was talking about was with respect to the existing rules, policies, and ethics. And if you do believe these rules are morally wrong, then you change them from within the system.
The upside is there are multiple opportunities to do this without also getting fired. There are also opportunities to do as much union organizing as you like without getting fired. The Thanksgiving four played a very dangerous game, as did this individual, and they got the expected result.
Unfortunately, the other result is that if you want to find examples of blatantly illegal union busting, I'm sure they are out there but these are not them. This smacks of agitation and activism for it's own sake.
> you have a problem larger than this conversation and you should expect pushback
Why is that? Please give an example of what I said that is sexist or any other -ist.
> So really, it's just your feelings.
No, it's perfectly reasonable to object to points that were made that don't support the argument. I'm only stating that CompTIA+ does not provide evidence that you are an engineer because of the nature of the certification.
> You're obviously eager to categorize her as a not-engineer
I didn't categorize here as either way. Someone else did, I just object to assuming that a job title or a cert makes you one. It doesn't. I don't think it even matters to the argument at hand either.
> you're obviously eager to shut down any pro-unionization messages, even legally protected ones
I'm not. I'm neutral to whether googler's want a union or not since I don't have to work there and have no interest at all in google's future direction. I'm eager to inject some reality into some very dangerous idealism before more people think they will stand up to the man without understanding the not-so-nice realities.
It's well and good, from the safety of the narrative of her supporters to say things like "she had autonomy to make changes". But engineer or not, she doesn't have that kind of autonomy. No employee really does, including directors. And it's up to her to prove she did. For example: can she show her manager approved this specific action in writing? Who asked her to do this? It looks a lot different when google shows up to a hearing with logs, rules, job descriptions, and her manager's manager having not approved the labor message, corporate security policies, and on and on. Then she shows up with, "but I thought it was OK because I did other stuff similar before, but it didn't involve labor notices. Yes, I had no actual authorization, but I was trusted as an engineer". People need to think adversarially, not just "Oh the NLRB will magically protect me". Because it can't if they don't follow the rules to the letter, and even then only partially.
A company in google's position is just waiting for people to do what she did: combine legal organizing with breaking a verifiable rule. Something with proof, like security logs. Great! now they have plausible reason to make someone an example. Now - do you see why I think it was stoopid?
> Why is that? Please give an example of what I said that is sexist or any other -ist.
Because you are specifically supporting a narrative that declines to grant an arbitrary status to a woman even as you argue that there is no clear delineation of that status. You "know it when you see it" is a hell of a thing to say as you make a pronouncement about someone's termination from a job.
What's more, looking over the history of this thread, you've substantially changed your message depending on how forcefully people reply to you. You've gone from saying that she cannot be an engineer because she has no credentials (which you first try to claim is required, "That IS why (engineers are credentialed and regulated)." https://news.ycombinator.com/item?id=21822286); and eventually move to saying you're a fiat arbiter of: "[I] can recognize something that isn't one." (https://news.ycombinator.com/item?id=21832089)
It's crystal clear you're not having a discussion. You're trying to push a narrative. You're writing anything you think you can get away with, and trusting the thread depth cutoffs of HN to hide that part of the thread.
> No, it's perfectly reasonable to object to points that were made that don't support the argument. I'm only stating that CompTIA+ does not provide evidence that you are an engineer because of the nature of the certification.
The assertion earlier was that she was untrained. She is clearly not.
> I'm not. I'm neutral to whether googler's want a union or not since I don't have to work there and have no interest at all in google's future direction.
This isn't really the question and I don't know why you think this statement is relevant. The question is "should people be fired for talking about unionization." Clearly, you now that some Googlers are friendly to unionization in at least some aspects of the workplace. You're reading a story about one right now.
> I'm eager to inject some reality into some very dangerous idealism before more people think they will stand up to the man without understanding the not-so-nice realities.
Oh? And those not-so-nice realities seem to be that you'll cheerfully throw in with discrediting a woman.
> But engineer or not, she doesn't have that kind of autonomy. No employee really does, including directors.
No technical organization I've ever encountered has to go and get every action stamped and filed by their manager to avoid being fired. That's so far beyond the norm I'm wondering if you've ever been a manager or run your own company.
Quite the contrary, Management has to constantly document directives in writing and carefully apply messages to employees because there is substantial legal risk in just letting managers do whatever they feel like.
> and her manager's manager having not approved the labor message, corporate security policies, and on and on. Then she shows up with, "but I thought it was OK because I did other stuff similar before, but it didn't involve labor notices. Yes, I had no actual authorization, but I was trusted as an engineer". People need to think adversarially, not just "Oh the NLRB will magically protect me". Because it can't if they don't follow the rules to the letter, and even then only partially.
"Thinking adversarially" is at this point collective action. As I've said, Google is making a stronger and stronger case for all its employees that they need to consider a defensive unionization strategy.
> A company in google's position is just waiting for people to do what she did: combine legal organizing with breaking a verifiable rule
If she goes to court, they're going to have to prove there was a rule in place and that it was communicated to her. We'll see then.
> Because you are specifically supporting a narrative that declines to grant an arbitrary status to a woman
I'm supporting a narrative that declines to grant an arbitrary status to a PERSON based on a tech certification.
It is NOT sexist to say that CompTIA+ is insufficient evidence to be called an engineer. Not even CompTIA+ would say that. And I'm not pushing a narrative - you are pushing the narrative that if someone starts questioning a position, they must be sexist.
I don't think I'm changing my message - it's based on replying to the conversation. I'm not even saying she's not an engineer, just that people need to stop conflating tech certs with engineering. In many of these comments I'm still referring to her as an engineer, so now I'm not a sexist right? Good. Got it.
> technical organization I've ever encountered has to go and get every action stamped and filed by their manager to avoid being fired.
Yep, no engineer can or will get every action stamped and approved by management. They are expected to work independently. However, if you ABUSE that independence to bite the hand of your employer, you have absolutely no expectation of top cover. So if you are planning to do something dangerous like this, you better make sure you have it in writing that it was authorized. Because the burden of proof is now on you to show it was. Furthermore, if you go into a legal setting with your argument that engineers always act autonomously, you just sound like a bunch of cowboys to the bureaucrats that get to decide this.
If and when this goes to court, I agree we will see. But it won't. Of course that will be months and years from now either way.
Until then, if the goal was to inform her co-workers that it was safe to discuss union organizing without fear of reprisal, how's she doing at that?
> I don't think I'm changing my message - it's based on replying to the conversation. I'm not even saying she's not an engineer, just that people need to stop conflating tech certs with engineering. In many of these comments I'm still referring to her as an engineer, so now I'm not a sexist right? Good.
You're definitely still saying and have been saying you believe she's not an engineer.
> However, if you ABUSE that independence to bite the hand of your employer, you have absolutely no expectation of top cover.
Again, your bias shows. If your employer is treating you well, why would talking about unionization be threatening? These conversations are happening precisely because people claim to be seeing abusive parts of the system and are looking for recourse.
Is that biting the hand of your employer? You clearly think so. Would that folks like you were more active in demanding action the collective action by corporate CEOs to illegally fix wages. Sadly, folks seem content to shrug and smile and pretend that's the right of their minders.
> Furthermore, if you go into a legal setting with your argument that engineers always act autonomously, you just sound like a bunch of cowboys to the bureaucrats that get to decide this.
No, but the idea that summary dismissal is normal for a simple message not approved by management on a legally protected subject is hogwash. I think you know this, but you'd prefer it's not so.
> You're definitely still saying and have been saying you believe she's not an engineer.
I never said that, nor do I necessarily believe that. I replied to someone else in a one-liner which was to put forward a possible reason other people were questioning it.
> Again, your bias shows. If your employer is treating you well, why would talking about unionization be threatening?
Talking about unionizing is not threatening to me, or my company (which has a union), but it's pretty clearly very threatening to your company. You should be cognizant and careful about that.
> Is that biting the hand of your employer? You clearly think so.
What I think is that google and every other sufficiently large company will think so. It would be naive to think because your company has some zippy slogan like "don't be evil" (now retired) that they are somehow different.
It's interesting, btw., how you believe to know what I think based on not at all what I say. Novel way to run an argument.
> Would that folks like you were more active in demanding action the collective action by corporate CEOs to illegally fix wages. Sadly, folks seem content to shrug and smile and pretend that's the right of their minders.
There's a right and a wrong way to take action. Getting youself fired doesn't seem smart, but it could be a nice martyr move if you don't need the income.
If you are engineers, then you are not just wage slaves. You are independent people and can take - or leave - your employment at will. If you don't like company X, I'd suggest it's far better to simply leave.
Your problem is a bad employer, so you add a union, now you have two problems: a still bad employer and a union full of politicians.
So, I've enjoyed your interesting thought processes, and I leave you with this advice:
- read, carefully, the rights granted by the NLRB. Stick strictly and safely within them.
- for example, do you notice that it gives you the right to talk and distribute literature outside working areas (such as breakrooms or parking lots)? Do you notice how modifying a browser security extension isn't on that list? Nor is doxing your co-workers?
- don't use company time or resources to do it! A) it could easily be construed as not-protected and B) obvious opsec reasons
- martyrs for the cause might energize the base but they scare off those with mortgages.
Tbh it sounds like other ulterior motives are clouding your judgement here. She seems like exactly the sort of engineer who would benefit from unionization and while I might need it less, I fully support her and I'm disappointed in Google for firing her.
As I've said elsewhere, these sham reasons for firing folks adjacent to union activity are opening up the company to massive liability and imo the board and shareholders should hold more people accountable.