San Francisco, California, United States
As a Staff Software Engineer and Technical Lead, I have a strong background in the development and management of software projects. With over 3 years of experience at Doma and previous leadership roles at Capital One and Vocus, I have a diverse skill set and a track record of successfully leading and motivating engineering teams. In my current role at Doma, I have taken on various responsibilities including designing and implementing software solutions, mentoring and coaching team members, and collaborating with cross-functional teams to ensure project success. My experience in both technical and leadership roles has allowed me to excel in driving results and delivering high-quality products. [engineering leadership, mentoring, nodejs, javascript, typescript, postgres, mysql, azure, aws]
I spearheaded the conception, design, and realization of the Doma Comms service, an integral system that handled the reception, parsing, and processing of emails pertinent to Doma's Title and Underwriting sector. Notable accomplishments include: - Architecting and implementing the Doma Comms API, seamlessly extracting and integrating essential data from incoming emails into our system of record. - Constructing a streamlined workflow using Azure functions and an Azure service bus queue, bolstering operational robustness. - Collaborating closely with Product Managers to identify development priorities, frame quarterly roadmaps, and serve as the team's representative in weekly and quarterly roadmap dialogues. - Orchestrating a high-performing team of 5 adept Software Engineers. Guided their growth through regular 1:1s and formulated tailored development plans. - Conducted daily stand-ups, sprint planning, and retrospectives, ensuring team objectives and accomplishments were recognized and understood by the team.
Led a backend team to craft an API for android and iPhone clients for the Capital One Teen Money App, a customer facing mobile application for parents and children to develop financial literacy. This project required a focus on team leadership, feature delivery, and maximiznig reliability for a customer facing application. Through close collaboration with Product owners and mobile teams and regular re-evaluation of our product roadmap we were able to take this project from complete green-field to production beta testing in about 6 months.
We had two parallel software stacks at Wikispaces; one a large PHP application and another built using a large constellation of microservices based on Node/Mongo. I worked across the entire stack implementing new features, triaging and fixing issues as they arose, and working with the team to plan and scope upcoming projects.
As the Lead Software Engineer at North Social I've been required to wear many hats. I needed to build out infrastructure so our devs could build new apps, stay in touch with support to triage bugs and sift the high and low priority bugs, and work with product development to determine a development schedule.