I am not seeking other opportunities at this time and have not taken the time to write out my responsibilities and accomplishments for my present role. If you would like to know more about what I'm up to in this role, please contact me directly.
As a frontend staff engineer within product engineering, I am responsible for the technical success of my team and for cultivating the practices, documentation, education, tooling, and development culture across all frontend engineers. I partner with product and design to guide new feature development and to balance the demands of new features against existing maintenance needs.
Product. Led frontend teams to design, build, and improve upon several core features within Slack, including: Channel Sections, People & Channel Search, and Slack Connect Invitation Management.
Channel Sections was a particularly challenging feature to launch. In addition to leading the engineers, I guided the product design and built the necessary consensus among product leadership to allow for this feature to launch. (U.S. Patent No. 11,194,447. Delanghe, Rhazi, Nguyen, et al. (2021))
Infrastructure & Tooling. While primarily leading product teams, I've also aimed to improve the foundation on which product development takes place.
Organizational. I strived to improve the practices and overall quality of the engineering organization through its growth.
EMR integration. Led the team to build and iterate on Blink's first integration with an Electronic Medical Records system: a patient prescription portal. The product sends email/sms notifications to patients upon receipt of prescriptions from their doctor and acts as a portal to view medication information and purchase through Blink.
This project was Blink's first HIPAA compliant enterprise as a Business Associate. The unusual corporate structure and imprecise nature of medical records led us to have a unique set of constraints. Partnering with our lawyers and the security team, we designed the system to be particularly robust to failure and incomplete data, observable at clearly defined levels of specificity, and compliant/auditable while practicing continuous delivery.
Direct mail marketing tool. Reworked an abandoned, internal mass mail system to accurately measure conversion, allow for both small-batch & mass mail campaigns, and run experiments on marketing collateral & provider targeting. Discussed use cases and constraints with all of the internal users and stakeholders, designed a simplified workflow to meet their needs, built additional failsafes to aid the detection of manual data entry errors, recorded of state before/after each step for diagnosis, and trained the staff on how to use the new tool.
Engineering managers at Etsy wear many hats. I acted as a technical lead, people manager, product manager, and project manager on two teams: Web Platform and Design Systems.
I strove to provide an environment where everyone on my teams:
I hired three engineers, took two internal transfers, promoted two engineers, helped hire and spin up a replacement for myself as an engineering manager, and am lucky enough to not have fired or laid off anyone.
As a software engineer on the Frontend Infrastructure team, I built and adapted systems and tools to help product teams streamline their web development. I researched, designed, reviewed, scoped, estimated, tested, implemented, documented, and was responsible for the uptime of software systems and tools in support of web browsers accessing Etsy's website.
I collaborated with cross-organizational teams to improve parts of the system with no clear ownership, and pushed for improvements to our test infrastructure, web accessibility, build tooling, debug tooling, project management, and engineering rigor.
Software engineers were expected to:
"REST" HTTP API framework. Designed to access business objects and our 3d assets, the framework unified authentication, authorization, input & output validation, and increased code reuse. This framework improved back-end ease of development, allowed QA to much more easily write automated tests and detect regressions in our back-end API, improved migration of services by utilizing HATEOAS, and allowed for the access of appropriate 3d assets by use of content negotiation to have flexible response content appropriate for the client needs.
Web asset build & deploy system. Designed a build tool to compile static resources (images/CSS/JavaScript/etc...) to refer to each other by content hash, allowing for "infinite" caching by HTTP proxies and CDNs. This reduced bandwidth served for static resources to our cluster, increased cache hit rate, and decreased the total page load time.
"imvujs" frontend JavaScript core library for application development targeting IE8+, FF, Chrome, (mobile) Safari, and node.js. This provided a set of tools, core libraries, dependency injection framework, and test frameworks for consistent application development.
"ui-core" JavaScript framework. Designed and built a JavaScript framework that would integrate well with our back-end "REST" framework. The framework would handle communication with our backend servers, establish a websocket/long-polling connection to detect invalidated (and automatically re-fetch) persisted resources, automatically track and send handled UI events to our data warehouse for analysing usage patterns. The first application to use this was a hybrid sync/async multi-user threaded conversation messaging application.
As one of the 2-4 engineers during my time there, I was responsible for all aspects of the development and deployment of the front-end and back-end software for our anti-spam appliance. I was responsible for feature development, second-level support, and being on-call to diagnose and resolve customer issues.