Mike Deichman Email & Phone Number

Seattle, Wa, Us

As a Product Manager, I played a pivotal role in the future of WatchGuard’s Firebox Management in WatchGuard Cloud- Attended and led calls with partners and customers to hear their feedback, show them new features/capabilities, assist in solving problems they may be facing and to set expectations with the roadmap.- Listened to Sales Engineers, Support and Training teams about current challenges the user base was experiencing.- Kept an eye on the market and competitors to identify opportunities for new feature or adjustments we could make to our own products.- Used the above information to generate requirements for products I was responsible for. This included creating Epics and stories in Jira as well as detailed requirements pages in Confluence.- Attended planning meetings with development to answer questions about the partner or customer’s concerns and to set the appropriate priority for each item.- Worked closely with User Experience (UX), Documentation and Training organizations to ensure the best possible outcome for new features or adjustments to current features.- Served as the company liaison for third party certification bodies such as NSS, NetSecOpen and SaferInternetUK- Recorded and edited videos to show off new additions to the product.

Seattle, Wa, Us

Holding many responsibilities, I helped stabilize my team by managing their resources, organizing work to come and ensuring the highest quality of features for which we were responsible.- Worked closely with developers during the planning and the ongoing development of new features to ensure a deep knowledge of features. In turn, this raises the quality of test cases.- Conducted performance evaluation for my team’s portion of the code.- Used Python to create scripts which allow us to test our devices in ways we weren’t previously able and to help reproduce customer cases.- Coordinated with the overseas test team to ensure all testing was getting performed. I also reviewed the results from their efforts where it pertained to my team’s features.- Reproduced high priority bugs typically found in the field.- Drove my team’s SCRUM process. Our team had planning meetings and retrospectives that I hosted and guided. This involved getting input from developers, development leads and product owners to ensure the correct items were being worked on.- Created and maintained test cases.- Maintained my team’s lab resources. If new devices needed to be added, old devices needed to be removed, or if we simply needed a newly designed test bed, I took care of it.- Presented my team’s features and changes to the documentation and support organizations.

Redmond, Washington, Us

In this position was responsible for:- My team’s fuzzing program. We had a few VM servers running Codenomicon Defensics. I helped others in my team and outside my team use the tool. I was also responsible for maintaining the servers.- Automating test cases. Our team had a number of automation engineers. I used Python to make use of their code and build tests.- Assisting other groups with "test cluster" networking and troubleshooting. This relates to test devices in a production environment. If there was an issue, we helped figure out if it’s the network or not, then help fix the issue if it is.- Evaluation of potential new hardware and software for use in production. Including review of test results submitted by the potential vendors.- Coordinating the effort of on-boarding new solutions. Testing, pilots, results review, bug and feature request reviews.- Keeping an eye out for future lab tools to help us work more efficiently.

Houston, Texas, Us

In this position I was responsible for:- Performance evaluation and benchmarking of intrusion prevention systems (IPS) and next generation firewall (NGFW) products using equipment from IXIA, BreakingPoint and various other tools which can be run on Linux servers.- Evaluating potential new hardware for future products. Processors etc,- Demonstrating our testing to potential customers, proving our reliability in testing.- Support existing customers on corner case traffic issues. This usually involved analyzing a capture of problematic traffic and explaining to the customer why the traffic yields the results they’re experiencing.- Competitive analysis. Comparing our products with similar products our competitors offer to the market.- Assisting other groups internally with any performance related issues they might have seen. - Working closely with Hardware Engineering, Functional/System Test, FPGA team, Architects and the core Software Developers of TippingPoint’s products.- Developing new test cases and scenarios with input from Product Management, Architects and customers.- Testing the test equipment. If we saw unexpected results, we needed ways to capture massive amounts of traffic and ways to analyse that traffic to determine if the tool is functioning as expected. Our solution for this was Endace. Our work was then fed back to IXIA and BreakingPoint’s developers for future improvements. We also used IXIA to test the Endace to verify it was capturing in an uncompromised manner.- Maintenance of our lab environment. The environment would change constantly due to the variety of problems we handled and recreated. This could get messy if not kept after. Also with new devices entering our rackspace, I had to re-work the infrastructure once in a while.- Perpetually seeking ways for our team to improve its processes and efficiency.- Training new members of our group.

Us

In this position I was responsible for:- Installing and verifying drivers/software found in HP’s Proliant Enterprise Foundation Packs on a multitude of enterprise level servers.- Functional and Feature test of Blade Networks enterprise level blade chassis switches.- Functional and Feature test of the management software for those blade switches.- Evaluation and troubleshooting of customer issues.- Setting up and tearing down network configurations on a regular basis.