Compare commits
No commits in common. "e349dc89bb2363cf0d296d4b510769649891e590" and "8bdcf88fdcd4dbb2393728c7838568fbb739a504" have entirely different histories.
e349dc89bb
...
8bdcf88fdc
@ -11,17 +11,15 @@
|
||||
|
||||
%---------------------------------------------------------
|
||||
\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,75 +11,68 @@
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Portal Instruments Inc. - Information Technology} % Job title
|
||||
{Principal Information Technology and Security Engineer} % Organization
|
||||
{Principal Information Technology and Security Engineer} % Job title
|
||||
{Portal Instruments Inc. - Information Technology} % Organization
|
||||
{Cambridge MA, United States} % Location
|
||||
{August 2022 - Present} % Date(s)
|
||||
{August 2022 - Present (2 years)} % 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.
|
||||
Audit and consolidate IT resource and asset management into a single
|
||||
business segment to reduce duplicate spending and improve day-to-day
|
||||
employee workflows.
|
||||
}
|
||||
\item {
|
||||
Operate as a single IT administrator to manage resources at all levels
|
||||
and in all areas of the business, including facility infrastructure,
|
||||
Administer IT resources at all levels, 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.
|
||||
Provide daily support for employees across all business segments at every
|
||||
level, including Windows and Mac workstations, enterprise resource managment,
|
||||
access control, and product security reviews.
|
||||
}
|
||||
\item {
|
||||
Designed and implemented a top-to-bottom replacement of core network
|
||||
infrastructure including virtual private clouds, on-site network equipment,
|
||||
Design and implement a top-to-bottom replacement of the core corporate 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.
|
||||
Manage ongoing relationship with existing vendors including the corporate Managed
|
||||
Service Provider partner.
|
||||
}
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Starry Inc. - Product Engineering} % Job title
|
||||
{Systems Administrator / Development Operations Engineer} % Organization
|
||||
{Systems Administrator / Development Operations Engineer} % Job title
|
||||
{Starry Inc. - Product Engineering} % Organization
|
||||
{Boston MA, United States} % Location
|
||||
{June 2018 - August 2022} % Date(s)
|
||||
{June 2018 - August 2022 (4 years)} % Date(s)
|
||||
{
|
||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||
\item {
|
||||
Took ownership of a Network Monitoring System built specifically for
|
||||
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
|
||||
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 to serve the needs of multiple test teams.
|
||||
%}
|
||||
\item {
|
||||
Facilitated inter-operation between the Manufacturing Division and
|
||||
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
|
||||
Product Engineering to support expanded access to internal technology,
|
||||
increased awareness of documentation and knowledge resources, and greater
|
||||
cross-team communication.
|
||||
@ -89,50 +82,50 @@
|
||||
|
||||
%---------------------------------------------------------
|
||||
\cventry
|
||||
{Worcester Polytechnic Institute - Network Operations Center} % Job title
|
||||
{Senior Network Technician} % Organization
|
||||
{Worcester MA, United States} % Location
|
||||
{August 2013 - June 2018} % Date(s)
|
||||
{Technical Writing Contractor} % Job title
|
||||
{Dassault Systèmes S.E. - SOLIDWORKS User Experience} % Organization
|
||||
{Waltham MA, United States} % Location
|
||||
{May 2015 - January 2016 (8 months)} % 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.
|
||||
Tested official product tutorials for compliance with user workflows in
|
||||
SOLIDWORKS 2016 and updated the tutorials where they were outdated.
|
||||
}
|
||||
\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.
|
||||
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}
|
||||
}
|
||||
|
||||
%---------------------------------------------------------
|
||||
\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)
|
||||
{Senior Network Technician} % Job title
|
||||
{Worcester Polytechnic Institute - Network Operations Center} % Organization
|
||||
{Worcester MA, United States} % Location
|
||||
{August 2013 - June 2018 (5 years)} % 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.
|
||||
Acted as first point of contact for users experiencing networking issues to
|
||||
triage problems and escalate to network engineers when appropriate.
|
||||
}
|
||||
\item {
|
||||
Designed and wrote new tutorials for the newly implemented advanced
|
||||
electrical and pipe routing tools added to SOLIDWORKS 2016.
|
||||
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 {
|
||||
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 {
|
||||
% Responded to and fixed user submitted bug reports concerning errors,
|
||||
% mistakes, or ambiguity in the official product documentation.
|
||||
% }
|
||||
\end{cvitems}
|
||||
}
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
%-------------------------------------------------------------------------------
|
||||
% SECTION TITLE
|
||||
%-------------------------------------------------------------------------------
|
||||
\cvsection{Summary}
|
||||
\cvsection{Introduction}
|
||||
|
||||
|
||||
%-------------------------------------------------------------------------------
|
||||
@ -9,12 +9,9 @@
|
||||
%-------------------------------------------------------------------------------
|
||||
\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 on a team 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.
|
||||
|
||||
%---------------------------------------------------------
|
||||
Current Principal Information Technology and Security Engineer at
|
||||
Portal Instruments interested in opportunities in Site Reliability Engineering,
|
||||
System Administration, and Network Engineering at socially concious organizations
|
||||
dedicated to public service, climate resiliancy, and infrastructure management.
|
||||
\end{cvparagraph}
|
||||
|
10
resume.tex
10
resume.tex
@ -80,8 +80,8 @@
|
||||
}
|
||||
% \address{Boston MA, United States}
|
||||
|
||||
\mobile{+1 (617) 733-0601}
|
||||
\email{me@enpaul.net}
|
||||
% \mobile{}
|
||||
\email{me@enp.one}
|
||||
\homepage{enpaul.net}
|
||||
\github{enpaul}
|
||||
\linkedin{enpaul}
|
||||
@ -122,6 +122,12 @@
|
||||
\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}
|
||||
|
Loading…
Reference in New Issue
Block a user