9610 S 242nd Ct, Kent, WA 98030
I have over twenty years of professional development experience across both large and small organizations and in roles ranging from solitary developer to staff engineer. I've worked on projects ranging from standalone executables to real-time simulation components to database-backed web services. I'm a dedicated, hard-working self-starter with strong verbal and written communication skills.
2021 April - Present / Cobalt.io / Kent, WA
Staff Software Engineer / CX - Integrations Team / 2021 April - Present
The CX (customer experience) integrations team is responsible for building out Cobalt's first public-facing API.
- Participated in the full development cycle.
2015 January - 2021 March / Indeed.com / Seattle, WA
Software Development Engineer II / Quartermaster Team / 2018 April - 2021 March
The Quartermaster team is responsible for self-service provisioning of internal MongoDB, MySQL, and Redis instances.
- Contributed to an open-source Kubernetes RabbitMQ operator; unfortunately changing priorities meant that this project was not continued.
- Made several changes in the core reservation logic (which determines which physical host each database will run on). These changes included adding the concept of a "reservable size", distinct from the "physical size" of the host, and refactoring existing reserved emergency disk space into the new model.
- Building on that change, introduced CPU oversubscription to better utilize existing physical hosts.
- Added ability to reserve multiple resources atomically, allowing for resources to be guaranteed to run on the same physical host(s).
- Migrated about twenty projects from Ant to Gradle.
- Participated in the daytime oncall rotation to support the entire application stack.
- Helped maintain and improve the entire application stack, from Go-language tools that interface directly with the OS to the user-facing React webapp.
Software Development Engineer II / DREMR Team / 2015 October - 2018 March
The DREMR team was responsible for Indeed's external (jobseeker- and employer-facing) email infrastructure.
- Designed and implemented a MongoDB-backed caching layer to allow the replaying of email-creation requests from remote datacenters in the case of catastrophic link failure.
- Designed and implemented an abstraction layer/service for an LSM-tree-based on-disk data store, allowing us to begin breaking up and horizontally distributing a legacy monolithic program.
- Participated in the daytime oncall rotation to support the entire application stack.
- Helped maintain and improve the entire application stack.
Software Development Engineer II / Resume Team / 2015 January - 2015 September
The resume team was the only Seattle-based team at the time. It was responsible for all aspects of a jobseeker's resume, from entry/import on the web to search.
- Worked with the data science team to attempt to identify features of "good" resumes for the purposes of coaching jobseekers to improve their own resumes.
2008 January - 2014 December / Amazon.com / Seattle, WA
Software Development Engineer II / Source Team / 2010 June - Present
The source team was responsible for the "commit to build" portion of Amazon's internal development workflow. Its role includes supporting all corporate revision control systems, managing a related database-backed metadata service, and (initially) code search and code review.
- Acted as the Scrum Master in an agile, scrum-based development process.
- Took part in my team's on-call rotation. Responsibilities during the on-call period included 24-hour pager availability, working with our customers (other Amazon developers) to answer questions and provide advice, coordinating with sibling teams on large-scale issues, and fixing any newly-discovered, high-priority bugs in our systems.
- Participated in the design, implementation, and support of Amazon's proprietary, Git-based distributed revision control system. This systems combined the advantages of a centralized revision control system (authoritative master version of code, automatic backups, auditability) with those of a distributed revision control system (horizontal scalability, easy peer-to-peer sharing of code under development).
- Also participated in the design, implementation, and support of several other large Amazon-wide systems, including a database-backed metadata system to aggregate source code change information and a system to abstract away differences in revision control systems for certain basic operations.
- Ensured a high level of availability for the corporate Perforce and Subversion servers. The former was one of the largest Perforce installations in the world at the time with over 8 million CLNs (and counting).
- Participated in the recruiting process, having performed over 100 phone screens and a dozen in-house interviews.
- Mentored interns and junior team members.
Software Development Engineer II / Build Team / 2008 January - 2010 May
The build team was responsible for all aspects of Amazon's internal source code and build systems, supporting the entire workflow from managing the revision control system through successfully completing builds of software packages. Associated systems include code search, code review, Perforce and Subversion revision control systems, a proprietary distributed build system, and several metadata systems.
- Took part in on-call rotation similar to that described above.
- Worked to improve Subversion integration with the rest of Amazon's infrastructure. Upgraded the Subversion server from version 1.3 to 1.4. This included upgrading several custom components.
- Spearheaded effort to reduce the time required to index the corporate source code repositories from twenty-seven hours to under eight.
1999 May - 2007 December / FAAC Incorporated / Ann Arbor, MI
Senior Engineer / Military Simulator Group / 2005 September - 2007 December
System engineer for most military simulator contracts throughout this period; technical lead on all military simulator contracts. Duties included estimating effort required to meet requirements, mentoring and guiding other technical staff, and acting as technical-managerial liaison.
- Designed, implemented, and tested a facility (QSL - "QNX Services for Linux") to provide basic QNX 4-style send/receive/reply messaging on Linux.
- Ported existing QNX 4 simulator product to Linux by using QSL. Maintained cross-platform QNX 4/QNX Neutrino/Linux capabilities from a single code base throughout conversion.
- Converted and verified via regression testing several legacy missile simulations written in Fortran to C++. Implemented a cross-platform DLL framework to support dynamic loading of missile simulations.
Engineer / Military Simulator Group / 2002 September - 2005 September
Technical lead on most military simulator contracts during this period.
- Designed and implemented second generation of distributed real-time simulation architecture. Responsible for maintenance and expansion of architecture to support new simulator product lines.
- Maintained and improved inherited code for performing real-time input and output (both digital and analog) for simulators.
Associate Engineer / Military Simulator Group / 1999 May - 2002 September
Assisted senior personnel in designing a QNX 4 distributed real-time simulation architecture for use in driver-trainer simulators. Completely implemented said architecture, totalling about 15,000 lines of code.
1995 September - 1999 May / University of Toledo / Toledo, OH
Bachelor of Science, Computer Science and Engineering
- Graduated magna cum laude.
- Participated in the honors program.
Languages and Tools
- Scala: Core language (2.5 years, current)
- Go: Core language (2.5 years, current)
- Java: Core language (12 years, current); Spring (8 years, current); Hibernate (4 years, very stale)
- Python: Core language (5 years, moderately stale)
- Ruby: Core language (10 years, slightly stale); Rails (5 years, moderately stale)
- Perl: Core language (10 years, very stale)
- C and C++: Core languages (10 years, very stale)
- SQL Databases: SQL (12 years, current); PostgreSQL (5 years, current); MySQL (5 years, slightly stale); Oracle (5 years, very stale)
- NoSQL Databases: MongoDB (5 years, current)
- Integrated Development Environments: IntelliJ (10 years, current); Eclipse (5 years, very stale); Visual Studio (5 years, very stale)
- Command Line Tools: Zsh (20+ years, current); Standard Linux Toolchain (20+ years, current)
- Revision Control: Git (10 years, current); Perforce (14 years, very stale); Subversion (8 years, very stale)
- JVM: Application programming (12 years, current)
- Kubernetes (2 years, current)
- Docker (3 years, current)
- Linux: Scripting (20+ years, current); Application programming (10 years, moderately stale); System programming (5 years, very stale)
- Microsoft Windows: Application programming (5 years, very stale)
- QNX 4/QNX Neutrino: Application programming (8 years, very stale); System programming (8 years, very stale)
- Member of the American Cryptogram Association.
- Implemented automated solvers for various types of ciphers using techniques such as brute-force keyspace exploration, simulated annealing, and hillclimbing. Wrote algorithms to recognize valid English text.