Responsibilities as Director of Enterprise Development at GMI: * Lead the full lifecycle of software development for the organization* Create and participate in cross-functional teams to gather requirements, deploy systems, and train users in new best-practices for our software* Drive yearly goal-setting sessions with company board members* Juggle individual sprint planning goals against our big-picture goals* Run sprint review and planning meetings for key stakeholders, and summarize that meeting for all org middle/upper management.* Ensure deployed solutions fit facilities of various sizes with different production practices across 4 time zones and 2 countries.* Set coding standards, select frameworks, and choose deployment practices for our application* Participate in code reviews and design sessions with team engineers * Contribute regularly to our codebase - Primarily PHP and Angular with a SQL Server database

During my first year at Slalom I've lead the creation of a data visualization application for a publicly traded major communications company. The application leverages a suite of modern web technologies including:* Angular 4 Single Page Application* Mapbox for rendering maps with sales volume heatmaps* AWS Lambda functions for server layer API* AWS Aurora for RDBMS* AWS Step Functions state machine for processing big data input* Automated end-to-end testing using headless ChromeAs the technical lead on this project, I'm tasked with overseeing the other engineers, making key architecture decisions, and implementing features.

In the five years I worked at Emberex, I was the Technical Manager on several projects of varying scale for different clients. These projects were full stack data-driven web-interfaces, for which I wrote software and lead teams using Javascript (browser and node), Java, and PHP. I lead the team that built the flagship internal project, Bloxi - a community quiz website. Our team designed, created and built it, and I oversaw the technical aspects. This included selecting the technologies used, assigning work to our engineers, and coding key features. The server is Node.js based, connecting to a MongoDB database, serving data in classic REST calls. The browser code is Backbone based, using Handlebars templates and LESS for layout and rendering. Check it out at bloxi.comBloxi allows users to create and customize social quizzes on a variety of topics with different question types. The editing interface, graphs, and results tracking are supported by MongoDB aggregate queries and a number of open source graphing tools. Technical challenges we faced in building the site included:* rendering quizzes for different devices and resolutions* presenting results in a meaningful way for questions with 10 answers or 100,000 answers* optimizing data for rendering speed by using denormalized collections* rendering quiz results for sharing on social media platforms* compressing and combining browser code into single chunks for easy downloads* creating an internal A/B testing system for different site versions* migrating existing user data as our database needs changed.Other projects I was the Technical Manager for at Emberex include: * A dashboard for mobile game developers to manage in-game advertisements. (PlayHaven) * A site for helping special education teachers compare results metrics to their peers. (University of Oregon) * A tool for helping high school administrators ensure curriculum meets federal standards. (EPIC)

During the 7 years at Grain Millers I managed a team building internal and external use web applications. These systems are still being used extensively to manage Grain Millers operations at several different milling facilities.The primary system was built in PHP and running on an MS SQL database. (Back in 2004, PHP was a common platform.) It started as a means to track Quality Assurance results in the laboratory at the mill in Eugene Oregon. Over the years it grew to include maintenance and sanitation scheduling, customer complaint tracking, production scheduling, shipping management, yields analysis, audit compliance tracking, customer service support... etcTo gather requirements for these systems I'd often move my workspace into the department where I intended to focus on next. I'd spend weeks in the QA lab, or reviewing maintenance documentation, or travelling to Saskatchewan for onsite visits at a mill there. I'd review existing paper and Excel based tracking systems, and discuss with managers and equipment operators what data they create and need in their daily work.I'd then spend weeks overseeing the creation of a system customized to fit those needs, often changing the way the company ran their business in the process. For example, prior to my systems each location had different quality assurance procedures and methods even if creating the same final product. Once my systems were in place, each location followed a standardized method.After creating the system, I'd travel back to the location where it was to be used and work with those same people to train and guide them in their use of the new software. This would often include workers from multiple shifts, requiring me to be available and teach workers at all hours of the day in multiple timezones. As a side project, I also oversaw the creation of grainmillers.com including graphic design, interviewing different departments to write copy, writing the copy, and design of the code. (Still in use.)