As a Snap Kitchen software engineer I've worked across the stack from iOS (swift 3-4) and backend (python) to facilitate the digital aspects of selling food. I've been part of building pieces of the stack from promotions to delivery and pickup to consuming point-of-sales data via Kafka connectors to populate our bundled meal plans. Technologies include python, Swift, Kafka and postgres.

Back-end engineer for the Mailbox app at Dropbox. Responsibilities include writing Node.js for the email sync / reconciliation back-end and parts of the business-layer back-end, large-scale architecture, tremendous scaling, deployment and maintenance. At its peak Mailbox processes 100’s of millions of emails per day. The platform stack contains Mongo, Redis, Node.js, AWS, RabbitMQ.

Back-end engineer for the Mailbox application. Acquired by Dropbox in March 2013. 4 weeks after launch the Mailbox system was processing ~50M emails per day. Initial demand was so strong that due to concerns over scale Mailbox built the now infamous ‘reservation system’ for the app.

Senior software engineer and product lead for Appconomy, a mobile application development and services platform company. In this full-stack engineering role I have helped build or prototype multiple native iOS applications and corresponding back-end services (via REST). Initially the primary iOS application was a group chat / collaboration tool; later incarnations became hybrid iOS/Android apps for ‘daily deal’-style commerce. The platform stack is J2EE on Tomcat7 with a MongoDB backend. I have also been responsible for our cloud (Amazon AWS) infrastructure - EC2 management/ initialization, AMI generation and management, automated cloud backups, monitoring and deployments. As the early MongoDB champion at Appconomy I am also responsible for deployment and configuration of our database infrastructure.

Technical Lead / Architect / Project Owner for a Ruby On Rails collaboration application practicing Agile methodologies. In this role I led a technical team along with designers from IDEO to build out a team-based collaboration tool. I helped architect and build out a resource-oriented suite of services (user service, content service, provisioning/config service, etc). All services are consumed via REST endpoints. I also handled a significant amount of 3rd-party API integrations (social media apis, for the most part) into new systems. I was in charge of infrastructure vetting, build-out, monitoring and maintenance (both rack-mount hosting and cloud), and deployment tasks (custom capistrano recipes). I managed almost all database administration work, along with schema design (largely MySQL). In this role I enjoyed a large range of technologies - Passenger, Apache, MySQL, MongoDB, Rails, Ruby, Prototype.js, JQuery, Linux, Monit, etc.

Kalivo started as a portal for customer-engagement software, built on an RoR stack (a version of LAMP on AWS). Kalivo, and the software application being built, was brought into the nGenera family in 2007, where the focus of the application became more centered towards team collaboration.

Scalable Software provides applications for corporations to help manage their compliance levels over multiple regulations (both industry-standard regulations and government mandated). Regulations such as COBIT, SOX, and ISO 17799 are covered. The application is a web-based hosted solution called Command Center. It is a J2EE app with Resin/Apache and an Oracle backend.

EMO was an online financial operation similar to PayPal with some major differences such as the ability to print plain paper money orders on your home printer. Since the application dealt with money there was a wide range of secondary code for fraud detection/management, security and 3rd party integration (such as with brick and mortar banks and numerous e-currencies). The application was a J2EE app using mysql and apache/tomcat configuration. Related technologies included Flash, Velocity, Turbine (MVC Framework), Torque (ORM), James Java Mail Server, and others.

Contract Development for Dell Computer through Cobb Information Systems. This J2EE application ('Harmony') managed peripheral products primarily from third-parties. Harmony fed multiple downstream applications and inevitably provided the peripheral data to the online site. Harmony allowed its users to manage product information such as lead time, category trees, 'hot/top sellers' and the like. During my tenure the app went from a local product to a globalized product, including Canada and the UK. It also went from a hand-built framework of javascript and XML/XSL to Struts.

Coagent was a short-lived startup that focused on providing software to manage your network remotely. The goal was to provide managed services via SOAP, JAVA, JMX and other technologies. A functional prototype was built and demo'ed.

iMark was an online auction site for used industrial equipment. Bidding could occur via the website (much like eBay), or through our real time bidding application. The real-time bidding application was a Java applet that handled 'bids' as MSMQ messages. The application was developed with IIS, ASP, COM, Delphi and had an Oracle back end.

Integrated with a third part reporting application (Brio). Maintained and improved a web-based document repository for offsite sales. The sales force maintained data in a spreadsheet, then could later upload it to the repository. The application allowed for multiple types of data manipulation. Built on Visual Basic, COM, ASP with a sql server backend.