• Technical lead of the Commerce team, responsible for automated provisioning of Observability products and billing and usage reporting

• Subject matter expert for integrating new products into the provisioning process, which is required for any product to go GA

• Part of the design team for building a prototype of an API gateway as part of a larger effort to breakdown an oversized monolithic REST API server

• Part of the team managing the REST API server, the internal auth server, provisioning and subscription management, and a few other small support pieces

• Helped interview and hire new engineers and supported them through onboarding in their early careers

• Designed and lead implementation of a completely new provisioning service to integrate with the SFDC workflows post acquisition

• Designed and lead implementation of the provisioning portion of the early integration between products (former SignalFx and Splunk Cloud)

• Heavily involved in planning of work in an Agile framework and organizing execution

• Developed primarily for backend systems in Java

• Responsible for systems performing a supporting role between the application layer and the platform

• serving authz and customer entitlement information

• provisioning

• maintaining the REST server

• Aided in establishing Agile practices in the engineering culture

• Engineer liaison between support and engineering, picking up opaque bugs and edge cases that could not be handled by the support team

• Main duty was to attempt to resolve any questions or bugs directly; if sub-system expert involvement was necessary, my job was to work with those engineers to find a solution

• Communicated continuously with both customers and support teams on issue status

• Acted as the main point of contact between support and engineering, ensuring support cases were handled in a timely manner and minimizing interruptions to engineering time

• Developed broad knowledge of subsystems in a complex platform

• Spent time as a full-stack developer in a Java/AngularJS stack, working on customer-facing features

• Delivered high-impact functionality, most notably a feature that enables reusability of dashboards for different teams and use cases across large organizations

• Member of the global on-call rotation; for a 7 day shift several times a year, oncallers were responsible 24 hours a day for being the first responder to critical issues anywhere in the entire system