[tneely]

I’ve effectively worked on greenfield projects my entire time at Amazon:

1. New service within Prime to handle GDPR and other compliance related matters

2. Opensource CLI tooling

3. New AWS service

4. Another new AWS service

Maybe (1) doesn’t count since it had to operate within a preexisting microservice ecosystem, but in the rest we’ve had complete control of the product from languages to servers to cloud infrastructure.

I’d wager there are always new teams in most large companies that are doing greenfield projects, you just have to look for them and be willing to join.

[OJFord]

Is a greenfield project at Amazon actually greenfield the way anyone means though?

I assume there are org-wide style guides, best practices, approved languages and libraries, strategies, norms, etc. - I don't mean to say it's a bad thing (or make any judgement) but I'd have thought there would be relatively little difference from anything brownfield; that it's really just a 'not a monorepo' technicality?

[13of40]

I'm running a greenfield project at bigcorp, and I can tell you hands down "yes it makes a difference". Sure, you have to write it in the company language, do accessibility etc., but it's far better than being tied down to the last guy's hacks and assumptions, or cross team dependencies that can't be untangled.

[rodlette]

I've ran greenfield at FAANG, and smaller companies.

Greenfield at smaller companies has more technical decisions to be made, since as you say, FAANG already has strongly preferred frameworks.

It's a shame, since making technical decisions is an important source of professional growth.