Introduced an import linter, which established contracts for the dependency graph, to help identify coupling, relationships between applications in the monolith, broke out work to help remove some of the complex dependencies, in support of reduced side effects, improved maintainability, and an easier transition to a non-monolithic architecture.

Fulfilled a mission critical business need for payoff/paydown data capture when the lead stepped back, enabling a successful data tape in support of securitization without compromising application database as source of truth.

Acted as an SME for our data science team to assist in data aggregation across internal and external sources.

Investigated and implemented a major architectural change to no longer create a new homeowner application on application unlock, simplifying the technical lifecycle to improve maintainability.

In support of the work, investigated graphQL as a way to a.) speed up API design process, b.) reduce teams impacting each other, c.) revisit db entities carried into API layer.

Participated in tiger team to investigate/break up legacy database schema that coupled MPA pages to the database. Reduced rigidity, improved maintainability, enabled the team to make product-driven changes.

In support of improved communications and processes, a.) revisited our retro structure to create a safer space, b.) wrote pointing guide to improve cross-team alignment on estimates and improve accuracy, c.) created/led bi-weekly cross-team meeting to surface related work, reduce silos, help technical leads identify consulting SME’s, d.) advocated for shift away from maintainer model to reduce bottleneck.

Created layer on top of generic historical snapshots framework in Django to enable human readable snapshots, created a snapshot diff builder, to capture changes made when the homeowner application was unlocked, reducing the risk of missed changes/effort necessary by staff to identify what had changed.

Closely mentored other engineers by a.) unblocking without solving problems, b.) meeting regularly to support, build relationship, understand concerns, c.) identifying and encouraging around growth areas.

Established service patterns for pulling business logic out of the ORM.

Active on steering committees focused on release management, developer experience and improving code quality.

Implemented functionality within the internal Django portal that limited available contract templates from Formstack to home's state, saving the signing and funding team additional manual effort.

Investigated and integrated a third party, AWS-integrated antivirus service for scanning uploaded documents, reducing risk from one attack vector.

Helped to shape departmental culture, standardize process, consolidate documentation.

Added a new processor to the payment processing report ETL pipeline, modified existing pipelines to meet merchant needs, using custom ETL services and MongoDB.

Spent considerable time with the payment processing report building service to expand on standard reporting for users, becoming a second SME to the original developer.

As one of the first new hires on an established code base, documented processes for pushing code in Jenkins and adding new payment processors from fetching through data normalization at a high level, and at a low level added docstrings to functions/classes, comments to tricky logic, more meaningful variable names, reducing reliance on SME’s and enabling future hires, and current hires working on a new part of the code base, to spin up more quickly.