Zachery Moneypenny

• Built enterprise platform technical strategy for Cars Commerce, including vehicle inventory processing for multiple product platforms and customer data
• Forged alignment around new cenralized services with five different business units
• Worked in concert with Support, Sales, Product, and Operations to turn around failing services and software development process
• Brought new observability capabilities to a variety of polyglot services running in kubernetes
• Operationalized incident and on-call process for new enterprise services

Worked primarily to coordinate across feature teams and ship the new Cars.com platform. In turn, worked as release manager for the first test release to production, drove the prioritization and backlog for an engineering team, managed a variety of engineers and managers across other teams, coached managers on other teams on building better processes and team dynamics, wrote feature code to deliver extra functionality for critical business systems, redesigned the job descriptions and hiring/interview processes for the Software Engineering team, redesigned a core frontend metrics gathering library and rolled out the usage examples to engineers across the organization.

Advised multiple teams working in 8 week cycles on various systems and subsystems for the new Cars.com platform. Worked with engineering managers, product managers and design to determine requirements based on functionality in the existing platform, and strove to build better processes and systems on the fledgling engineering team.

I managed the growth and process of the engineering team at Mobile Doorman, a leading provider for custom resident experiences in the multi-family housing industry.

I worked closely with the VP of Product to build an incredibly efficient and productive dev team that ships to production daily and with high quality. Years spent in agile teams of all kinds have left me with a great toolbox to reach into to continue to work with teams and tweak process until we find a great fit for the team and company.

I managed and architected the evolution of our Rails backend from its seed-stage origins to keep up with our current continued growth, as well as put in place additional systems to give us better data around how our platform is being used.

I work with sales, account managers, customer support and product to drive priority for engineering team across all the stakeholders given our resources.

Finally, alongside the rest of the dev team I work on new features, fixed bugs and made general improvements to the code and build process.

Worked on the Angular frontend to the AVENIO ctDNA analysis product with a diverse technical team stretching from Javascript UI through web services to bioinformatics processing.

Built custom tooling to reduce testing complexity for the Madison development team, allowing engineers to focus on delivering feature code rather than perpetually fiddling with configuration tasks. This points to a particular personal goal I have: to clear away distractions and inconveniences on any team I'm on so everyone else can do their best work.

Facilitated bi-weekly team retrospectives as a way to bring the team closer as well as give folks a sense of what other team members were concentrating on.

Worked with a variety of name-brand clients (such as GoPro, Getty Images and Gamut) to drive new feature and product launches. In doing so, I worked on everything from prioritization and backlog grooming, to architecture design, to implementation and testing.

On some clients, I additionally consulted on improving engineering team dynamics through feedback, process improvements and frequent team retrospectives.

I led several efforts on smaller, internal web site and application projects. For example, I designed the architecture for and built the Cardigan front-end and backend systems.

I also coordinated internal tech talks on such topics as Elixir and Phoenix.

I was a lead developer for Intuit Payroll for QuickBooks and paychecks.intuit.com.

I led a team that worked on refactoring legacy QuickBooks for Windows C/C++ code to talk to a new generation of cloud services. I improved team productivity by 90% (cutting idle time for artifact delivery), introduced unit testing to a code base that everyone said was untestable and walked the fine line between platform improvements and delivering feature code.

I led a team that built https://paychecks.intuit.com, a product for employees of small businesses using Intuit Payroll to view their pay stubs and W-2s. It was a MarionetteJS app that was an initial experiment with single-page apps hooked up to Intuit's mature Java services layer.

I'm particularly proud of the fact that I did all of this very effectively as a remote employee. The teams I worked with and led were mostly in Mountain View, CA while I worked from home or co-working spaces in Madison, WI.

I was a primary developer on Intuit QuickBooks Payroll for Windows. For multiple releases I was in charge of maintenance, new feature development, and stewardship of the legacy C/C++ code base for payroll in QuickBooks. This work involved bootstrapping new feature development and interop using C# and C++/CLI components.

The most significant feature my team launched was for desktop users to be able to e-file payroll tax forms and e-pay payroll tax liabilities across federal plus 50 state jurisdictions. I personally wrote and maintained the payroll rules engine on the client side, as well as the dynamic UI component that handled credential entry and transmission to the TurboTax SOAP API.

Most of my time in this position (including significant releases of the e-file and e-pay feature) was as a remote employee, working from my home and other co-working spaces in Madison, WI.

My team built the QuickBooks automation lab, where nightly builds of QuickBooks for Windows were run through acceptance tests, smoke tests and regression tests. I designed and built the internal web application that allowed test suites to be kicked off and collated results for developers, QA engineers and managers.

I wrote automated acceptance and regression tests, as well as test-related scripts for running and reporting results on automated tests. I also worked on the COM layer of QuickBooks to enable tighter automation integration with the custom UI framework QuickBooks used.