Compare commits
5 Commits
2022-05/di
...
2022-05/fr
Author | SHA1 | Date | |
---|---|---|---|
03353d85ad | |||
371d7e8d27 | |||
43b8a31053 | |||
f13cd071c0 | |||
97cb5388db |
1
.gitignore
vendored
1
.gitignore
vendored
@@ -15,3 +15,4 @@
|
||||
## Output
|
||||
*.pdf
|
||||
publish/
|
||||
build/
|
||||
|
24
Makefile
24
Makefile
@@ -1,5 +1,7 @@
|
||||
# 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:
|
||||
@@ -10,8 +12,22 @@ help: ## List Makefile targets
|
||||
|
||||
clean: ## Clean up temp resources
|
||||
rm --recursive --force publish/
|
||||
rm Awesome-CV/*.log
|
||||
rm --recursive --force build/
|
||||
rm --force Awesome-CV/*.log
|
||||
|
||||
pdf: ## Build the resume PDF
|
||||
mkdir --parents publish/
|
||||
xelatex -output-directory=publish/ resume.tex content/
|
||||
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
|
||||
|
@@ -19,8 +19,9 @@
|
||||
\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 using
|
||||
Python, Docker, MariaDB, and AWS to handle a thirty-fold workload increase.
|
||||
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 {
|
||||
Designed and deployed a testbed management network using Ubiquiti
|
||||
@@ -28,12 +29,12 @@
|
||||
eleven corporate offices across the country.
|
||||
}
|
||||
\item {
|
||||
Helped to lead a team developing Ansible tooling for managing and
|
||||
securing hundreds of physical engineering systems.
|
||||
Helped to 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 built on Python, Flask, Nginx and MariaDB.
|
||||
indexing test results to serve the needs of multiple test teams.
|
||||
}
|
||||
\item {
|
||||
Facilitated interoperation between the Manufacturing Division and
|
||||
@@ -64,13 +65,12 @@
|
||||
}
|
||||
\item {
|
||||
Designed and implemented a MySQL database schema to store metadata about
|
||||
image assets, as well as the migrations necessary to convert existing legacy
|
||||
data into the new schema layout.
|
||||
image assets to help automate existing workflows on the team.
|
||||
}
|
||||
\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.
|
||||
IIS 8.5, and MySQL Server, then worked with the IT deparment to implement
|
||||
these requirements.
|
||||
}
|
||||
\end{cvitems}
|
||||
}
|
||||
@@ -105,16 +105,6 @@
|
||||
{August 2013 - June 2018} % Date(s)
|
||||
{
|
||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||
\item {
|
||||
Organized and executed preemptive campus-wide testing of ethernet conduit in
|
||||
limited-access facilities to identify and repair faulty infrastructure.
|
||||
}
|
||||
\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, doing maintenance work, and
|
||||
planning expansions.
|
||||
}
|
||||
\item {
|
||||
Developed procedures for technicians to follow when debugging WPA certificate
|
||||
authentication on Windows, Android, iPhone, and Ubuntu systems.
|
||||
@@ -128,6 +118,16 @@
|
||||
replacing faulty PDUs, organizing and documenting routed cables, and retiring
|
||||
network and server hardware.
|
||||
}
|
||||
\item {
|
||||
Organized and executed preemptive campus-wide testing of ethernet conduit in
|
||||
limited-access facilities to identify and repair faulty infrastructure.
|
||||
}
|
||||
\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, doing maintenance work, and
|
||||
planning expansions.
|
||||
}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
|
@@ -12,7 +12,7 @@
|
||||
Cross-team communication,
|
||||
specification design and evaulation,
|
||||
problem analysis,
|
||||
technical support,
|
||||
remote triage and debug,
|
||||
security threat modeling
|
||||
}
|
||||
|
||||
|
@@ -12,6 +12,6 @@
|
||||
%---------------------------------------------------------
|
||||
Current Linux Systems Administrator and Development Operations Engineer at
|
||||
Starry Inc looking for opportunities in Development Operations, Site
|
||||
Reliability Engineering, or Solutions Engineering at socially conscious
|
||||
Reliability Engineering, or Technical Support at socially conscious
|
||||
companies and organizations.
|
||||
\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@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}
|
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.
|
||||
}
|
Reference in New Issue
Block a user