Moved up the engineering stack to get a better sense of how changes in our backend would affect our customers (i.e. through our APIs)

Lead the effort to rewrite our eCheck processing using our new infrastructure and the subsequent migration; this will be the first major payment flow onto our new system

Drove discussions to finally getting our core parts of our code out of our monolith as a major engineering initiative

Maintained the health and stability of all our payment products (e.g. credit card payments, refunds, chargebacks, settlements, fees, etc.)

Initiated a pivot to redesign our event driven asynchronous state machine to create a new asynchronous, deterministic, more flexible workflow-based processing engine built on the principles of reactive programming and idempotence

This new "money engine" is called Pym and uses Waltz, a distributed write-ahead log built within WePay (refer to https://wecode.wepay.com/posts/waltz-a-distributed-write-ahead-log) as its data store. Building Pym as a Waltz application provides the built-in support of enabling multi-region support for our payment processing.

Supported major team initiative to consolidate and migrate our payment processing to use Chase on the backend instead of a variety of other third-party payment processors with code reviews, on-call support, and other task completions

Created documentation for our on-call runbook with notable contributions to dealing with stuck payments caused by inefficiencies/bugs in our current money engines

Received mentorship from some quality engineers.