Explored potential business ideas full time. I was the only person working on these projects. Qrunch is a working spreadsheet prototype and was a fun programming challenge. I used an event driven architecture with a functional programming style to give users the ability to easily do complex multi variable scenario planning, which is not well supported in current spreadsheets. It has a very responsive (fast) UI and mature features like undo/redo capabilities. I wrote my own spreadsheet language parser in PEG.js to support custom annotations since I needed to support more operators than regular spreadsheets. Concept write up: https://www.stephensisk.net/posts/modern-spreadsheet/, video walkthrough showing working code: https://youtu.be/BOQl13E1sSQ (things get exciting at 3:45). I don’t know how to make money with this, but it was really fun to build :)ThxNoThx (https://www.thxnothx.com) was primarily a project to explore running my own business. I chose it as a small scale project with the potential to get enough customers to support myself as a solo founder. It is a working service with paying customers (very few, but some!) I started an LLC, iterated on my sales funnel by doing multiple rounds of google advertising, landing pages, and small scale user interviews.

* Kaggle runs machine learning competitions, hosts datasets, and allows users to run notebooks. We are a public website with several million users. Written in Typescript/React/C#/ASP.NET Core/EF on GCP with MSSQL/Redis/BigQuery/Stackdriver Tracing+Logs. Kaggle is a remote-first team* I was the primary engineer responsible for Kaggle’s GDPR compliance - I worked with legal to understand the requirements for Kaggle and coordinated work across all of Kaggle’s sub-teams (~20 devs). This required substantial work since Kaggle previously had no deletion functionality.* I led a team of 3 other engineers to re-write kaggle’s login UI + backend, doing the initial design work then collaborating with others to get the work done.* I worked on a rewrite of Kaggle's notification system, including working with marketing, design, and other teams at kaggle to define what types of notifications we sent to user. Then I worked with another developer to rewrite our notifications infrastructure to support those needs.* Other projects include: 1) as part of a 3 person team we re-worked Kaggle’s moderation rules + tooling to improve user satisfaction and reduce incentives for gaming the system and 2) owning my team’s metrics, helping our team define business success metrics (used in our OKRs and individual feature tracking) and building non-trivial SQL queries to make them concrete.

GCP Dataflow Team:* Took dataflow's UI from prototype quality to finished v1 product - I worked with designers and senior leadership on team to refine. Our frontend was written in JS/Angular.* Became Tech Lead of dataflow monitoring team (4 other SWEs) - we were responsible for how users debug their Dataflow jobs. I was responsible for the dev work of my team as well as defined OKRs and did project management for the team as well as working on features myself. Written in C++ running on Google’s internal equivalent of kubernetes (borg + internal Spanner). As part of this, I was responsible for building strong relationships with the Stackdriver teams and we delivered several important joint features.* Led project to get more database connectors added to Apache Beam - worked with the Apache Beam open source community to define testing goals for connectors and managed contractors. Written in Java running on Kubernetes.

Doing contract programming work, primarily for EDP Software in Vancouver, BC. EDP is a Canadian company selling HR software to manage shifts for facilities with complex 24‐hour people scheduling needs. A Ford factory, nuclear power plant and several Shell refineries are EDP customers. EDP has a small dev team, with 4 active devs using C#, Javascript, AngularJS, ASP.NET & WebAPI, Entity Framework and SQL Server.

Worked as part of a team of ~10 devs. LiquidPlanner is a Ruby on Rails shop, with a jQuery front end. I worked on a variety of projects, including adding features to our Access Controls system and upgrading the app to Rails 3.

• As part of a team of ~10 devs, the majority of my time was spent coding. Our technology stack was C#/Javascript (Google Closure)/Asp.Net/NHibernate/Mysql/LINQ. • I led a team of 3 devs to build a email marketing campaign management tool for Appature. I defined what the devs on the team worked on and ensured they weren’t blocked. I worked with the CTO to define the early feature set + UI mocks, then designed the feature’s architecture and was initially the sole dev before asking for and getting 2 more devs assigned to the project in order to meet our deadlines. The product was a success and is in use by many of Appature's customers. • As part of that project, I built a flow chart editor in Javascript (based on JSPlumb), allowing users to draw a flowchart of actions to execute. • I also designed the backend execution engine that takes the flowcharts and runs them. Problems with this code could result in losing customers so I designed the engine with testability in mind and added heavy automated testing. The engine is also designed to allow high scale throughput on our servers' limited resources.• With only ¼ of a PM assigned to our feature, in addition to being a dev, I was responsible for spotting high-level issues and ensuring that what we’re building will actually meet customer needs. This included meeting with customers and running usability tests. I introduced some very lightweight process (kanban) to ensure that we can focus on coding, not coordinating with each other or reporting progress.

The team I worked on owns Phone/Messaging/Email/Contacts/Feeds. I was the PM owner of the code that we use to talk to facebook, windows live and other social networks to retrieve feeds data, as well as the day-to-day owner of the engineering relationships with those partners.

I was the owner of various features across WLMail, responsible for the UI and backend of those features. I also worked with partners like Hotmail so they would plan and deliver new features to support Mail.

As part of a team of ~10 developers, I architected and coded new features. I also did extensive bug fixing in Mail’s large codebase, working in areas including our message & contacts database, UI, various mail protocols, and MIME parser. This included doing a set of Windows Update security patches for Outlook Express

Working as a tester in Autos, I wrote test plans, test cases and then implemented test automation (primarily C# interacting with SQL databases.) I also built a monitoring tool which allowed us to detect problems in our group’s web servers.