Compare commits
35 Commits
b4b5a74e80
...
2024-05/fr
| Author | SHA1 | Date | |
|---|---|---|---|
|
680d864aa9
|
|||
|
cd5076922a
|
|||
|
7081b174da
|
|||
|
efa0f0760f
|
|||
|
e349dc89bb
|
|||
|
3964c315df
|
|||
|
9dffb95070
|
|||
|
52871bdf71
|
|||
|
b080d4af53
|
|||
|
b4a9e73113
|
|||
|
64aab159fa
|
|||
|
8bdcf88fdc
|
|||
|
276c709e15
|
|||
|
2e08eab36c
|
|||
|
a5768cdb0a
|
|||
|
f146b4b097
|
|||
|
5a636bb9aa
|
|||
|
88a7198f3a
|
|||
|
6a3676e53d
|
|||
|
22675b8d45
|
|||
| 03353d85ad | |||
| 371d7e8d27 | |||
| 43b8a31053 | |||
| f13cd071c0 | |||
| 97cb5388db | |||
| 6881580482 | |||
| 1fa031cd04 | |||
| 50b888ca24 | |||
| ccb8cb4acc | |||
| 273482b745 | |||
| 17d22dcc05 | |||
| 7936644c94 | |||
| c657fd2673 | |||
| a292d50ab4 | |||
| 7d874384fa |
18
.gitignore
vendored
Normal file
18
.gitignore
vendored
Normal 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
3
.gitmodules
vendored
Normal 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
16
.pre-commit-config.yaml
Normal 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
1
Awesome-CV
Submodule
Submodule Awesome-CV added at bdd64051f1
33
Makefile
Normal file
33
Makefile
Normal 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
|
||||||
16
README.md
16
README.md
@@ -4,3 +4,19 @@
|
|||||||
|
|
||||||
This work is licensed under a
|
This work is licensed under a
|
||||||
[Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License](https://creativecommons.org/licenses/by-nc-nd/4.0/).
|
[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
1
awesome-cv.cls
Symbolic link
@@ -0,0 +1 @@
|
|||||||
|
Awesome-CV/awesome-cv.cls
|
||||||
27
content/education.tex
Normal file
27
content/education.tex
Normal 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}
|
||||||
180
content/experience.tex
Normal file
180
content/experience.tex
Normal file
@@ -0,0 +1,180 @@
|
|||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
% SECTION TITLE
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
\cvsection{Experience}
|
||||||
|
|
||||||
|
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
% CONTENT
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
\begin{cventries}
|
||||||
|
|
||||||
|
%---------------------------------------------------------
|
||||||
|
\cventry
|
||||||
|
{Portal Instruments Inc. - Information Technology} % Company + department
|
||||||
|
{Principal Information Technology and Security Engineer} % Job title
|
||||||
|
{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 {
|
||||||
|
Identify information security vulnerabilities in the company's digital
|
||||||
|
infrastructure and develop a prioritization plan for corrective actions.
|
||||||
|
Communicate these security gaps to company leadership, then propose and
|
||||||
|
implement mitigations in accordance with the needs and priorities of
|
||||||
|
the business.
|
||||||
|
}
|
||||||
|
% \item {
|
||||||
|
% Advise the Software Engineering department on security requirements and best
|
||||||
|
% practices as part of the company's digital health initiative and expansion into
|
||||||
|
% cloud service offerings. Educate employees at all levels on security
|
||||||
|
% best practices and help foster a collaboratively vigilant security culture.
|
||||||
|
% }
|
||||||
|
\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} % Company + department
|
||||||
|
{Systems Administrator / Development Operations Engineer} % Job title
|
||||||
|
{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} % Company + department
|
||||||
|
{Senior Network Technician} % Job title
|
||||||
|
{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} % Company + department
|
||||||
|
{Contract Development Operations Specialist} % Job title
|
||||||
|
{Waltham MA, United States} % Location
|
||||||
|
{May 2016 - August 2017} % Date(s)
|
||||||
|
{
|
||||||
|
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||||
|
\item {
|
||||||
|
Worked as a software specialist on a Graphics Design team to take over
|
||||||
|
maintenance of a custom-built image asset lifecycle management tool and
|
||||||
|
design its replacement.
|
||||||
|
}
|
||||||
|
\item {
|
||||||
|
Designed and implemented a web application stack using PHP, JQuery, and
|
||||||
|
MySQL to provide a web portal for internal clients to request new assets
|
||||||
|
from the graphics design team, provide feedback and iteration on asset
|
||||||
|
requests, and serve as the internal source of truth for finalized assets.
|
||||||
|
}
|
||||||
|
% \item {
|
||||||
|
% Designed the final deployment infrastructure using Windows Server 2012,
|
||||||
|
% IIS 8.5, and MySQL Server, then communicated these requirements to the
|
||||||
|
% IT department for implementation.
|
||||||
|
% }
|
||||||
|
\end{cvitems}
|
||||||
|
}
|
||||||
|
|
||||||
|
|
||||||
|
%---------------------------------------------------------
|
||||||
|
% \cventry
|
||||||
|
% {Dassault Systèmes S.E. - SOLIDWORKS User Experience} % Company + department
|
||||||
|
% {Contract Technical Writer} % Job title
|
||||||
|
% {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}
|
||||||
61
content/skills.tex
Normal file
61
content/skills.tex
Normal file
@@ -0,0 +1,61 @@
|
|||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
% SECTION TITLE
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
\cvsection{Skills}
|
||||||
|
|
||||||
|
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
% CONTENT
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
\begin{cvskills}
|
||||||
|
\cvskill{Interpersonal}{
|
||||||
|
interdisciplinary communication,
|
||||||
|
specification design and evaulation,
|
||||||
|
technical writing and documentation,
|
||||||
|
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
20
content/summary.tex
Normal 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
110
coverletter.tex
Normal 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@enpaul.net}
|
||||||
|
%\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\\218 Thorndike Street Unit \#101\\Cambridge, MA 02141\\U.S.A.}}
|
||||||
|
% 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}
|
||||||
63
letters/freedom_of_the_press.tex
Normal file
63
letters/freedom_of_the_press.tex
Normal 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.
|
||||||
|
}
|
||||||
64
letters/freedom_of_the_press_2.tex
Normal file
64
letters/freedom_of_the_press_2.tex
Normal file
@@ -0,0 +1,64 @@
|
|||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
% LETTER INFORMATION
|
||||||
|
% All of the below lines must be filled out
|
||||||
|
%-------------------------------------------------------------------------------
|
||||||
|
% The company being applied to
|
||||||
|
\recipient
|
||||||
|
{}
|
||||||
|
{Freedom of the Press Foundation\\49 Flatbush Avenue \#1017\\Brooklyn, NY 11217\\U.S.A.}
|
||||||
|
|
||||||
|
% The date on the letter, default is the date of compilation
|
||||||
|
\letterdate{\today}
|
||||||
|
|
||||||
|
% How the letter is opened
|
||||||
|
\letteropening{To the Infrastructure Team,}
|
||||||
|
|
||||||
|
\letterbody{
|
||||||
|
My name is Ethan Paul and I am interested in working in a position on the Infrastructure
|
||||||
|
Team at the Freedom of the Press Foundation (FPF). In my eleven 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, a systems
|
||||||
|
architect and administrator for an internet service provider, and a single-member IT team
|
||||||
|
for a small startup company. Throughout my 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.
|
||||||
|
\\\\
|
||||||
|
Projects like SecureDrop and the Press Freedom Tracker exist at this intersection where
|
||||||
|
technology and people collide. This intersection- ideally beneficial but too often
|
||||||
|
confounding or exploitative- is already quite difficult to navigate for many people and, as
|
||||||
|
technology continues to evolve, will only demand ever higher amounts of technical knowledge
|
||||||
|
to properly manage. 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 continually digitizing world by making technology and technical resources
|
||||||
|
more accessible and navigable. 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 principal benefit of its
|
||||||
|
clients and community is what appeals most to me about joining 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, build a plethora of diverse relationships, and gave me
|
||||||
|
more opportunities to expand my technical knowledge than I ever would have found working
|
||||||
|
alone.
|
||||||
|
\\\\
|
||||||
|
After eight years in the technology sector I am fortunate enough to have the flexibility to
|
||||||
|
shift my career path away from technology for technology's sake and towards technology for
|
||||||
|
the sake of people. Working in an environment where I can make contributions to complex
|
||||||
|
technical systems, learn from experts in a diverse set of fields, and have the
|
||||||
|
confidence that my work helps to fight inequality and improve free access to information is
|
||||||
|
a dream opportunity. I have admired the FPF's work from afar for long enough that the
|
||||||
|
prospect of working with the FPF feels almost surreal. And yet the Infrastructure Team
|
||||||
|
combines two elements that are very important to me: improving people's relationship with
|
||||||
|
their technology and promoting digital freedom for people everywhere. For all these reasons
|
||||||
|
I hope you will consider me for a position and I look forward to hearing from you soon.
|
||||||
|
}
|
||||||
127
resume.tex
Normal file
127
resume.tex
Normal 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{
|
||||||
|
System Administrator
|
||||||
|
{\enskip\cdotp\enskip}
|
||||||
|
Information Technology \& Security
|
||||||
|
{\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}
|
||||||
Reference in New Issue
Block a user