32 Commits

Author SHA1 Message Date
efa0f0760f Fix extra spaces in summary 2024-04-24 17:01:04 -04:00
e349dc89bb Update experience to tune for MBTA application 2024-04-24 15:50:55 -04:00
3964c315df Replace generic introduction with executive summary 2024-04-24 15:38:37 -04:00
9dffb95070 Remove durations 2024-04-24 15:38:37 -04:00
52871bdf71 Remove unused imports 2024-04-24 15:38:37 -04:00
b080d4af53 Merge major and minor into one line to conserve space 2024-04-24 15:38:36 -04:00
b4a9e73113 Swap priority of business names with job titles
Move 3DS to below WPI
2024-04-24 12:56:08 -04:00
64aab159fa Add phone number 2024-04-24 12:55:43 -04:00
8bdcf88fdc Update summary for MBTA OCC job 2024-04-24 01:28:45 -04:00
276c709e15 Update skills to reflect current experience 2024-04-24 01:28:35 -04:00
2e08eab36c Update with job duraions 2024-04-24 01:28:20 -04:00
a5768cdb0a Update PI experience with administration details 2024-04-24 01:24:14 -04:00
f146b4b097 Update summary with new goals 2024-04-19 20:18:13 -04:00
5a636bb9aa Update experience to include PI 2024-04-19 20:18:02 -04:00
88a7198f3a Update byline 2024-04-19 14:43:27 -04:00
6a3676e53d Update summary and skills for portal experience 2024-04-19 14:24:35 -04:00
22675b8d45 Add ubuntu dependency instructions 2024-04-18 17:28:35 -04:00
03353d85ad Add cover letter for FPF application 2022-05-03 11:57:15 -04:00
371d7e8d27 Update resume to focus more on interpersonal experience 2022-05-03 00:08:06 -04:00
43b8a31053 Remove header from coverletter template 2022-05-02 23:59:46 -04:00
f13cd071c0 Update makefile to reduce noise in output dir
Add notice of published artifact paths
2022-05-02 17:22:31 -04:00
97cb5388db Add scaffolding for coverletters 2022-05-01 19:14:02 -04:00
6881580482 Add link to published document in readme 2022-04-05 00:21:28 -04:00
1fa031cd04 Proofread and reorganize skills section 2022-04-04 00:35:36 -04:00
50b888ca24 Fix duplicate class file when symlink was intended 2022-03-29 18:42:34 -04:00
ccb8cb4acc Run precommit on all files 2022-03-29 18:40:43 -04:00
273482b745 Add precommit 2022-03-29 18:40:28 -04:00
17d22dcc05 Add initial resume content, ported from old format 2022-03-29 18:36:12 -04:00
7936644c94 Add initial content and doc structure adapted from awesome-cv 2022-03-26 15:19:50 -04:00
c657fd2673 Add build tooling and dependency docs 2022-03-26 15:08:49 -04:00
a292d50ab4 Symlink awesome-cv compoents into top-level 2022-03-26 15:08:11 -04:00
7d874384fa Add Awesome-CV as dependency submodule
Add gitignore for excluding build files
2022-03-26 15:07:27 -04:00
15 changed files with 637 additions and 0 deletions

18
.gitignore vendored Normal file
View File

@@ -0,0 +1,18 @@
### TeX ###
## Core latex/pdflatex auxiliary files:
*.aux
*.lof
*.log
*.lot
*.fls
*.out
*.toc
## Intermediate documents:
*.dvi
*-converted-to.*
## Output
*.pdf
publish/
build/

3
.gitmodules vendored Normal file
View File

@@ -0,0 +1,3 @@
[submodule "Awesome-CV"]
path = Awesome-CV
url = https://github.com/posquit0/Awesome-CV.git

16
.pre-commit-config.yaml Normal file
View File

@@ -0,0 +1,16 @@
---
repos:
- repo: https://github.com/pre-commit/pre-commit-hooks
rev: v4.1.0
hooks:
- id: end-of-file-fixer
types:
- text
- id: trailing-whitespace
types:
- text
- id: check-merge-conflict
types:
- text

1
Awesome-CV Submodule

Submodule Awesome-CV added at bdd64051f1

33
Makefile Normal file
View File

@@ -0,0 +1,33 @@
# personal resume makefile
LETTERS = $(shell command ls letters/*.tex -1 | sed 's/letters\///' | sed 's/.tex//')
.PHONY: help
# Put it first so that "make" without argument is like "make help"
# Adapted from:
# https://marmelab.com/blog/2016/02/29/auto-documented-makefile.html
help: ## List Makefile targets
$(info Makefile documentation)
@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-10s\033[0m %s\n", $$1, $$2}'
clean: ## Clean up temp resources
rm --recursive --force publish/
rm --recursive --force build/
rm --force Awesome-CV/*.log
resume: ## Build the resume PDF
@mkdir --parents publish/
@mkdir --parents build/
@xelatex -output-directory=build/ resume.tex content/
@mv build/resume.pdf publish/resume.pdf
@echo Publishable build artifact written to publish/resume.pdf
$(LETTERS):
@mkdir --parents publish/
@mkdir --parents build/
@cp letters/$@.tex build/coverletter-content.tex
@xelatex -output-directory=build/ coverletter.tex build/
@mv build/coverletter.pdf publish/$@.pdf
@echo Publishable build artifact written to publish/$@.pdf
letters: $(LETTERS); ## Build all cover letters, or use <letter name> to build a specific letter

View File

@@ -4,3 +4,19 @@
This work is licensed under a
[Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License](https://creativecommons.org/licenses/by-nc-nd/4.0/).
View the published version of this document at the permalink [here](https://cdn.enp.one/resume.pdf).
## System requirements (Fedora):
- `tetex`
- `texlive-fontawesome5`
- `texlive-sourcesanspro`
## System requirements (Ubuntu):
- `texlive`
- `texlive-fonts-extra`
- `texlive-xelatex`
*After cloning, be certain to initialize the git submodules.*

1
awesome-cv.cls Symbolic link
View File

@@ -0,0 +1 @@
Awesome-CV/awesome-cv.cls

27
content/education.tex Normal file
View File

@@ -0,0 +1,27 @@
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Education}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Bachelor of Science in Mechanical Engineering / Minor in Business Administration} % Degree
{Worcester Polytechnic Institute} % Institution
{Worcester MA, United States} % Location
{Class of 2017} % Date(s)
{
% \begin{cvitems} % Description(s) bullet points
% \item {Minor in Business Administration}
% \end{cvitems}
}
\vspace{-4mm} % needed while no bullet points under education
%---------------------------------------------------------
\end{cventries}

139
content/experience.tex Normal file
View File

@@ -0,0 +1,139 @@
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Experience}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cventries}
%---------------------------------------------------------
\cventry
{Portal Instruments Inc. - Information Technology} % Job title
{Principal Information Technology and Security Engineer} % Organization
{Cambridge MA, United States} % Location
{August 2022 - Present} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {
Audit and consolidate IT resource management into a single
department to reduce duplicate spending and improve day-to-day
employee workflows. Create a budget and ordering process for IT resources.
}
\item {
Operate as a single IT administrator to manage resources at all levels
and in all areas of the business, including facility infrastructure,
cloud resources, licensing, physical and virtual servers, and employee
workstations.
}
\item {
Provide daily support for the entire organization across four timezones.
Support Windows, MacOS, and Linux workstations, enterprise resource
management, access control, and security incidents.
}
\item {
Designed and implemented a top-to-bottom replacement of core network
infrastructure including virtual private clouds, on-site network equipment,
and virtual private networking.
}
\item {
Offboard and assume responsibilities of existing Managed
Service Provider and manage relationships with IT vendors
as the primary point of contact.
}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Starry Inc. - Product Engineering} % Job title
{Systems Administrator / Development Operations Engineer} % Organization
{Boston MA, United States} % Location
{June 2018 - August 2022} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {
Took ownership of a Network Monitoring System built specifically for
Starry's WISP network model, expanding and developing the system to meet
the needs of the Network Operations team and handle a thirty-fold workload
increase.
}
\item {
Provided 24/7 support for the NMS to ensure uninterrupted access
to alerts, data, and performance reports for the Tier 2 Support team and
executive leadership.
}
\item {
Designed and deployed a testbed management network using off-the-shelf
routing equipment and Ansible that connected engineering systems at all
eleven corporate offices across the country.
}
\item {
Helped lead a team developing Ansible automation for managing and
securing hundreds of physical engineering systems across four departments.
}
%\item {
% Contributed to the design, implementation, and operation of a REST API for
% indexing test results to serve the needs of multiple test teams.
%}
\item {
Facilitated inter-operation between the Manufacturing Division and
Product Engineering to support expanded access to internal technology,
increased awareness of documentation and knowledge resources, and greater
cross-team communication.
}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Worcester Polytechnic Institute - Network Operations Center} % Job title
{Senior Network Technician} % Organization
{Worcester MA, United States} % Location
{August 2013 - June 2018} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
% \item {
% Acted as first point of contact for users experiencing networking issues to
% triage problems and escalate to network engineers when appropriate.
% }
\item {
Assisted with regular maintenance of the three campus data centers, including
replacing faulty PDUs, organizing and documenting routed cables, and retirement of
network and server hardware.
}
\item {
Planned and developed campus-wide documentation of network conduit to
provide the Network Operations and Telecommunication departments with better
information sources when triaging problems, performing maintenance work, and
planning expansions.
}
\end{cvitems}
}
%---------------------------------------------------------
\cventry
{Dassault Systèmes S.E. - SOLIDWORKS User Experience} % Job title
{Contract Technical Writer} % Organization
{Waltham MA, United States} % Location
{May 2015 - January 2016} % Date(s)
{
\begin{cvitems} % Description(s) of tasks/responsibilities
\item {
Tested official product tutorials for compliance with user workflows in
SOLIDWORKS 2016 and updated the tutorials if they were outdated.
}
\item {
Designed and wrote new tutorials for the newly implemented advanced
electrical and pipe routing tools added to SOLIDWORKS 2016.
}
% \item {
% Responded to and fixed user submitted bug reports concerning errors,
% mistakes, or ambiguity in the official product documentation.
% }
\end{cvitems}
}
\end{cventries}

62
content/skills.tex Normal file
View File

@@ -0,0 +1,62 @@
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Skills}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvskills}
\cvskill{Interpersonal}{
Cross-team communication,
specification design and evaulation,
problem analysis,
incident triage,
security threat modeling
}
\cvskill{Operations}{
Ansible,
OAuth,
L2/L3 Routing,
DNS,
DHCP,
Containers,
Nginx,
Apache,
MySQL/MariaDB,
MongoDB,
OpenSSH,
CI/CD
}
\cvskill{Administration}{
Windows Server,
Debian/RHEL Server,
Active Directory,
LDAP,
Microsoft Hyper-V,
KVM,
VMWare ESXi,
Google Workspace,
Microsoft O365
}
\cvskill{Software}{
Python,
Bash,
TypeScript,
SQL,
HTML,
CSS,
Git,
Ansible,
GNU Make,
Terraform,
PHP,
PowerShell,
Docker Swarm,
GlusterFS
}
\end{cvskills}

20
content/summary.tex Normal file
View File

@@ -0,0 +1,20 @@
%-------------------------------------------------------------------------------
% SECTION TITLE
%-------------------------------------------------------------------------------
\cvsection{Summary}
%-------------------------------------------------------------------------------
% CONTENT
%-------------------------------------------------------------------------------
\begin{cvparagraph}
Computer engineer and system administrator with experience designing and
operating a diverse set of digital infrastructure, including data center
equipment, core and edge networks, multi-cloud environments, end-user devices,
and SaaS products. Proven ability to work independently or collaboratively to
build effective solutions to engineering challenges with respect to business and
technical requirements. Strong dedication to quality, knowledge sharing,
collaboration, documentation, digital security, and public service.
\end{cvparagraph}

110
coverletter.tex Normal file
View File

@@ -0,0 +1,110 @@
%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode
% Awesome CV LaTeX Template for Cover Letter
%
% This template has been downloaded from:
% https://github.com/posquit0/Awesome-CV
%
% Authors:
% Claud D. Park <posquit0.bj@gmail.com>
% Lars Richter <mail@ayeks.de>
%
% Template license:
% CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/)
%
%-------------------------------------------------------------------------------
% CONFIGURATIONS
%-------------------------------------------------------------------------------
% A4 paper size by default, use 'letterpaper' for US letter
\documentclass[11pt, letterpaper]{awesome-cv}
% Configure page margins with geometry
\geometry{left=1.4cm, top=.8cm, right=1.4cm, bottom=1.8cm, footskip=.5cm}
% Color for highlights
% Awesome Colors: awesome-emerald, awesome-skyblue, awesome-red, awesome-pink, awesome-orange
% awesome-nephritis, awesome-concrete, awesome-darknight
\colorlet{awesome}{awesome-darknight}
% Uncomment if you would like to specify your own color
% \definecolor{awesome}{HTML}{CA63A8}
% 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{sectiondivider}{HTML}{5D5D5D}
% Set false if you don't want to highlight section with awesome color
\setbool{acvSectionColorHighlight}{false}
% If you would like to change the social information separator from a pipe (|) to something else
\renewcommand{\acvHeaderSocialSep}{\enskip\cdotp\enskip}
\newcommand*{\letterbody}[1]{\def\@letterbody{#1}}
% This file doesn't actually exist in the repo, but will be created by the
% makefile
\input{build/coverletter-content.tex}
%-------------------------------------------------------------------------------
% PERSONAL INFORMATION
% Comment any of the lines below if they are not required
%-------------------------------------------------------------------------------
% Available options: circle|rectangle,edge/noedge,left/right
\name{Ethan}{Paul}
%\position{Systems Administrator / Development Operations Engineer}
\mobile{+1.617.733.0601}
\email{me@enp.one}
%\dateofbirth{January 1st, 1970}
%\homepage{enpaul.net}
%\github{posquit0}
%\linkedin{posquit0}
% \gitlab{gitlab-id}
% \stackoverflow{SO-id}{SO-name}
% \twitter{@twit}
% \skype{skype-id}
% \reddit{reddit-id}
% \medium{madium-id}
% \kaggle{kaggle-id}
% \googlescholar{googlescholar-id}{name-to-display}
%% \firstname and \lastname will be used
% \googlescholar{googlescholar-id}{}
% \extrainfo{extra information}
% How the letter is closed
\letterclosing{\recipientaddressstyle{Ethan Paul\\13 Faxon St\\Newton, MA 02458\\USA}}
% Any enclosures with the letter
%\letterenclosure[Attached]{Resume}
%-------------------------------------------------------------------------------
\begin{document}
% Print the footer with 3 arguments(<left>, <center>, <right>)
% Leave any of these blank if they are not needed
\makecvfooter
{\today}
{}
{\href{https://creativecommons.org/licenses/by-nc-nd/4.0/}{CC BY-NC-ND 4.0}}
% Print the title with above letter information
\makelettertitle
%-------------------------------------------------------------------------------
% LETTER CONTENT
%-------------------------------------------------------------------------------
\begin{cvletter}
\@letterbody
\end{cvletter}
%-------------------------------------------------------------------------------
% Print the signature and enclosures with above letter information
\makeletterclosing
\end{document}

1
fonts Symbolic link
View File

@@ -0,0 +1 @@
Awesome-CV/fonts/

View File

@@ -0,0 +1,63 @@
%-------------------------------------------------------------------------------
% LETTER INFORMATION
% All of the below lines must be filled out
%-------------------------------------------------------------------------------
% The company being applied to
\recipient
{}
{Freedom of the Press Foundation\\601 Van Ness Ave. Suite E731\\San Francisco, CA 94102\\USA}
% The date on the letter, default is the date of compilation
\letterdate{\today}
% How the letter is opened
\letteropening{To the Hiring Manager,}
\letterbody{
My name is Ethan Paul and I am writing to apply for the Newsroom Support Engineer position
at the Freedom of the Press Foundation (FPF). In my nine years of professional experience I
have worked in a wide variety of positions including as a Tier I support technician for a
legacy institution that supported thousands of clients, and a systems architect and
administrator for a small startup company. Through my entire career what I have enjoyed most
from my work are the opportunities to meet people, understand their technical challenges,
and work to build and deliver solutions that help them to be more successful in their jobs.
While I enjoy solving technical problems, it is the relationship between technology and
people that has always been of greatest interest to me.
\\\\
Developing this relationship is the work that the FPF provides through the maintenance and
support of projects like SecureDrop, which demonstrates an ideal model of a distributed open
source software platform. The relationship between people and technology is so
often a complicated one that grows more so as systems become ever more sophisticated and
stratified. As a result of this sophistication, taking advantage of technological
benefits becomes increasingly difficult as the level of expertise required to work within a
system also increases. This makes the work of specialist groups all the more important:
organizations like the FPF provide the essential service of helping people better participate
in our rapidly digitizing world. The FPF and similar organizations also stand in stark
contrast to companies that ostensibly provide the same service, but only for their own
benefit rather than that of their clients, customers, and community. The commitment to
providing enhanced access to technological resources for the principle benefit of its clients
and community is what appeals most to me about applying to join the team at FPF.
\\\\
One of the most interesting and fulfilling projects I have had the opportunity to work on
during my time in the technology sector was the implementation and support of a network
monitoring system for my company's wireless network infrastructure. This project allowed me
to work with and learn from experts in different fields as I coordinated the system's design
across several engineering departments while continually working with the Network
Operations teams to understand how they needed the system to function in daily use. While the
technical work for the project was interesting, by far the most engaging part of the process
was understanding the needs and limitations of the people using the system so that I could
work to improve its utility. This exposure to other teams and specialties helped me to develop
a better understanding of the business, a plethora of diverse relationships, and gave me more
opportunities to expand my technical knowledge.
\\\\
At this point in my career I am interested in the impact my work has on my community and
environment which is why I have chosen to branch out of the traditional technology sector.
I value contributing positively to my organization's culture and clients, but doing so
while also working to fight inequity and improve free access to information is a dream
opportunity for me. I have admired the FPF's work from a far for long enough that the
prospect of applying to work here seems almost surreal. And yet the Newsroom Support
Engineer role combines two elements that are very important to me: developing people's
relationship with their technology, and promoting digital freedom for people everywhere. For
all these reasons I hope you will consider me for the position and I look forward to hearing
from you soon.
}

127
resume.tex Normal file
View File

@@ -0,0 +1,127 @@
%!TEX TS-program = xelatex
%!TEX encoding = UTF-8 Unicode
% Awesome CV LaTeX Template for CV/Resume
%
% This template has been downloaded from:
% https://github.com/posquit0/Awesome-CV
%
% Author:
% Claud D. Park <posquit0.bj@gmail.com>
% http://www.posquit0.com
%
% Template license:
% CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/)
%
%-------------------------------------------------------------------------------
% CONFIGURATIONS
%-------------------------------------------------------------------------------
% A4 paper size by default, use 'letterpaper' for US letter
\documentclass[11pt, letterpaper]{awesome-cv}
% Configure page margins with geometry
\geometry{left=1.2cm, top=.8cm, right=1.2cm, bottom=1.8cm, footskip=.5cm}
% Specify the location of the included fonts
\fontdir[fonts/]
% Color for highlights
% Awesome Colors: awesome-emerald, awesome-skyblue, awesome-red, awesome-pink, awesome-orange
% awesome-nephritis, awesome-concrete, awesome-darknight
\colorlet{awesome}{awesome-darknight}
% Uncomment if you would like to specify your own color
% \definecolor{awesome}{HTML}{CA63A8}
% 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}
% Set false if you don't want to highlight section with awesome color
\setbool{acvSectionColorHighlight}{false}
% If you would like to change the social information separator from a pipe (|) to something else
\renewcommand{\acvHeaderSocialSep}{\enskip\cdotp\enskip}
% Custom settings to tighten up the formatting and conserve space while making it more readable
\renewcommand{\acvSectionTopSkip}{0mm}
\renewcommand{\acvSectionContentTopSkip}{1.5mm}
% Kind of frustrating, but needed to overwrite this whole environment just to change the
% list item separation
\renewenvironment{cvitems}{
\vspace{-4.0mm}
\begin{justify}
\begin{itemize}[leftmargin=2ex, nosep, itemsep=3pt]
\setlength{\parskip}{0pt}
\renewcommand{\labelitemi}{\bullet}
}{
\end{itemize}
\end{justify}
\vspace{-4.0mm}
}
%-------------------------------------------------------------------------------
% PERSONAL INFORMATION
% Comment any of the lines below if they are not required
%-------------------------------------------------------------------------------
% Available options: circle|rectangle,edge/noedge,left/right
% \photo[rectangle,edge,right]{./examples/profile}
\name{Ethan}{Paul}
\position{
Systems Administrator
{\enskip\cdotp\enskip}
Information Technology
{\enskip\cdotp\enskip}
Software Engineer
}
% \address{Boston MA, United States}
\mobile{+1 (617) 733-0601}
\email{me@enpaul.net}
\homepage{enpaul.net}
\github{enpaul}
\linkedin{enpaul}
% \gitlab{gitlab-id}
% \stackoverflow{SO-id}{SO-name}
% \twitter{@twit}
% \skype{skype-id}
% \reddit{reddit-id}
% \medium{madium-id}
% \googlescholar{googlescholar-id}{name-to-display}
%% \firstname and \lastname will be used
% \googlescholar{googlescholar-id}{}
% \extrainfo{extra informations}
% \quote{``Be the change that you want to see in the world."}
%-------------------------------------------------------------------------------
\begin{document}
% Print the header with above personal informations
% Give optional argument to change alignment(C: center, L: left, R: right)
\makecvheader[C]
% Print the footer with 3 arguments(<left>, <center>, <right>)
% Leave any of these blank if they are not needed
\makecvfooter
{\today}
{}
{\href{https://creativecommons.org/licenses/by-nc-nd/4.0/}{CC BY-NC-ND 4.0}}
%-------------------------------------------------------------------------------
% CV/RESUME CONTENT
% Each section is imported separately, open each file in turn to modify content
%-------------------------------------------------------------------------------
\input{content/summary.tex}
\input{content/education.tex}
\input{content/experience.tex}
\input{content/skills.tex}
%-------------------------------------------------------------------------------
\end{document}