I played a crucial role in the effort to move our acquired Singular Key product (now known as DaVinci) onto our PingOne/v2 platform. This included (but is not limited to) migrating from MongoDB to Cassandra, establishing a new set of libraries for NodeJS services on our platform, and spearheading quality initiatives to improve our confidence and observability. Tech stack includes NodeJS, TypeScript, React, Cassandra, Redis, Kafka, New Relic, Splunk, Docker, Kubernetes, AWS, and Jenkins.

Previously, I worked on authentication APIs for the PingOne platform, as well as our UIs. I am primarily a backend developer, although I also own our next-gen end-user/runtime UI. Our backend is Java and Spring Boot, with Cassandra for persistence and Kafka for messaging. Our frontend is React. Jenkins for CI/CD and deploy to Kubernetes on AWS. New Relic and Splunk for observability.

I took a key role in the development of our Flows feature, a next-gen drag-n-drop editor for no-code customization of identity orchestration flows. I worked extensively on the backing microservices, internal SDKs and plugins, and our configuration and runtime UIs.

See above.

I work on authentication services for the PingOne platform.

I was the lead for the test automation team. My responsibilities include development of our test frameworks, reviewing automated test results, working with the development and sustaining teams to debug issues, mentoring the rest of the automation team, code reviews for the entirety of the QA team, assisting the manual testers to most effectively utilize our test frameworks, and more.

My work is mostly with Java, including frameworks and tools such as Spring, TestNG, Google Web Toolkit, Maven, IntelliJ IDEA, TomCat, Selenium, and HSQLDB. I also do some front end work (many of our tools are web applications), which includes Google Web Toolkit, VueJS, Marionette, jQuery, and Bootstrap. I sometimes use Python and frequently make use of shell scripts (I like zsh). Not a day goes by without using Jenkins, JIRA, and Crucible. I make heavy use of Docker during development (and production) because it's incredible at saving time.

Frameworks I have worked on include a Java API for interacting with our products, multiple TestNG based test harnesses (update test harness, cross version compatibility test harness), a performance test harness, a historical test results webapp, a product installation webapp (this automates installation of complex topologies), a custom test parallelization framework/tool (which supports our various test harnesses), and a command line test harness (think a specialized version of pexpect).

I was also the primary point of contact for any Jenkins related issues, although the deployment was owned by another team.

(This work spans my tenure at Ping and UnboundID, but is only included here once for brevity).

Continued work as the automation lead, with major projects including a migration of our on-premise Jenkins to an AWS cloud based deployment, creation of a custom test parallelization framework, and creation of our next generation update test harness.