Coldwell Banker
What I did
So I did work on 2 flagship sites; coldwellbanker.com and coldwellbankerhomes.com. On coldwellbanker.com (let’s just call it cb.com and the other one is cbh.com) I served as a technical lead where my main job was tacking any thorny production bottlenecks– the most common task was fixing errors in a wildly complicated CI/CD pipeline and ticketing up requests as they came in. On the CBH side my typical day involved implementing and expanding a JSON-LD schema system that helped us generate those cool little property listing cards right inside Google search or doing A/B testing software implementation/ configuration.
What stands out on this project
This was the most visited set of sites I’ve worked on, bar none. Having that many eyes on the site at any given time meant it we had to do releases with the same speed and precision as a NASCAR pit crew. Releases were late in the day with a choice set of teammates with tightly defined roles and well rehearsed sets of actions, reports, and steps as each report came in.
The other thing that stood out was the speed and volume of feedback. We could change the text on one button on an obscure page and the PM’s would get a dozen messages before the next day with surprisingly strong feelings on the change– there was something I just found interesting to see so many people cared about the small stuff within the organization and the PM’s were excellent about making sure the other devs and I didn’t get buried by all the feedback.
coldwellbanker.com stack
- Frontend: React / Next.js
- Backend: Node.js & Java Enterprise
- CMS: Custom
- Infrastructure: AWS
- Favorite Project: Running bi-weekly releases
coldwellbankerhomes.com Stack
- Frontend: Vanilla JS + jQuery
- Backend: Microsoft .NET / C#
- CMS: custom
- Infrastructure: Azure
- Favorite Project: New lead routing software