I work on a microservice platform team at Salesforce. In addition to the technical leadership duties expected of an Architect, I actively work in code and develop for multiple projects.- Java runtime container for microservices (Spring Boot with custom extensions)- Golang runtime container for microservices- Bazel build system for the microservices monorepo- CI system for the microservices monorepo- Defensive security, including supply chain and threat modeling- Bazel IDEI am the creator/lead maintainer for Bazel Eclipse and Bazel rules_spring projects, available on GitHub. I have been a speaker at multiple Bazel conferences.

SportsLabs is building the next generation platform for sports. They work with top brands and content rights holders in college and pro sports to create real digital businesses by using their proprietary Advanced Media Platform (AMP for Sports v3.0) to serve fans on all devices. API traffic on game days reaches into the tens of millions of requests.I served as Principal Engineer on the Advanced Media Platform server team. I worked on batch ingest engines, online REST APIs, persistence layer features, and partner integrations. Technologies used included Spring, Spring Batch, Spring Data, MongoDB, and Apache Camel. We deployed to AWS, and all AMP engineers had operations responsibilities - we used Elastic Beanstalk, Route 53, CloudFront, EC2, S3, SQS and other services.

GridMachine (now Sentient) is a spin out grid computing product from the parent financial trading company. This was a great job that ended too quickly – the Boulder office was consolidated into the San Francisco headquarters in April, and I opted not to take the relocation package. During my tenure, I worked with the team to define the product roadmap and APIs, I developed a core middle tier server component with public REST APIs, built and configured the Continuous Deployment infrastructure and provisioned the production environment.Product Design Tools: apiary.io, myBalsamiq, TrelloApp Development Tech: Java, Spring, Jetty, Jackson, Spring MVC (for REST), MongoDB, JSONContinuous Deployment: Jenkins, Artifactory, cargoProduction: Ubuntu Server, Chef, Sensu (for monitoring), OSSEC (IDS), fail2ban (IPS), Apache, rsyslog, and more.Another team member built the front end using node.js and bootstrap, which consumed the REST APIs that my middle tier server provided. Production was deployed on an existing VMware infrastructure owned by the parent company.

I worked in the office of the CTO on engineering projects that involved partners, large customers, or internal product initiatives. The output of my work was often a prototype or a demo. Tasks included writing code, system design, analyzing and authoring technical requirements, providing technical information to others, and researching technologies and standards.

With the acquisition of BEA, Oracle integrated BEA's portal products into the existing Oracle portal product line. As an architect, helped define strategy and performed technical research in support of these efforts.

Served as chief architect of the new SaaS platform initiative at BEA in parallel with my role on WebLogic Portal. Designed the SaaS platform offering from the initial requirements, wrote specifications for the implementation team, and oversaw the construction of the prototype. After the completion of the Oracle acquisition of BEA, I was asked to return to my portal roots and lead the Oracle portals architecture group.

I was the manager and architect for the architecture team for WebLogic Portal. The team consisted of me and three other architects. Our primary mission was to help define the future technical direction of the WLP product. Example team successes included spearheading the HTTP Portlet Publishing, Ajax customization tools, and REST features of WLP.

During my tenure on the CCE team, I amassed a large amount of knowledge and experience with the WebLogic Portal product. I specifially developed a deep understanding of issues related to building, operating, and updating large enterprise applications in Production data centers. Customers at this time were beginning to face numerous challenges in this area with the WebLogic Portal product. I was asked to start and lead the Production Operations development team for WLP 9.2 which focused on these use cases.The major project for the Production Operations team was the Propagation Tool that appeared in WLP 9.2 (and backported to WLP 8.1.5). It is a tool that reconciles configuration differences between two environments of WLP (usually Staging and Production) and allows precise control and visibility of the dependencies between configuration artifacts. As lead, I served as architect and lead developer of this tool.

Co-developed the second version of a web MVC technology called Webflow that was introduced with WebLogic Portal 4.0. This technology was the core presentation technology for all WLP customers until WLP 8.1, when a Struts based technology (Pageflow) replaced Webflow. I subsequently volunteered for the Customer Centric Engineering team that works on enhancements and fixes for the product post-release. In this capacity I flew all over the globe to solve problems in mission critical applications for Fortune 100 customers. As the leader of this team of 10 engineers, I had wide latitude in identifying and designing features to be added to the product to correct outages in response to customer feedback. I also spoke at BEA conferences, wrote white papers, and consulted with customer architects.