Compare commits
17 Commits
2022-05/fr
...
2024-04/mb
Author | SHA1 | Date | |
---|---|---|---|
efa0f0760f
|
|||
e349dc89bb
|
|||
3964c315df
|
|||
9dffb95070
|
|||
52871bdf71
|
|||
b080d4af53
|
|||
b4a9e73113
|
|||
64aab159fa
|
|||
8bdcf88fdc
|
|||
276c709e15
|
|||
2e08eab36c
|
|||
a5768cdb0a
|
|||
f146b4b097
|
|||
5a636bb9aa
|
|||
88a7198f3a
|
|||
6a3676e53d
|
|||
22675b8d45
|
@@ -13,4 +13,10 @@ View the published version of this document at the permalink [here](https://cdn.
|
||||
- `texlive-fontawesome5`
|
||||
- `texlive-sourcesanspro`
|
||||
|
||||
After cloning, be certain to initialize the git submodules.
|
||||
## System requirements (Ubuntu):
|
||||
|
||||
- `texlive`
|
||||
- `texlive-fonts-extra`
|
||||
- `texlive-xelatex`
|
||||
|
||||
*After cloning, be certain to initialize the git submodules.*
|
||||
|
@@ -11,15 +11,17 @@
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Bachelor of Science in Mechanical Engineering / Minor in Business Administration} % Degree
|
||||
{Worcester Polytechnic Institute} % Institution
|
||||
{Bachelor of Science in Mechanical Engineering} % Degree
|
||||
{Worcester MA, United States} % Location
|
||||
{Class of 2017} % Date(s)
|
||||
{
|
||||
\begin{cvitems} % Description(s) bullet points
|
||||
\item {Minor in Business Administration}
|
||||
\end{cvitems}
|
||||
% \begin{cvitems} % Description(s) bullet points
|
||||
% \item {Minor in Business Administration}
|
||||
% \end{cvitems}
|
||||
}
|
||||
|
||||
\vspace{-4mm} % needed while no bullet points under education
|
||||
|
||||
%---------------------------------------------------------
|
||||
\end{cventries}
|
||||
|
@@ -11,33 +11,75 @@
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Systems Administrator / Development Operations Engineer} % Job title
|
||||
{Starry Inc - Product Engineering} % Organization
|
||||
{Boston MA, United States} % Location
|
||||
{June 2018 - Present} % Date(s)
|
||||
{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 {
|
||||
Took ownership of a network monitoring system built specifically for
|
||||
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 {
|
||||
Designed and deployed a testbed management network using Ubiquiti
|
||||
EdgeRouters and Ansible that connected engineering equipment at all
|
||||
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 to lead a team developing Ansible automation for managing and
|
||||
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 {
|
||||
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 interoperation between the Manufacturing Division and
|
||||
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.
|
||||
@@ -47,87 +89,50 @@
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Development Operations Contractor} % Job title
|
||||
{Dassault Systèmes SE - SOLIDWORKS User Experience} % Organization
|
||||
{Waltham MA, United States} % Location
|
||||
{May 2016 - August 2017} % Date(s)
|
||||
{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 {
|
||||
Worked as a software specialist on a Graphics Design team to replace
|
||||
an existing unsupported image asset lifecycle management tool.
|
||||
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 {
|
||||
Designed and implemented a web application stack using PHP, JQuery, and
|
||||
MySQL to provide a web portal for internal clients to request new images
|
||||
from the graphics design team, provide feedback and iteration on image
|
||||
requests, and serve as the source of truth for finalized image assets.
|
||||
}
|
||||
\item {
|
||||
Designed and implemented a MySQL database schema to store metadata about
|
||||
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 worked with the IT deparment to implement
|
||||
these requirements.
|
||||
}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
\cventry
|
||||
{Technical Writing Contractor} % Job title
|
||||
{} % Organization
|
||||
{} % 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 where 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.
|
||||
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
|
||||
{Senior Network Technician} % Job title
|
||||
{Worcester Polytechnic Institute - Network Operations} % Organization
|
||||
{Worcester MA, United States} % Location
|
||||
{August 2013 - June 2018} % Date(s)
|
||||
{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 {
|
||||
Developed procedures for technicians to follow when debugging WPA certificate
|
||||
authentication on Windows, Android, iPhone, and Ubuntu systems.
|
||||
Tested official product tutorials for compliance with user workflows in
|
||||
SOLIDWORKS 2016 and updated the tutorials if they were outdated.
|
||||
}
|
||||
\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 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.
|
||||
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}
|
||||
}
|
||||
|
||||
|
@@ -12,7 +12,7 @@
|
||||
Cross-team communication,
|
||||
specification design and evaulation,
|
||||
problem analysis,
|
||||
remote triage and debug,
|
||||
incident triage,
|
||||
security threat modeling
|
||||
}
|
||||
|
||||
@@ -22,44 +22,41 @@
|
||||
L2/L3 Routing,
|
||||
DNS,
|
||||
DHCP,
|
||||
Docker,
|
||||
Microsoft IIS,
|
||||
Containers,
|
||||
Nginx,
|
||||
Apache,
|
||||
MySQL/MariaDB,
|
||||
MongoDB,
|
||||
Postgres,
|
||||
OpenSSH
|
||||
OpenSSH,
|
||||
CI/CD
|
||||
}
|
||||
|
||||
\cvskill{Administration}{
|
||||
Windows Server,
|
||||
Ubuntu Server,
|
||||
CentOS/RockyLinux,
|
||||
Microsoft ADDS,
|
||||
OpenLDAP,
|
||||
Debian/RHEL Server,
|
||||
Active Directory,
|
||||
LDAP,
|
||||
Microsoft Hyper-V,
|
||||
KVM,
|
||||
RedHat Ovirt,
|
||||
VMWare ESXi,
|
||||
Google Workspace,
|
||||
Microsoft O365
|
||||
}
|
||||
|
||||
\cvskill{Software}{
|
||||
Python3,
|
||||
Tox,
|
||||
Poetry,
|
||||
Pylint,
|
||||
MyPy,
|
||||
Python,
|
||||
Bash,
|
||||
TypeScript,
|
||||
SQL,
|
||||
HTML,
|
||||
CSS,
|
||||
Bash,
|
||||
Git,
|
||||
Gitea,
|
||||
Gitlab,
|
||||
Github,
|
||||
CI/CD,
|
||||
Jenkins,
|
||||
Ansible,
|
||||
GNU Make
|
||||
GNU Make,
|
||||
Terraform,
|
||||
PHP,
|
||||
PowerShell,
|
||||
Docker Swarm,
|
||||
GlusterFS
|
||||
}
|
||||
\end{cvskills}
|
||||
|
@@ -1,7 +1,7 @@
|
||||
%-------------------------------------------------------------------------------
|
||||
% SECTION TITLE
|
||||
%-------------------------------------------------------------------------------
|
||||
\cvsection{Introduction}
|
||||
\cvsection{Summary}
|
||||
|
||||
|
||||
%-------------------------------------------------------------------------------
|
||||
@@ -9,9 +9,12 @@
|
||||
%-------------------------------------------------------------------------------
|
||||
\begin{cvparagraph}
|
||||
|
||||
%---------------------------------------------------------
|
||||
Current Linux Systems Administrator and Development Operations Engineer at
|
||||
Starry Inc looking for opportunities in Development Operations, Site
|
||||
Reliability Engineering, or Technical Support at socially conscious
|
||||
companies and organizations.
|
||||
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}
|
||||
|
12
resume.tex
12
resume.tex
@@ -74,14 +74,14 @@
|
||||
\position{
|
||||
Systems Administrator
|
||||
{\enskip\cdotp\enskip}
|
||||
Development Operations Engineer
|
||||
Information Technology
|
||||
{\enskip\cdotp\enskip}
|
||||
Software Engineer
|
||||
}
|
||||
% \address{Boston MA, United States}
|
||||
|
||||
% \mobile{}
|
||||
\email{me@enp.one}
|
||||
\mobile{+1 (617) 733-0601}
|
||||
\email{me@enpaul.net}
|
||||
\homepage{enpaul.net}
|
||||
\github{enpaul}
|
||||
\linkedin{enpaul}
|
||||
@@ -122,12 +122,6 @@
|
||||
\input{content/education.tex}
|
||||
\input{content/experience.tex}
|
||||
\input{content/skills.tex}
|
||||
% \input{content/honors.tex}
|
||||
% \input{content/presentation.tex}
|
||||
% \input{content/writing.tex}
|
||||
% \input{content/committees.tex}
|
||||
% \input{content/extracurricular.tex}
|
||||
|
||||
|
||||
%-------------------------------------------------------------------------------
|
||||
\end{document}
|
||||
|
Reference in New Issue
Block a user