I talked a little bit about Connect here:
https://news.ycombinator.com/item?id=47241412
I worked at AWS ProServe / their internal consulting department - full time blue badge RSU earning employee - and I was one of the highest contributors to a popular at the time open source “AWS Solution” around Connect and I had my own open source projects published under AWS’s open source GitHub organization.
BTW, I would never use the “solution” now. There are a lot better ways to do it post gen AI.
The thing was, it was years before AWS introduced APIs around Connect and even longer before they have CloudFormation support. I was the first to use those APIs at scale for clients and found and reported bugs to the team while I was there.
In many cases the challenge isn’t just finding a job posting, but finding one where that specific experience is actually valued or understood by the hiring side.
It’s less about closed code and more about experience with real deployments, edge cases, and integration patterns that only appear at scale.
This shouldn't surprise me, knowledge of a code base is a competitive advantage. But there is just something depressing about it. Maybe it being closed source and you having to learn it by being burned by undocumented behavior? Please tell more