Kyle Tilman

During my time at Lumos, I was able to deliver a number of high priority projects where I was the main contributor. The achievements I am most proud of are more connected to my leadership than to raw lines of code. My tools were: code reviews, pairing, asking questions, defining goals and scope, running planning sessions and retros. These efforts did not result in an algorithmic masterpiece but they did align our team, help us focus our efforts and multiply the efficiency and efficacy of the whole team. I was able to bring my leadership skills combined with technical skills to multiple teams to help them deliver on important, time-sensitive projects they would not have been able to accomplish otherwise.

• Researched, documented and rewrote a legacy internationalization system written in Ruby, in order to move us to a new version of our internationalization vendor's API. This was a huge mission-critical project, on a tight deadline. Given the deadline (3rd party API deprecation) I wasn't going to be able to deliver 100% of the features we needed. I documented possbile solutions, conferred with the stakeholders (product, marketing, internationalization) and we decided on a path forward. We made the target cutover with no downtime. We simplified the API and deprecated a legacy system that no longer deployed without manual intervention and arcane tribal knowledge.
• Introduced the team to our first AWS Lambda driven service using our shiny new IaC (CDK) tool!
• Worked hand in hand with the Infrastructure team to deliver on some time-sensitive IaC (CDK typescript) work that the team was not able to accomplish
• Planned out the Infrastructure and backend for one of the companies new mobile backend and launched it into production
• Researched and introduced a proof-of-concept for a 3rd-party authentication vendor to simplify our in-house authentication provider. Then used the POC as the basis to shave about 10 planned weeks of work for building a new Authx system
• As for leadership, I worked very hard to assimilate information across many teams and stakeholders in order to refine our product vision and engineering process.
• Mentored teammates on Typescript best practices through code reviews and pair programming.

As a backend Scala dev at Carbon I started and helped build a team responsible for handling millions of lives worth of patient data. When staffing left another team short on people, I jumped in and helped refine the vision of the team and begin delivering on their big goals that had been pushed back several times.

• Built the Interoperability team and actively setup agile process for delivery, reflection and growth of the team.
• Planned and executed on new Event-driven architecture in Scala to decouple and simplify logic for reporting COVID test results and immunizations. Deprecated existing legacy code.
• Researched and integrated with multiple 3rd parties (Redox, IronBridge) in our Scala backend to enable the scaling of all interoperability ingress and egress
• Led a company-wide push for a better on-call process and delivered a new set of processes, documentation and scheduling. Collaborated with support and engineering to build out tooling and process that worked.
• Started an education initiative to increase the effectiveness of our new recruits in our unique Scala environment.
• Comprehensively identified requirements, domains, and contexts in the Labs Team in pursuit of decoupling our logic and moving towards microservices.
• Mentored multiple other engineers to help guide them in growing their technical and soft skills.