Katy Fox Email and Phone Number

When I made the decision to leave Keap, I was pursuing another Product Management opportunity. As I neared the end of my two weeks I realized that my true passion is Software Development. Although I love Product Management, I am not at my happiest unless I can be hands-on creating awesome software. I completed my two weeks at Keap as planned, and spent a few months resetting and strengthening my technical skills.

At Keap, I worked with a very talented group of people to help small businesses succeed. I was the Product Manager for a set of teams that worked on advancing Keap’s tech strategy by extracting a set of platform from our core code-base. I was also the Product Manager for another fundamental and cross-cutting team, the Auth team, that solved for all of Keap’s authentication needs. On both teams, we focused on strengthening our Software Delivery best practices and improving our pace, productivity and quality, so that we could deliver what our customers needed to turn leads into satisfied clients. On the extraction teams, I focused primarily at the charter level clarifying the problems we were trying to solve, establishing our team vision, identifying the key few valuable metrics to measure along the way, and prioritizing at a high level the objectives we wanted to target. I also worked closely with the teams to bring the user’s perspective to our acceptance criteria, to help balance our ideal timeline with scope decisions, and to brainstorm the best way to slice our deliverables so that we could learn quickly with faster delivery cycles.

Throughout my career as a Software Engineer I became increasingly passionate about Product Management. In this role as a PO, I worked side-by-side with Senior Product Management to understand the product vision and roadmap, and I worked with our Engineering team to break that vision into features that we consistently delivered to stay on-course with our roadmap.Making the move from Software Engineering to Product Management was a tough but rewarding experience. I have an entirely new perspective on the product development process, and a deeper understanding of the goals and challenges that Product Managers face.

For most of my career at Vantiv I was a Senior Software Engineer on an integrated payments EMV product. It is a self-hosted RESTful API that is consumed by developers of point of sale systems. It interfaces with the point of sale system, the PIN pad that accepts chip cards, and the payment processing gateway, to encapsulate and abstract any operations involving card data. I started my career at Vantiv as a Mid-level Software Engineer, and I was lucky enough to work with a team of talented developers and mentors that helped me achieve my goal of becoming a Senior Software Engineer. Since then, I've had the opportunity to help build, on-board and mentor a brand new team.Some of my biggest achievements at Vantiv include being selected to on-board our new team, being nominated by a teammate for the company's Envisioneer Award, being recognized as one of 12 top performers of 2016 across several locations, being selected as one of three employees to present our product at the company's yearly tech expo, traveling to our sister-site to teach others about our product, and being selected to co-record a podcast about our product.I've also had the opportunity to participate in two book clubs where we studied Clean Code and Head First Design Patterns, which have significantly improved my coding style.

I started my career at GlobalMed as a Test Automation Engineer. I created an application that ran hundreds of API regression tests that we were able to use as a part of our deployment process. A few months into the project, I was asked to be a developer on the team that developed these APIs and the website that used them. At GlobalMed, I gained experience with C#, Java, SQL Server, HTML5, CSS, JavaScript, and JQuery Mobile, and I worked in an environment that was ISO and HIPAA compliant. In addition to automated testing and development, I also focused on maintaining and updating Test Plan and Requirements documents.

As a Software Tester at The Astronautics Corporation of America, I worked on a team that developed an on-board avionics maintenance system. I started my career as an intern, and I was hired on full-time when I graduated. I primarily focused on executing and maintaining test plans for a specific piece of the maintenance system. I also performed code reviews of the software itself and completed change management requests. The software I was responsible for testing and reviewing was written in C and C++, and the test plans were comprised of manual steps, Bash scripts and small test applications written primarily in C. The test environment was Debian Linux.I also developed a complete onboarding guide for new employees that included information about the company, getting their PCs set up properly, and information about our lab environment.The project I enjoyed the most was reverse-engineering a specific test machine’s environment so we could build a back-up.