> In any case, it is a bad idea to invest in the company you work for

I'd question this conventional wisdom, simply because you have a lot more information about the company as an employee than a random investor does, even if you are not in possession of things like financials that the SEC considers "material non-public information". Things like culture, intelligence of your coworkers, whether or not you're actually delivering on your commitments, how many feature requests and bug reports you get from your customers, mood of management, perks offered, etc. are all intangibles, but they are usually better predictors of long-term company performance than the financials that the company gives investors.

If your company is not doing well enough or is not something that you would consider investing in, you should find a different company to work for. Bad things are going to happen in your future, regardless of whether you own shares or not.

▲

raw_anon_1111 an hour ago | parent [-]

No you don’t. If you did, you would be subject to lock outs. The average rank and file employee at any BigTech company knows only a minuscule more than the general public.

Amazon for instance has over 1 million employees. You know nothing about most of your coworkers or whether other teams are delivering featured

▲

youarentrightjr an hour ago | parent [-]

> The average rank and file employee at any BigTech company knows only a minuscule more than the general public.

Huh? We're not talking about the custodial staff.

> Amazon for instance has over 1 million customers. You know nothing about most of your coworkers or whether other teams are delivering featured

This is a hilarious example; especially at Amazon, "rank and file" employees are privy to $100M+ AWS deals, they have to implement them after all.

▲

raw_anon_1111 38 minutes ago | parent [-]

I worked for AWS in Professional Services (full time blue badge employee). Part of “sales”. Even when we talked internally asking for advice from the service teams (the people who worked on the various AWS services) or even internally within ProServe outside the project team, when we spoke on Slack, we didn’t mention the customers in Slack channels outside of a need to know basis and used the acronym “IHAC” (I have a customer) when referring to the customer.

I assure you the random developer on the EC2 service team for instance knew nothing about the sales deals.

Also a “$100 million dollar sales deal” is nothingburger for AWS not enough to move the market.

Do you think someone on the Alexa team in the retail division (“CDO”) knew anything about what was going on within AWS?

▲

youarentrightjr 29 minutes ago | parent [-]

> Do you think someone on the Alexa team in the retail division (“CDO”) knew anything about what was going on within AWS?

Hmm, no?

As a solutions architect at Amazon I was very much a "rank and file" employee, and privy to large deals, so I'm not sure what you're on about. I haven't heard of Professional Services, presumably you guys had different responsibilities.

▲

raw_anon_1111 24 minutes ago | parent [-]

So you worked at AWS as an SA and never tried to sell its own internal consulting services?

https://aws.amazon.com/professional-services/

But either way, it’s monumentally a kind of weird statement to think that anyone besides “janitors” would know anything about the deals that would go through or to think a “$100 million sales deal” would move the needle especially as we see right now that AMZN is tanking because they reported they will spend more than all of their free cash flow on CAPEX for AI. You couldn’t have predicted that

▲

youarentrightjr 12 minutes ago | parent [-]

> So you worked at AWS as an SA and never tried to sale its own internal consulting services?

Not sure I understand the value proposition here, but then again Amazon is known for having redundant teams every now and again.

	▲	raw_anon_1111 8 minutes ago \| parent [-]
		SAs are not allowed to give the customer code or actually do anything. When a customer signs a contract (SOW) with ProServe, they are billable consultants who actually do implementations. Even they can’t touch production workloads and basically do everything in non production environments and teach the customer hope to do the work and move it into production