Bryan Gregory Email & Phone Number

Santa Clara, Ca, Us

My position at SnapNames involved a wide variety of tasks. As lead architect for the Aftermarket segment, I was regularly asked to envision technical solutions and innovations to secure our position as a leading website in our sector, as well as work with other stakeholders throughout the wider organization to collaborate and architect innovative new solutions. As the manager of development efforts for SnapNames.com and its ancillary processes, I was heavily involved in coordinating DevOps, QA, and Development to ensure a secure, high-quality, performant eCommerce experience for our customers, including virtually all API and webservice design and architecture.I have mentored junior Developers and DevOps while working with senior and principal software engineers to keep the group moving fluidly and productively. I have also helped evaluate partners and vendors and worked extensively and professionally with both. During my time as a Development Manager I've constantly worked with both offshore resources and internal groups on different continents, working to ensure regular communication and make teams in differing time zones an asset, not a liability.

Before joining the management team, I was a primary developer on our three-tier enterprise application dealing with procuring and selling domain names to interested buyers. I gained significant experience in many facets of the domain name industry, from the primary market as a registrar to the secondary market as a reseller, as well as integration with registry applications in a time-sensitive high-scalability manner.The development of our auction application required dealing with complex issues including extensive database/application integration, rigorous controls to ensure data and bid integrity, and construction of multiple interfaces for administration usage, customer usage, and test injection. Many of the pieces I worked on for this application were designed to allow asynchronous operation from multiple machines. I specifically developed several of these pieces to be capable of inter-process communication, failover, and additional scalability and throughput. I participated in designing our in-house Agile process before Scrum was developed, and was a primary presence in moving forward to a Scrum process later on.During this time, I also worked with an extensive .NET/SQLServer application from a partner company we integrated with.