Bulk infra and ci/cd info now on resume
This commit is contained in:
@@ -80,27 +80,68 @@
|
||||
|
||||
\section{Experience}\label{sec:experience}\removesectionpadding
|
||||
\cventry{Sept. 2019 --\\Apr. 2025}{Hardware Test Engineer I/II}{SpaceX}{Redmond, WA \& Remote}{}{
|
||||
Developed, owned, and maintained critical software, hardware, and infrastructure to support high-rate and high-reliability validation of space-bound hardware.\newline
|
||||
Detailed achievements:
|
||||
Developed, owned, fabricated, debugged, and maintained critical software, hardware, and infrastructure to enable and support high-rate/high-reliability validation of space-bound hardware, and support effective team operations
|
||||
\begin{itemize}
|
||||
\item Designed, fabricated, commissioned, deployed, and supported test systems for Starlink flight computers and power conversion systems, with ~4500 tested units reaching orbit.
|
||||
\item Achievement 2 (with sub-achievements)
|
||||
\item Owned, developed, and completed the consolidation, automation, and containerization of all Components Test Team infrastructure and applications
|
||||
\begin{itemize}
|
||||
\item Sub-achievement (a);
|
||||
\item Sub-achievement (b), with sub-sub-achievements (don't do this!);
|
||||
\item Unified all team applications into a dedicated monorepo, along with default templates enabling rapid new project startup
|
||||
\item Converted all existing applications to containerized, de-duplicating work via intermediate images per common project type
|
||||
\item Created commonized Makefiles for the repo, plus tailored versions per application, allowing for fast local development which mimicked production deployments and provided common interfaces when deploying
|
||||
\item Added Sentry failure monitoring to all applications, including local development runs, to simplify collaborative resolution of failures
|
||||
\item Created and maintained ansible playbooks for the end-to-end ci/cd of the team's containerized applications, as well as test-system/server commissioning and management
|
||||
Tasks included:
|
||||
\begin{itemize}
|
||||
\item Sub-sub-achievement i;
|
||||
\item Sub-sub-achievement ii;
|
||||
\item Sub-sub-achievement iii;
|
||||
\item CI/CD
|
||||
\begin{itemize}
|
||||
\item Build, test, validation, deployment, and cleanup of application containers via pull request and merge triggers
|
||||
\item Deployment with self-recovery and auto-start of networks and containers for development, staging, and production environments
|
||||
\item Templating and management of NGINX web configurations, alongside ACME certificates, for development, staging, and production environments
|
||||
\item Upload of passing container, and custom python package, builds to artifactory infrastructure
|
||||
\item Periodic cleanup of artifactory assets to reduce resource usage
|
||||
\end{itemize}
|
||||
\item Test System/Server Commissioning/Management
|
||||
\begin{itemize}
|
||||
\item Commissioning and association of new servers/vms with core SpaceX infrastructure such as HashiCorp Vault
|
||||
\item Automated installation and association of server monitoring tools with central monitoring infrastructure
|
||||
\item Management and updates to system and baseline packages
|
||||
\item Automatic interface and network configuration
|
||||
\item Automatic downstream network switch configuration to apply appropriate vlans, trunking, and configs
|
||||
\end{itemize}
|
||||
\end{itemize}
|
||||
\item Owned, managed, and greatly improved monitoring of team infrastructure, test systems, and applications
|
||||
\begin{itemize}
|
||||
\item Configured and managed the team's Sentry instance, which greatly increased our team's ability to triage and solve critical application errors quickly
|
||||
\item Owned and managed the Grafana + Loki instances for both the Components Test and Starlink Hardware Test teams, providing useful insight into hardware/software bottlenecks, statuses, and metrics.
|
||||
Created and maintained the following dashboards:
|
||||
\begin{itemize}
|
||||
\item System metrics monitoring such as cpu, network, memory, and disk usage to quickly find and eliminate hardware bottlenecks
|
||||
\item Per-application metrics such as connection counts, unique users, response times, load-balancing status, etc\ldots to help find pain points and ensure applications remained stable and responsive
|
||||
\item Per-product and per-test metrics to help identify common failures for devices-under-test, as well to to evaluate any out-of-family measurements
|
||||
\end{itemize}
|
||||
\item Helped manage the Component Test Team's OpsGenie integrations and schedules, and responded to pager tickets for the infrastructure sub-team
|
||||
\end{itemize}
|
||||
\item Sub-achievement (c);
|
||||
\end{itemize}
|
||||
\item Achievement 3
|
||||
\item Achievement 4
|
||||
\end{itemize}}
|
||||
\cventry{Jan. 2019 --\\Mar. 2019}{Avionics Test Engineer (Intern)}{SpaceX}{Hawthorne, CA}{}{
|
||||
Wrote software in Python for automation of avionics hardware test systems. Performed circuit debugging on test system hardware. Validated test software performance per aerospace standards. Automated Jira work ticket generation for two internal avionics teams to improve product investigation, test, and repair workflows.
|
||||
\item Designed, fabricated, commissioned, deployed, and supported test systems hardware/test software for Starlink satellite flight computers and power boards
|
||||
\begin{itemize}
|
||||
\item ~4500 flight computers, from four flight hardware generations, were tested using these systems and are/were in orbit
|
||||
\item ~4000 power boars, from two flight hardware generations, were tested using these systems and are/were in orbit
|
||||
\end{itemize}
|
||||
\end{itemize}
|
||||
}
|
||||
% \cventry{Jan. 2019 --\\Mar. 2019}{Avionics Test Engineer (Intern)}{SpaceX}{Hawthorne, CA}{}{
|
||||
% Supported the avionics test team via python driver/module development, hardware debugging, workflow automation, and monitoring/driving of qualification tests to completion
|
||||
% \begin{itemize}
|
||||
% \item Finished an orphaned proof-of-concept python driver for a VISA connected 3k psi differential pressure regulator, plus unit tests
|
||||
% \begin{itemize}
|
||||
% \item Uncovered critical firmware bugs in the pressure regulator and worked with the manufacturer to alpha/beta test fixes until solved, while also suggesting improvements to their product documentation
|
||||
% \item Added self-monitoring of potentially unsafe pressure states and combinations, with automated system safing where possible
|
||||
% \end{itemize}
|
||||
% \item Created a python module, and associated unit tests, to automate exercising and validating cots/in-house pressure sensors against the ISO 9001 standard
|
||||
% \item Automated cross-system Jira work ticket generation to improve build reliability investigation, test, and repair workflows
|
||||
% \item Successfully debugged, and recommended fixes for, electrical failures of in-house designed test fixture printed circuit boards
|
||||
% \item Actively drove and monitored qualification of avionics hardware through shock testing
|
||||
% \end{itemize}
|
||||
% }
|
||||
% \cventry{Sept. 2013 --\\Aug. 2019}{Automation Engineer/Student Automation Engineer}{Sinnhuber Aquatic Research Lab}{Corvallis, OR}{}{Description}
|
||||
% \cventry{Apr. 2016 --\\May 2018}{Student Software \& Electrical Engineer}{CEOAS Ocean Mixing Group}{Corvallis, OR}{}{Description}
|
||||
|
||||
@@ -108,30 +149,14 @@
|
||||
|
||||
|
||||
\section{Skills}\label{sec:skills}\removesectionpadding
|
||||
\cvitem{Legend}{\cvskill{1}: Least Experience\hspace{1cm}\cvskill{5}: Most Experience}
|
||||
|
||||
\setcvskillcolumns[][0.23]
|
||||
\cvskillhead[-0.1em]
|
||||
|
||||
\cvskillentry*{Languages:}{5}{Python}{\yearsSince{2013}{09}{01}}{\small{
|
||||
Experienced in Python. there is so much text here which means so much room for activities!
|
||||
}}
|
||||
\cvskillentry{}{2}{C++}{\yearsSince{2019}{09}{01}}{}
|
||||
\cvskillentry{}{4}{Bash}{\yearsSince{2008}{02}{01}}{}
|
||||
\cvskillentry*{OSes:}{5}{Linux}{\yearsSince{2008}{02}{01}}{NixOS, Ubuntu, CentOS, Arch}
|
||||
\cvskillentry{}{4}{Windows}{\yearsSince{2008}{02}{01}}{}
|
||||
\cvskillentry*{OCI:}{5}{Docker}{\yearsSince{2021}{08}{01}}{}
|
||||
\cvskillentry{}{3}{Podman}{\yearsSince{2021}{08}{01}}{}
|
||||
\cvskillentry{}{2}{Kubernetes}{\yearsSince{2021}{08}{01}}{}
|
||||
\cvskillentry*{VC:}{4}{Git}{\yearsSince{2013}{09}{01}}{}
|
||||
\cvskillentry{}{2}{Svn}{\yearsSince{2019}{09}{01}}{}
|
||||
\cvskillentry*[1em]{Methods:}{4}{Agile}{6}{}
|
||||
|
||||
\cvitem{Most}{Linux (Ubuntu, CentOS NixOS) | Python | Test Driven Development | Bash Scripting | Docker/Podman/OCI | Ansible | Git | Makefiles | Sentry | Grafana}
|
||||
\cvitem{Some}{Grafana Loki | HashiCorp Vault | Bitwarden | Artifactory | NGINX | Puppet | Web Full Stack Development}
|
||||
\cvitem{Least}{Kubernetes | Google Cloud Platform | Amazon Web Services | Subversion | C++}
|
||||
\removesectionmargin
|
||||
|
||||
|
||||
\section{Hobbies/Interests}\label{sec:hobbies/interests}\removesectionpadding
|
||||
\cvitem{}{\small{Home Automation | Homelab | Motorcycling | PCB Design }}
|
||||
\cvitem{}{\small{Home Automation | Homelab | Motorcycling | PCB Design | 3D Modeling \& Printing }}
|
||||
|
||||
%----------------------------------------------------------------------------------------
|
||||
% FOOTER
|
||||
|
||||
Reference in New Issue
Block a user