Portfolio

I currently work at Kin, a home insurance company headquartered in Chicago.

I was part of the original team that designed and built the Claims app from the ground up in 2022, and continue to work on it today. As a senior engineer I’ve touched a lot of code, including architecting and leading several projects.

A couple of the things I’ve worked on over the last few years -

• I architected and led an integration with a 3rd party vendor, allowing us to intake claims via SMS and phone. In addition to the actual software that I wrote, I also handled a lot of the coordination between Kin engineering, Kin operations, and the vendor, ensuring we delivered the product on time.
• I architected and led a major restructuring of Claims data. Due to several teams working on a very short deadline, we had data being saved in several different places. I led the effort to consolidate three processes’ worth of data accurately and without downtime.
• I architected and led major updates to the claim intake process to allow us to process additional categories of claims. This also shored up some vulnerabilities in our endpoints, making the app more secure.
• I established and built out patterns for looking up role-based permissions as part of a larger initiative to give Kin employees access to resources based on user roles.
• I created a process that enabled Kin to collect low-intent leads for the first time. In addition to setting up the relevant API endpoints, I also needed to research which third-party communication app to use, synced data between a third party vendor and our customer database, and set up a dashboard for the marketing team’s use.

In addition to direct contributions to the code base and project planning, I also do more intangible work around the team as a whole -

• I’ve mentored more junior devs, including pitching in to help less experienced devs with architecture briefs and project planning
• I have led several weekly Claims meetings to facilitate knowledge sharing and collaboration across the team, including with QE and product
• I proactively work on general code health – I’ve led a couple of initiatives to clear out old code and bring parts of the code base that could use some love up to a higher standard

While at ReviewTrackers, a reputation management company in Chicago, I worked on both the customer app and the internal app used by the Customer Success team.

A couple of things I worked on while I was there –

• I built out key sections of a new SMS alert feature, including creating front-end components and ensuring duplicate alerts could not be sent.
• I built key components and a front-end interface for automated Quarterly Business Review decks created with Google slide APIs.
• I built a front-end interface for automated QBRs, including quality-of-life enhancements based on feedback from the Customer Success team.
• I implemented design changes and auto-generated responses for immediate, daily, weekly, and monthly email alerts, such as auto-generated responses to new reviews.
• I maintained and improved the internal Customer Success app, including adding new pages and maintaining CS tools.
• In addition to feature work, I also contributed to component libraries and internal style cleanup initiatives to create a cohesive user experience.

Click here for examples of the features I worked on.

My first software development job was with Synap, an asset management app and part of the Imagineer Technology Group.

• I refactored existing UI components and existing front-end architecture to unify styles and functionality throughout the application, creating a more streamlined user experience and improving flexibility of application components.
• I implemented several highly visible client-facing features and internal API endpoints.
• I maintained and contributed to a repository of reusable React components.

Click here for examples of the features I worked on.

Before I became a software dev, I worked as a data analyst at a pharmaceutical marketing consultancy. As a consultant, my day to day tasks were quite variable; however, there were a few longer term projects that I worked on –

• I generated automated quarterly nation-, region-, and territory-level target lists that balanced valuable customers, rep-submitted information, and historical sales information from third-party vendors
• I generated a national sales plan for a new client from the ground up, based on publicly available datasets and competitor data
• I designed and implemented automated processes to check the accuracy of data and client-side implementation of business rules on a weekly, monthly, and quarterly basis, including flexible checks depending on several different contracted layouts and accurately replacing incomplete data with restatements
• I generated automated and accurate weekly, monthly, and quarterly compliance and payout reports for a client, including an automated email generation tool and flexible options for exporting data
• I quickly and accurately led updates to handle unexpected and unannounced changes to data sources, ensuring tight quarterly timelines were not affected
• I provided a variety of timely and accurate “what if?” analyses on quarterly models and client sales data to provide actionable insights to the client