> I was super excited I was actually getting an opportunity to pursue my engineering dreams. The word "engineer" was even in my job title!
He joined twitter and started sending his content to the PR team for approval:
> In fact, I was so prolific on social media that I got the attention of several industry analysts who asked how my company used social media for brand promotion and marketing. Of course, since I was in engineering, I sent these inquiries over to our PR department. ... I often tweeted about what we were doing, what the company was releasing, and what conferences I would attend. I understood the confidentiality policies at the company and never shared any confidential information. The company even gave me formal PR training so I would know what I could and couldn't say. ... After fielding several of my PR referrals, I eventually got the attention of a senior vice president at the company, let's call him Rick Dickerson. He then asked me if I could teach him how to use Twitter.
The author was clearly stepping out of their role and impacting public relations. The SVP asked them to explain what they were doing and be introduced to those the engineer was working with (in social media). Then they flagged future content and told them to stop.
The SVP was ensuring they had the information they needed to protect the company and then limit any future off-message content being produced. The SVP wanted this engineer out of the social media space and needed him stopped.
> At that moment, it became clear that the SVP didn't just want to get me away from anything social media related in the company; he wanted me out of the company entirely. He was trying to get me fired.
I'm not saying I would have done it this way, but this is what happened via the article.
His posts were being flagged by the PR team.
I suspect it's because he was discussing products without going through the PR team (because they would have told him to stop).
All my arguments are from the article itself.
> He was effectively self-grooming for the position, isn't that what you're supposed to do?
If someone from marketing came down and started force pushing code to production, would that be self-grooming? No, you'd expect a PR and some review process, which wasn't occurring here.
It seems the SVP was in company representative in charge of PR / social media? If so, he was the party responsible for the team and thus "the team"?
> The SVP backchanneled unfounded complaints to my director in order to get me in trouble.
Seems like the SVP was going through the command chain to direct his complaints / concerns to you. That's the typical way corporate structures work.
The causality you're implying (if not explying) seems inverted.
The article specifically says that they were not.
He would have received warnings that he was violating company policy. The SVP would have addressed him directly and asked him to stop tweeting about the company instead of asking him to be taught. His manager wouldn't have been confused about the complaint.
None of your arguments are from the article. You're going way out of your way to assume the engineer is in the wrong and omitting information in the article.
are you reading something I'm not?
It says other companies were asking HIM how his company used socials for PR.
> I sent these inquiries over to our PR department
He directed these companies over to their PR department for an actual answer, he didn't send his posts over to the PR department.
> After fielding several of my PR referrals, I eventually got the attention of a senior vice president (...) He then asked me if I could teach him how to use Twitter.
This SVP noticed he was basically sending them free marketing and decided it would be great to learn how to use it himself.
Nothing in your quote says he was sending his posts over to PR for approval at all.
I’m not sure where you’re drawing your conclusion from.
From a company perspective, how do you handle someone who's gained a social media following and is posting about the company and acting as a company spokesman without being approved to do so.
You would collect all the information you can, then tell the guy to knock it off or be fired. That appears to be what happened.
And a lot of companies were really feeling their way into social media at that point (and by no means were their strategies necessarily broadly agreed to internally). I've seen first hand how many companies did not have well-articulated and specific policies and individuals were sort of on their own to do the "right thing" the interpretation of which was likely to differ depending upon what exec you asked.
It's hard to say what exactly happened in this case but in the mid- to late-2000s, it would have been very easy for an enthusiastic social media user posting about company matters to run afoul of someone used to company communications happening through tightly controlled channels.
Besides, unless I misunderstood, it doesn't seem like the "knock it off" was directly communicated to the employee by the svp at any point, which a good faith manager would probably do, unless they have a severe nonconfrontatiomality issue (some managers do)
(Speaking of which, if this was AMD -- I likely traded on this guys information lol I made a boat load off employees sharing information they shouldn't have publicly)
> There was enough suspicious stuff going on (being uninvited from internal group chats) that you can't chalk it up to one-off accidental miscommunications.
We have no idea what actually happened, what we can say is that from the author's own statement(s) they continued to post on social media and stopped sending it to the PR team. To me, this reads that the author was given repeated hints / directly told to stop and wasn't listening. My guess is the training was, "hey you're probably not supposed to be posting this, review the training please".
That said, we don't know. I'm not saying this was handled well, but this definitely wasn't being "bullied" out of a job. Their job was engineering, they were pushed out of social media, at best; after not being hired for it.
You're simply saying you believe the engineer is lying and dishonest. This is possible but there's nothing compelling about your assumption unless you provide evidence that supports it. Otherwise it's just sort of a random assumption.
I mean, Yeah sure for example, I could assume that he also has anger issue problems that he's unaware about, but that's a random assumption... Why would anyone care? In short I'm saying what compelling evidence do you have to make your assumption more relevant?
You'd think if he wasn't approved to do so then they would've actually told him to knock it off and not, you know, give him PR training and put him on a social media council.
You have no idea if the perspective presented it accurate.
Sure, but it's pretty hard to skew being included in the very part of an organization that presumably influences how said organization represents itself on social media. Are you insinuating that the author is outright lying about that?
Obviously we don't know the other side of the story but you are making a massive leap from what is presented and ignoring the completely reasonable alternatives to what the SVP is reported to have done.
This flat hierarchy works at the low level. It already does almost everywhere on the border of "production workers" and "low management".
But in the middle management, the incentive is promotion and control. You start out with a flattened hierarchy, and say 20 managers vying for promotion, well, you probably won't get promoted. Then why try hard? Uhoh, now most of your managers will either:
1) leave
2) fight over / jockey over being the "senior level" of the 20 underlings
3) stop trying
4) embezzle
5) gradually conspire to "unflatten" and add more levels, gain control (solid line or dotted line) to the territory of your peers
I don't see a problem. The SVP was correct to do what they did. IMO they should have fired this guy, not just threatened them.
This was a junior engineer posting about internal company work on social media. The junior engineer knew they were supposed to reach out to the public relations team (per the article); but the engineer kept posting anyway. The public relations point team was asking the guy to stop and he was refusing until directly threatened with termination.
How would you handle this? Imagine if someone in marketing started committing code and force pushing code to production? That's effectively what this junior engineer was doing with marketing.