mirror of
https://github.com/posquit0/Awesome-CV.git
synced 2026-07-17 14:35:29 +08:00
LPG after AI eval and update
This commit is contained in:
Larry Gouger
parent
7c68bcbbd6
commit
7420a59517
6 changed files with 89 additions and 202 deletions
|
|
@ -572,7 +572,7 @@
|
|||
% Usage: \cvsubsection{<subsection-title>}
|
||||
\newcommand{\cvsubsection}[1]{%
|
||||
\vspace{\acvSectionContentTopSkip}
|
||||
\vspace{-3mm}
|
||||
\vspace{-2mm}
|
||||
\subsectionstyle{#1}
|
||||
\phantomsection
|
||||
}
|
||||
|
|
@ -580,7 +580,7 @@
|
|||
% Define a paragraph for CV
|
||||
\newenvironment{cvparagraph}{%
|
||||
\vspace{\acvSectionContentTopSkip}
|
||||
\vspace{-3mm}
|
||||
\vspace{-2mm}
|
||||
\paragraphstyle
|
||||
}{%
|
||||
\par
|
||||
|
|
@ -596,13 +596,13 @@
|
|||
% Define an entry of cv information
|
||||
% Usage: \cventry{<position>}{<title>}{<location>}{<date>}{<description>}
|
||||
\newcommand*{\cventry}[5]{%
|
||||
\vspace{-2.0mm}
|
||||
% \vspace{-2.0mm}
|
||||
\setlength\tabcolsep{0pt}
|
||||
\setlength{\extrarowheight}{0pt}
|
||||
\begin{tabular*}{\textwidth}{@{\extracolsep{\fill}} L{\textwidth -4.5cm} R{4.5cm}}
|
||||
\ifempty{#2#3}
|
||||
{}
|
||||
{\vspace{-3mm}\entrytitlestyle{#2} & \vspace{-3mm}\entrylocationstyle{#3} \\}
|
||||
{\vspace{-2mm}\entrytitlestyle{#2} & \vspace{-2mm}\entrylocationstyle{#3} \\}
|
||||
\ifempty{#4}
|
||||
{\entrypositionstyle{#1} \\}
|
||||
{\entrypositionstyle{#1} & \entrydatestyle{#4} \\}
|
||||
|
|
@ -673,7 +673,7 @@
|
|||
|
||||
% Define an environment for cvitems(for cventry)
|
||||
\newenvironment{cvitems}{%
|
||||
\vspace{-4.0mm}
|
||||
\vspace{-2.0mm}
|
||||
\begin{justify}
|
||||
\begin{itemize}[leftmargin=2ex, nosep, noitemsep]
|
||||
\setlength{\parskip}{0pt}
|
||||
|
|
@ -681,7 +681,7 @@
|
|||
}{%
|
||||
\end{itemize}
|
||||
\end{justify}
|
||||
\vspace{-4.0mm}
|
||||
\vspace{-2.0mm}
|
||||
}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -36,10 +36,10 @@
|
|||
|
||||
% Colors for text
|
||||
% Uncomment if you would like to specify your own color
|
||||
% \definecolor{darktext}{HTML}{414141}
|
||||
% \definecolor{text}{HTML}{333333}
|
||||
% \definecolor{graytext}{HTML}{5D5D5D}
|
||||
% \definecolor{lighttext}{HTML}{999999}
|
||||
\definecolor{darktext}{HTML}{414141}
|
||||
\definecolor{text}{HTML}{333333}
|
||||
\definecolor{graytext}{HTML}{5D5D5D}
|
||||
\definecolor{lighttext}{HTML}{999999}
|
||||
|
||||
% Set false if you don't want to highlight section with awesome color
|
||||
\setbool{acvSectionColorHighlight}{true}
|
||||
|
|
|
|||
|
|
@ -8,24 +8,10 @@
|
|||
%-------------------------------------------------------------------------------
|
||||
|
||||
\begin{cvparagraph}
|
||||
I was hired by Cox Automotive, then called Dealer.com, as an
|
||||
Engineering Manager, one of two in their Manhattan Beach, CA office.
|
||||
I managed engineers who were parts of 2 scrum teams, a total of 7
|
||||
individuals.
|
||||
\end{cvparagraph}
|
||||
|
||||
%\vspace{-1.00mm}
|
||||
|
||||
\begin{cvparagraph}
|
||||
Prior to becoming an Engineering Manager in my career, I had been a
|
||||
software engineer, and after becoming an Engineering Manager, I kept my
|
||||
hands in the code, usually by intercepting one-off requests that
|
||||
risked derailing my teams' planned efforts.\@ In late 2016, Cox
|
||||
Automotive decided to end its engineering presence in Manhattan
|
||||
Beach.\@ At that point, I transitioned to an individual contributor role as a
|
||||
Senior Developer, and I began working remotely as part of a Scrum team based
|
||||
in Burlington, VT.\@ After working remotely for a year I chose to
|
||||
relocate to Burlington, VT hoping to improve advancement opportunities.
|
||||
Joined Cox Automotive (then Dealer.com) in 2013 as an Engineering Manager in the Manhattan Beach, CA office,
|
||||
leading 7 engineers across 2 scrum teams. Follwing the closure of that office, I transitioned to an individual
|
||||
contributor role as a Senior Developer in late 2016, then relocated to Burlington, VT in 2017 to pursue
|
||||
technical leadership opportunities as a Scrum Tech Lead and Lead Software Engineer.
|
||||
\end{cvparagraph}
|
||||
|
||||
|
||||
|
|
@ -33,62 +19,29 @@ relocate to Burlington, VT hoping to improve advancement opportunities.
|
|||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Lead Software Engineer{\enskip\cdotp\enskip}Scrum Tech Lead} % Job title
|
||||
{Cox Automotive. --- Automotive Client Insights / Command Center} % Organization
|
||||
{Cox Automotive --- Automotive Client Insights / Retail Reporting} % Organization
|
||||
{Burlington, VT} % Location
|
||||
{Aug 2024 --- Present} % Date(s)
|
||||
{}
|
||||
\end{cventries}
|
||||
% \vspace{-6.00mm}
|
||||
|
||||
\begin{cvparagraph}
|
||||
I joined this newly forming scrum team focused on a new reporting tool, Command Center.
|
||||
Its goal is to bring together Reporting and Analytics for a broad array of Cox products.
|
||||
Currently each product sold by Cox Automotive includes its own data analytics and reporting systems.
|
||||
Initially Command Center will be a jumping off point to the scattered reporting sub-systems, and slowly
|
||||
take over reporting directly from within Command Center for more and more use cases.
|
||||
\end{cvparagraph}
|
||||
|
||||
% \vspace{-2.00mm}
|
||||
\begin{cventries}
|
||||
\cventry{Accomplishments} % job title
|
||||
{} % organization
|
||||
{} % location
|
||||
{} % date(s)
|
||||
{%
|
||||
\begin{cvitems} % description(s) of tasks/responsibilities
|
||||
\item {Architected unified reporting platform consolidating data from 6 product lines}
|
||||
\item {Led technical design sessions and drove adoption of GitOps practices with Argo CD}
|
||||
\item {Designed scalable data pipeline using Snowflake/dbtCloud triggered by data publication events}
|
||||
\begin{cvitems}
|
||||
\item {Joined newly forming scrum team building Command Center, a unified Reporting \& Analytics platform consolidating reporting across a broad array of Cox Automotive products.}
|
||||
\item {Architected unified reporting platform consolidating data from 6 product lines.}
|
||||
\item {Led technical design sessions and drove adoption of GitOps practices with Argo CD.}
|
||||
\item {Designed scalable data pipeline using Snowflake/dbt Cloud triggered by data publication events.}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Lead Software Engineer{\enskip\cdotp\enskip}Scrum Tech Lead} % Job title
|
||||
{Cox Automotive. --- Dealer.com / Vehicle Incentives Processing} % Organization
|
||||
{Cox Automotive --- Dealer.com / Vehicle Incentives Processing} % Organization
|
||||
{Burlington, VT} % Location
|
||||
{Feb 2021 --- Aug 2024} % Date(s)
|
||||
{}
|
||||
\end{cventries}
|
||||
% \vspace{-6.00mm}
|
||||
|
||||
\begin{cvparagraph}
|
||||
I joined the scrum team focused on Vehicle Incentives to bring it stability and leadership.
|
||||
Dealer.com's (DDC) incentives team collects Cash, APR, and Lease incentives from multiple sources,
|
||||
links them with the vehicles currently in inventory at our clients' dealerships,
|
||||
and makes them available for display on the dealerships' DDC websites.
|
||||
\end{cvparagraph}
|
||||
|
||||
% \vspace{-2.00mm}
|
||||
\begin{cventries}
|
||||
\cventry{Accomplishments} % job title
|
||||
{} % organization
|
||||
{} % location
|
||||
{} % date(s)
|
||||
{%
|
||||
\begin{cvitems} % description(s) of tasks/responsibilities
|
||||
\item {Processed tens of thousands of inventory updates impacted by active incentives}
|
||||
\item {Integrated with dozens of Incentive Providers}
|
||||
\begin{cvitems}
|
||||
\item {Brought technical leadership and stability to a critical system that collects Cash, APR, and Lease incentives from dozens of providers and links them with dealership inventory for display on Dealer.com websites.}
|
||||
\item {Processed tens of thousands of inventory updates impacted by active incentives.}
|
||||
\item {Integrated with dozens of Incentive Providers.}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
|
|
@ -98,73 +51,33 @@ and makes them available for display on the dealerships' DDC websites.
|
|||
{Cox Automotive --- Dealer.com / Platform Engineering} % Organization
|
||||
{Burlington, VT} % Location
|
||||
{July 2020 --- Feb 2021} % Date(s)
|
||||
{}
|
||||
\end{cventries}
|
||||
% \vspace{-6.00mm}
|
||||
|
||||
\begin{cvparagraph}
|
||||
I joined the DDC Platform Scrum team to pursue a Scrum Team Tech Lead role. Dealer.com's Platform Engineering team is responsible for several backend systems supporting Dealer.com's Web sites, Advertising and Inventory systems. (Team Chemistry)
|
||||
\end{cvparagraph}
|
||||
|
||||
% \vspace{-2.00mm}
|
||||
\begin{cventries}
|
||||
\cventry{Accomplishments} % Job title
|
||||
{} % Organization
|
||||
{} % Location
|
||||
{} % Date(s)
|
||||
{%
|
||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||
\item {}
|
||||
\item {}
|
||||
\begin{cvitems}
|
||||
\item {Joined the DDC Platform team as Scrum Tech Lead, supporting backend systems for Dealer.com Web sites, Advertising, and Inventory.}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
%---------------------------------------------------------
|
||||
|
||||
\cventry{Senior Software Engineer} % Job title
|
||||
{Cox Automotive --- Dealer.com / Agency Advertising Engineering} % Organization
|
||||
{Burlington, VT{\vspace{1mm}\newline}Manhattan Beach, CA} % Location
|
||||
{May 2017 --- July 2020} % Date(s)
|
||||
{}
|
||||
\end{cventries}
|
||||
% \vspace{-6.00mm}
|
||||
|
||||
\begin{cvparagraph}
|
||||
The team's focus was on systems to support digital advertising at Google, Microsoft, Facebook, and YouTube.\@
|
||||
Our systems enabled advertising the inventory of our clients' dealerships as their inventory changed.\@
|
||||
I was responsible for the design, implementation, testing, deployment, and support of these systems.
|
||||
\end{cvparagraph}
|
||||
|
||||
% \vspace{-2.00mm}
|
||||
\begin{cventries}
|
||||
|
||||
\cventry{Accomplishments} % Job title
|
||||
{} % Organization
|
||||
{} % Location
|
||||
{} % Date(s)
|
||||
{%
|
||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||
\item {}
|
||||
\item {}
|
||||
\begin{cvitems}
|
||||
\item {Owned design, implementation, testing, deployment, and support of digital advertising systems integrating with Google, Microsoft, Facebook, and YouTube.}
|
||||
\item {Enabled advertising of client dealership inventory as that inventory changed.}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
%---------------------------------------------------------
|
||||
|
||||
\cventry{Engineering Manager} % Job title
|
||||
{Cox Automotive --- Dealer.com / Social Applications Development} % Organization
|
||||
{Manhattan Beach, CA} % Location
|
||||
{Jan. 2013 --- May 2017} % Date(s)
|
||||
{}
|
||||
% \vspace{-6.00mm}
|
||||
|
||||
\cventry{Accomplishments} % Job title
|
||||
{} % Organizatio\textbf{api technologies:} rest, swagger/openapi, spring remoting}n
|
||||
{} % Location
|
||||
{} % Date(s)
|
||||
{\vspace{-0.5mm}
|
||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||
\item {\textbf{Team Building:} Regular 1-on-1 meetings and Quarterly check-ins/reviews}
|
||||
{%
|
||||
\begin{cvitems}
|
||||
\item {Managed 7 engineers across 2 scrum teams; practiced regular 1-on-1s and quarterly check-ins/reviews.}
|
||||
\item {Kept hands in the code by intercepting one-off requests that risked derailing team commitments.}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
|
|
@ -173,57 +86,29 @@ I was responsible for the design, implementation, testing, deployment, and suppo
|
|||
%---------------------------------------------------------
|
||||
%---------------------------------------------------------
|
||||
|
||||
\cvsection{Previous Experience --- ITG, Inc.}
|
||||
|
||||
%\cvsubsection{Skills at ITG}
|
||||
\vspace{-1.00mm}
|
||||
\cvsection{Earlier Experience}
|
||||
|
||||
\begin{cventries}
|
||||
\cventry{Senior Engineering Manger} % Job title
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry{Senior Engineering Manager / Senior Software Engineer} % Job title
|
||||
{ITG, Inc.} % Organization
|
||||
{Culver City, CA} % Location
|
||||
{Oct. 1991 --- July 2011} % Date(s)
|
||||
{}
|
||||
% \vspace{-6.00mm}
|
||||
|
||||
\cventry{Accomplishments} % Job title
|
||||
{} % Organization
|
||||
{} % Location
|
||||
{} % Date(s)
|
||||
{\vspace{-0.5mm}
|
||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||
\item {Led technology transitions (eg.\ from \CC{} on Solaris to \CS{} on Win32), and launched a remote team in NYC.}
|
||||
\item {Team Building, Team member reviews and one-on-ones, Hiring, Performance Improvement Plans, and Firing}
|
||||
\end{cvitems}
|
||||
{%
|
||||
\begin{cvitems}
|
||||
\item {Held progressive engineering and management roles across QuantEX trading systems, Algorithmic Trading Systems, POSIT Now \& Match NOW, and ITG Platform Tools.}
|
||||
\item {Led technology transitions (e.g., \CC{} on Solaris to \CS{} on Win32) and launched a remote engineering team in NYC.}
|
||||
\item {Hands-on leadership: hiring, team building, performance management, and reviews; practiced Scrum, Extreme Programming, and Pair Programming.}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
|
||||
%---------------------------------------------------------
|
||||
%\cvsubsection{Summary of Responsibilities}
|
||||
%\vspace{-1.00mm}
|
||||
|
||||
\begin{cvsubentries}
|
||||
\cvsubentry{}{Senior Engineering Manger --- ITG Platform Tools}{Oct. 2009 --- July 2011}{}
|
||||
\cvsubentry{}{Engineering Manger --- POSIT Now \& Match NOW}{Sept. 2004 --- Oct. 2009}{}
|
||||
\cvsubentry{}{Engineering Manger \& Senior Software Engineer --- Algorithmic Trading Systems}{May 1997 --- Sept. 2004}{}
|
||||
\cvsubentry{}{Senior Software Engineer --- QuantEX \& Canadian QuantEX}{Oct. 1991 --- May 1997}{}
|
||||
\end{cvsubentries}
|
||||
|
||||
%---------------------------------------------------------
|
||||
%---------------------------------------------------------
|
||||
|
||||
\cvsection{Previous Experience --- TRW, Inc.}
|
||||
|
||||
\begin{cventries}
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry{Senior Member of Technical Staff} % Job title
|
||||
{TRW Inc.} % Organization
|
||||
{Redondo Beach, CA} % Location
|
||||
{June 1985 --- Oct. 1991} % Date(s)
|
||||
{Senior Developer, C, SunOS/Solaris, worked on applications that exploited a TRW search technology called the Fast Data Finder.}
|
||||
{Senior C/SunOS developer building applications on top of TRW's Fast Data Finder search technology.}
|
||||
|
||||
%---------------------------------------------------------
|
||||
\end{cventries}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -9,44 +9,44 @@
|
|||
\begin{cvskills}
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Architecture/Patterns} % Category
|
||||
{Microservices, event-driven architecture, domain-driven design} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Observability} % Category
|
||||
{New Relic, Sumologic, Prometheus, Grafana, distributed tracing} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Security} % Category
|
||||
{Authentication/authorization, OAuth/OIDC, Secrets Management} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{AI Tools} % Category
|
||||
{Anthropic Claude Code, Github CoPilot, MCP servers, Skills} % Skills,
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{DevOps / IAC} % Category
|
||||
{AWS, Docker, Kubernetes, GitOps, Github Actions, Terragrunt, Terraform, CDK, Serverless} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Server Technology} % Category
|
||||
{Spring Boot, Spring Data, Spring Cloud AWS, Spring Web, REST API, MySQL, Snowflake, dbtCloud} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Database} % Category
|
||||
{Snowflake, dbtCloud, MySQL, DynamoDB, MmongoDB} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{AWS} % Category
|
||||
{EKS, ECS, Lambda, S3, SQS, SNS, RDS, API Gateway, SSM/Parameter Store, Secrets Manager, EC2, DynamoDB, IAM}
|
||||
\cvskill{Architecture} % Category
|
||||
{Microservices, Event-driven Architecture, Domain-driven Design, REST APIs, Distributed Systems, System Design at Scale} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Programming} % Category
|
||||
{Java, Python, Kotlin, Clojure, \CS{}, C, \CC{}, perl} % Skills
|
||||
{Java, Python, Kotlin, Clojure, \CS{}, C, \CC{}, Perl} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{AWS} % Category
|
||||
{EKS, ECS/Fargate, Lambda, Step Functions, API Gateway, S3, SQS, SNS, RDS/Aurora, DynamoDB, IAM, SSM/Parameter Store, Secrets Manager, EC2} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{DevOps / IaC} % Category
|
||||
{Docker, Kubernetes, GitOps, Argo CD, Helm, GitHub Actions, Terraform, Terragrunt, CDK, Serverless} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Back-end} % Category
|
||||
{Spring Boot, Spring Data, Spring Cloud AWS, Spring Web, REST, Swagger/OpenAPI, gRPC} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Data} % Category
|
||||
{Snowflake, dbt Cloud, MySQL, DynamoDB, MongoDB} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Observability} % Category
|
||||
{New Relic (APM, Infrastructure, Synthetics), Sumo Logic, Prometheus, Grafana, Distributed Tracing, LaunchDarkly} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Security} % Category
|
||||
{Authentication/Authorization, OAuth/OIDC, Secrets Management} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{AI Tools} % Category
|
||||
{Anthropic Claude Code, GitHub Copilot, MCP Servers, Skills} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cvskill{Methodologies \& Leadership} % Category
|
||||
{Scrum, Technical Mentorship, Code Reviews, Rally} % Skills
|
||||
{Scrum, Kanban, Technical Mentorship, Code Reviews, Tech Lead, Rally} % Skills
|
||||
|
||||
%---------------------------------------------------------
|
||||
\end{cvskills}
|
||||
|
|
|
|||
|
|
@ -8,13 +8,11 @@
|
|||
% CONTENT
|
||||
%-------------------------------------------------------------------------------
|
||||
\begin{cvparagraph}
|
||||
I'm seeking a role as a Lead Software Engineer. My career includes
|
||||
time as a Lead Software Developer and as an Engineering Manager. I've
|
||||
concluded that I enjoy the former more. I enjoy having my hands in
|
||||
the architecture, design, coding, testing, deploying, monitoring, and
|
||||
overall ownership of a software system. I understand that there's
|
||||
more to developing reliable, scalable, maintainable, and performant
|
||||
software systems than simply writing the code. I enjoy the team
|
||||
building process and helping to mentor all team members to grow and
|
||||
develop.
|
||||
Lead Software Engineer with deep experience designing, building, and operating reliable, scalable
|
||||
distributed systems. Strong technical foundation across AWS cloud-native architectures (EKS, ECS,
|
||||
Lambda), the Spring ecosystem, and modern DevOps practices (Kubernetes, GitOps, Terraform).
|
||||
Equally comfortable as a hands-on Scrum Tech Lead driving architecture and design
|
||||
decisions and as a former Engineering Manager who values mentorship, technical growth, and team
|
||||
ownership of systems end-to-end --- from design through deployment, monitoring, and production
|
||||
support.
|
||||
\end{cvparagraph}
|
||||
|
|
|
|||
|
|
@ -9,7 +9,11 @@
|
|||
\usepackage{fontspec}
|
||||
|
||||
% Define shortcut to load the Font Awesome font.
|
||||
\newfontfamily{\FA}{FontAwesome}
|
||||
% Default to a local "fonts/" directory if the host class/document hasn't
|
||||
% already defined \@fontdir; this lets the bundled FontAwesome.ttf be picked
|
||||
% up without requiring a system-wide install.
|
||||
\providecommand*{\@fontdir}{fonts/}
|
||||
\newfontfamily{\FA}[Path=\@fontdir]{FontAwesome}
|
||||
% Generic command displaying an icon by its name.
|
||||
\newcommand*{\faicon}[1]{{
|
||||
\FA\csname faicon@#1\endcsname
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue