165 lines
7.1 KiB
TeX
165 lines
7.1 KiB
TeX
\documentclass{article}
|
|
|
|
\usepackage{array}
|
|
\usepackage{enumitem}
|
|
\usepackage[letterpaper, portrait, top=0.5in, right=0.5in, left=0.5in, bottom=1.5in]{geometry}
|
|
\usepackage[colorlinks=true, linkcolor=linkColor, urlcolor=linkColor, citecolor=linkColor, anchorcolor=linkColor]{hyperref}
|
|
\usepackage{multirow}
|
|
\usepackage{titlesec}
|
|
\usepackage[usenames, dvipsnames]{xcolor}
|
|
\usepackage{fancyhdr}
|
|
\usepackage{fontspec}
|
|
\setmonofont{Hack Nerd Font}
|
|
|
|
\definecolor{blue}{HTML}{2079C7}
|
|
\definecolor{gray}{HTML}{666666}
|
|
\definecolor{linkColor}{HTML}{0000FF}
|
|
|
|
\newcolumntype{L}[1]{>{\raggedright\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
|
|
\newcolumntype{C}[1]{>{\centering\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
|
|
\newcolumntype{R}[1]{>{\raggedleft\let\newline\\\arraybackslash\hspace{0pt}}m{#1}}
|
|
|
|
\pagenumbering{gobble}
|
|
|
|
\renewcommand{\familydefault}{\sfdefault}
|
|
\renewcommand{\headrulewidth}{0.4pt}
|
|
\renewcommand{\footrulewidth}{0.4pt}
|
|
|
|
\setlength{\headheight}{69pt}
|
|
\setlist[itemize]{noitemsep, leftmargin=1em}
|
|
|
|
\titleformat{\section}
|
|
{\color{blue}\normalfont\Large\bfseries}
|
|
{\color{blue}\thesection}{1em}{\large\uppercase}
|
|
\titleformat{\subsection}
|
|
{\normalfont\Large\bfseries}
|
|
{\thesection}{1em}{\normalsize}
|
|
\titleformat{\subsubsection}
|
|
{\color{gray}\normalfont\Large\bfseries}
|
|
{\color{gray}\thesection}{1em}{\small}
|
|
|
|
\titlespacing*{\section}
|
|
{0em}{0em}{0em}
|
|
\titlespacing*{\subsection}
|
|
{0em}{1em}{0em}
|
|
\titlespacing*{\subsubsection}
|
|
{0em}{0em}{0em}
|
|
|
|
\begin{document}
|
|
|
|
\noindent
|
|
|
|
\pagestyle{fancy}
|
|
\fancyhead[L]{
|
|
\begin{tabular}{L{.4\textwidth} l l}
|
|
\multirow{2}{*}{\Huge{\textbf{Alejandro Angulo} }} & \small{\texttt{}} \space \href{https://github.com/alejandro-angulo}{https://github.com/alejandro-angulo} & \small{\texttt{}} \space \href{https://alejandr0angul0.dev}{https://alejandr0angul0.dev} \\
|
|
& {\small{\texttt{}} \space \href{mailto:\email}\email} & \small{\texttt{}} \space \phonenumber \\ % chktex 1
|
|
\end{tabular}
|
|
}
|
|
\fancyfoot[L]{
|
|
The source code for this document is available at \href{https://github.com/alejandro-angulo/resume}{https://github.com/alejandro-angulo/resume}
|
|
}
|
|
\vspace*{-0.3in}
|
|
\hspace*{-2em}
|
|
\begin{minipage}[t]{.6\textwidth}
|
|
\section*{Professional Experience}
|
|
\subsection*{Sure --- \textit{Staff Software Engineer}}
|
|
\subsubsection*{February 2020--Present}
|
|
\begin{itemize}
|
|
\item Replaced bespoke per-client insurance systems with a generic,
|
|
configuration-driven platform to manage an insurance policy's entire
|
|
lifecycle (quoting, binding, etc.), reducing client onboarding time
|
|
from months to weeks.
|
|
\item Prototyped and led initiative to reduce configuration burden,
|
|
establishing replication infrastructure and onboarding team members to scale
|
|
development efforts.
|
|
\item Identified and resolved critical database lock contention issue
|
|
under load, improving concurrent policy creation capacity from 20 to
|
|
150+ requests (previously caused application crashes).
|
|
\item Discovered and mitigated critical security vulnerability in
|
|
authentication service that allowed arbitrary credential generation;
|
|
coordinated with security team and implemented cryptographic signing
|
|
to prevent future exploits.
|
|
\item Authored backend RFC and owned the data schema design for a
|
|
JSON-driven form framework (CDF), enabling frontend teams to render
|
|
full insurance purchase flows from configuration rather than code.
|
|
\item Designed OpenAPI schema generation pipeline and auto-generated
|
|
TypeScript clients for frontend consumers, eliminating manual type maintenance
|
|
across teams.
|
|
\item Served as primary incident responder, proactively monitoring
|
|
system health via Datadog and Sentry, rapidly diagnosing issues and
|
|
implementing fixes.
|
|
\item Mentored engineers through pairing sessions and onboarding,
|
|
helping multiple teammates ramp up on complex initiatives and gain
|
|
context on platform architecture.
|
|
\end{itemize}
|
|
\subsection*{Everbridge (formerly NC4) --- \textit{Software Engineer}}
|
|
\subsubsection*{October 2018--February 2020}
|
|
\begin{itemize}
|
|
\item Developed and maintained Python (Django app) and PHP applications
|
|
used to help notify clients of potential issues (fires, police
|
|
activity, etc)
|
|
\item Migrated version control system from SVN to Git
|
|
\item Re-architected Python application to improve modularity
|
|
\item Introduced best practices (follow PEP8 for Python, begin linting code, etc.)
|
|
\item Streamlined code review process (integrated with source control)
|
|
\item Maintained and developed a RESTful API written in Python capable of generating
|
|
reports for end users
|
|
\item Worked with product managers to implement ``behind the scenes'' changes
|
|
(upgrading language versions, databases, etc.)
|
|
\end{itemize}
|
|
\subsection*{MedQIA --- \textit{Software Engineer}}
|
|
\subsubsection*{April 2017--September 2018}
|
|
\begin{itemize}
|
|
\item Developed and maintained a Java desktop application used by clinical readers
|
|
and lab technologists to assist in clinical trials
|
|
\item Documented and validated systems to comply with FDA regulations
|
|
\item Worked on Python applications that keep track of the status of scans
|
|
\item Maintained and developed a web client written in PHP and JavaScript that provided
|
|
a dashboard for the data team
|
|
\item Maintained and develop a RESTful API written in Python capable of generating
|
|
reports for end users
|
|
\item Wrote Python scripts that plug in to a Java application in order to provide
|
|
additional functionality (dynamic loading of patients, automating certain tasks
|
|
for end users, etc.)
|
|
\end{itemize}
|
|
\end{minipage}
|
|
\hspace{0.08\textwidth}
|
|
\begin{minipage}[t]{.3\textwidth}
|
|
\section*{About Me}
|
|
I'm a computer nerd with a decade of professional experience. I've always
|
|
enjoyed tinkering with computers and now I get to make a living from it. I'm
|
|
excited about designing maintainable systems and am looking to join a team that
|
|
values a good developer experience.
|
|
\\
|
|
\\
|
|
Outside of my professional work, I still like to tinker with computers. I've
|
|
recently began a master's degree to formalize my understanding of computer
|
|
science. I also enjoy spending time building my own personal ``cloud''
|
|
(self-hosting things like my own git server, CI runner, storage, etc.). I've
|
|
always been fascinated by tech and I'm eager to continue improving my skills
|
|
and the skills of those around me.
|
|
\vspace{1em}
|
|
\section*{Toolset}
|
|
Some tools/frameworks I use regularly in my current role:
|
|
\begin{itemize}
|
|
\item aws
|
|
\item django
|
|
\item docker
|
|
\item git
|
|
\item linux
|
|
\item postgresql
|
|
\item python
|
|
\item rabbitmq
|
|
\item redis
|
|
\item opencode (AI coding agent)
|
|
\end{itemize}
|
|
\section*{Education}
|
|
\subsection*{Georgia Tech}
|
|
\subsubsection*{M.S. in Computer Science}
|
|
\subsubsection*{2026--Present}
|
|
\subsection*{UC Davis}
|
|
\subsubsection*{B.S. in Applied Physics}
|
|
\subsubsection*{2012--2016}
|
|
\end{minipage}
|
|
\end{document}
|