Staff Software Engineer
Current2019 still dealing with creating vendor access points. Expanded from just service providers to include claim event consumers and external scoring vendors. Spent time with spring boot creating demo/test implementations for these providers. Also ported the runtime framework to our platform version 8 (a pre-gradle, java 7 version, build environment). 2018 switched over to integration of third party service providers (vendors) into our platform. This is basically a cloud based environment utilizing aws (dynamodb, s3, ecs) and requiring creating docker containers and gradle/groovy work to make all the parts work together. 2017 added a definition first (swagger) rest framework which utilized composition to have platform, internal app, and customer, into a unified, versionable, stable api. Also, a read only json schema based definition with mapping to provide a versionable, stable, json documents.The products supported h2, Oracle, and Sqlserver databases. The products ran on Windows and Linux platforms. And was deployable in Jetty, Websphere, Weblogic, Tomcat, and JBoss servers. I have participated in multiple release cycles and as a lead in the platform's integration pod have mentored a lot of fellow developers and worked with multiple different agile approach. The integration pod is responsible for how we permit customer to extend our product's backend. These integration points where batch processing, workflows, webservices, servlets, work queues, documents, and plugins. Prior to being promoted to the platform team, I work with a specific application team dealing with the Policy capture and management. Important projects there included making permissions and roles customer extendable (later adopted by platform); adding a different ACL (Access Control List) mechanism; extending workflows to permit visualization and management of complex processes like renewals and submissions (later adopted by platform); and worked on umbrella coverage.