This is more or less the norm at every FAANG. New hires are trained by their managers to pee and mark their territory.
This is how you pee
1. Don't verbally discuss project ideas with peers
2. Write up a nice beefy document even if the core idea can be expressed in 2 paragraphs
3. Do some vaguely relevant data analysis etc.
4. Circulate among leadership
Doing the above only protects you from theft within your team. Even if you do all of the above your ideas are liable to be stolen, by someone from other teams. Typically, some one else will prepare a document with a very different title that for the first 2 paragraphs might look like something different. The details will be virtually identical except for some subsections where some arbitrary changes will be made. They will be very eager to not discuss the timelines of when each document was prepared.
Why do they do this? Aren't they paid enough to do the decent thing? The problem is that most FAANG hires are career climber high GPA folks who can't accept the idea that they got into FAANG by grinding on leetcode, not because of any depth in CS knowledge and understanding. Their brain is programmed to ladder climb at all costs. For the untalented hacks that end up at a FAANG, eventually stealing becomes the only option.
One more way things get stolen. Someone quickly implements the key idea in your document and plays dumb about the plagiarization. To be "fair", the project might get split into 2 parts or be completely handed over to the one who "executed".
This is how you pee
1. Don't verbally discuss project ideas with peers
2. Write up a nice beefy document even if the core idea can be expressed in 2 paragraphs
3. Do some vaguely relevant data analysis etc.
4. Circulate among leadership
Doing the above only protects you from theft within your team. Even if you do all of the above your ideas are liable to be stolen, by someone from other teams. Typically, some one else will prepare a document with a very different title that for the first 2 paragraphs might look like something different. The details will be virtually identical except for some subsections where some arbitrary changes will be made. They will be very eager to not discuss the timelines of when each document was prepared.
Why do they do this? Aren't they paid enough to do the decent thing? The problem is that most FAANG hires are career climber high GPA folks who can't accept the idea that they got into FAANG by grinding on leetcode, not because of any depth in CS knowledge and understanding. Their brain is programmed to ladder climb at all costs. For the untalented hacks that end up at a FAANG, eventually stealing becomes the only option.