Compare commits
No commits in common. "main" and "2024-04/mbta" have entirely different histories.
main
...
2024-04/mb
@ -9,7 +9,7 @@ View the published version of this document at the permalink [here](https://cdn.
|
|||||||
|
|
||||||
## System requirements (Fedora):
|
## System requirements (Fedora):
|
||||||
|
|
||||||
- `texlive-scheme-tetex`
|
- `tetex`
|
||||||
- `texlive-fontawesome5`
|
- `texlive-fontawesome5`
|
||||||
- `texlive-sourcesanspro`
|
- `texlive-sourcesanspro`
|
||||||
|
|
||||||
|
@ -11,36 +11,23 @@
|
|||||||
|
|
||||||
%---------------------------------------------------------
|
%---------------------------------------------------------
|
||||||
\cventry
|
\cventry
|
||||||
{Portal Instruments Inc. - Information Technology} % Company + department
|
{Portal Instruments Inc. - Information Technology} % Job title
|
||||||
{Principal Information Technology and Security Engineer} % Job title
|
{Principal Information Technology and Security Engineer} % Organization
|
||||||
{Cambridge MA, United States} % Location
|
{Cambridge MA, United States} % Location
|
||||||
{August 2022 - Present} % Date(s)
|
{August 2022 - Present} % Date(s)
|
||||||
{
|
{
|
||||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||||
% \item {
|
\item {
|
||||||
% Audit and consolidate IT resource management into a single
|
Audit and consolidate IT resource management into a single
|
||||||
% department to reduce duplicate spending and improve day-to-day
|
department to reduce duplicate spending and improve day-to-day
|
||||||
% employee workflows. Create a budget and ordering process for IT resources.
|
employee workflows. Create a budget and ordering process for IT resources.
|
||||||
% }
|
}
|
||||||
\item {
|
\item {
|
||||||
Operate as a single IT administrator to manage resources at all levels
|
Operate as a single IT administrator to manage resources at all levels
|
||||||
and in all areas of the business, including facility infrastructure,
|
and in all areas of the business, including facility infrastructure,
|
||||||
cloud resources, licensing, physical and virtual servers, and employee
|
cloud resources, licensing, physical and virtual servers, and employee
|
||||||
workstations.
|
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 {
|
\item {
|
||||||
Provide daily support for the entire organization across four timezones.
|
Provide daily support for the entire organization across four timezones.
|
||||||
Support Windows, MacOS, and Linux workstations, enterprise resource
|
Support Windows, MacOS, and Linux workstations, enterprise resource
|
||||||
@ -51,18 +38,18 @@
|
|||||||
infrastructure including virtual private clouds, on-site network equipment,
|
infrastructure including virtual private clouds, on-site network equipment,
|
||||||
and virtual private networking.
|
and virtual private networking.
|
||||||
}
|
}
|
||||||
% \item {
|
\item {
|
||||||
% Offboard and assume responsibilities of existing Managed
|
Offboard and assume responsibilities of existing Managed
|
||||||
% Service Provider and manage relationships with IT vendors
|
Service Provider and manage relationships with IT vendors
|
||||||
% as the primary point of contact.
|
as the primary point of contact.
|
||||||
% }
|
}
|
||||||
\end{cvitems}
|
\end{cvitems}
|
||||||
}
|
}
|
||||||
|
|
||||||
%---------------------------------------------------------
|
%---------------------------------------------------------
|
||||||
\cventry
|
\cventry
|
||||||
{Starry Inc. - Product Engineering} % Company + department
|
{Starry Inc. - Product Engineering} % Job title
|
||||||
{Systems Administrator / Development Operations Engineer} % Job title
|
{Systems Administrator / Development Operations Engineer} % Organization
|
||||||
{Boston MA, United States} % Location
|
{Boston MA, United States} % Location
|
||||||
{June 2018 - August 2022} % Date(s)
|
{June 2018 - August 2022} % Date(s)
|
||||||
{
|
{
|
||||||
@ -78,19 +65,19 @@
|
|||||||
to alerts, data, and performance reports for the Tier 2 Support team and
|
to alerts, data, and performance reports for the Tier 2 Support team and
|
||||||
executive leadership.
|
executive leadership.
|
||||||
}
|
}
|
||||||
% \item {
|
\item {
|
||||||
% Designed and deployed a testbed management network using off-the-shelf
|
Designed and deployed a testbed management network using off-the-shelf
|
||||||
% routing equipment and Ansible that connected engineering systems at all
|
routing equipment and Ansible that connected engineering systems at all
|
||||||
% eleven corporate offices across the country.
|
eleven corporate offices across the country.
|
||||||
% }
|
}
|
||||||
\item {
|
\item {
|
||||||
Helped 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.
|
securing hundreds of physical engineering systems across four departments.
|
||||||
}
|
}
|
||||||
\item {
|
%\item {
|
||||||
Contributed to the design, implementation, and operation of a REST API for
|
% Contributed to the design, implementation, and operation of a REST API for
|
||||||
indexing test results to serve the needs of multiple test teams.
|
% indexing test results to serve the needs of multiple test teams.
|
||||||
}
|
%}
|
||||||
\item {
|
\item {
|
||||||
Facilitated inter-operation between the Manufacturing Division and
|
Facilitated inter-operation between the Manufacturing Division and
|
||||||
Product Engineering to support expanded access to internal technology,
|
Product Engineering to support expanded access to internal technology,
|
||||||
@ -102,8 +89,8 @@
|
|||||||
|
|
||||||
%---------------------------------------------------------
|
%---------------------------------------------------------
|
||||||
\cventry
|
\cventry
|
||||||
{Worcester Polytechnic Institute - Network Operations Center} % Company + department
|
{Worcester Polytechnic Institute - Network Operations Center} % Job title
|
||||||
{Senior Network Technician} % Job title
|
{Senior Network Technician} % Organization
|
||||||
{Worcester MA, United States} % Location
|
{Worcester MA, United States} % Location
|
||||||
{August 2013 - June 2018} % Date(s)
|
{August 2013 - June 2018} % Date(s)
|
||||||
{
|
{
|
||||||
@ -127,54 +114,26 @@
|
|||||||
}
|
}
|
||||||
|
|
||||||
%---------------------------------------------------------
|
%---------------------------------------------------------
|
||||||
\cventry
|
\cventry
|
||||||
{Dassault Systèmes S.E. - SOLIDWORKS User Experience} % Company + department
|
{Dassault Systèmes S.E. - SOLIDWORKS User Experience} % Job title
|
||||||
{Contract Development Operations Specialist} % Job title
|
{Contract Technical Writer} % Organization
|
||||||
{Waltham MA, United States} % Location
|
{Waltham MA, United States} % Location
|
||||||
{May 2016 - August 2017} % Date(s)
|
{May 2015 - January 2016} % Date(s)
|
||||||
{
|
{
|
||||||
\begin{cvitems} % Description(s) of tasks/responsibilities
|
\begin{cvitems} % Description(s) of tasks/responsibilities
|
||||||
\item {
|
\item {
|
||||||
Worked as a software specialist on a Graphics Design team to take over
|
Tested official product tutorials for compliance with user workflows in
|
||||||
maintenance of a custom-built image asset lifecycle management tool and
|
SOLIDWORKS 2016 and updated the tutorials if they were outdated.
|
||||||
design its replacement.
|
}
|
||||||
|
\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}
|
||||||
}
|
}
|
||||||
\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}
|
\end{cventries}
|
||||||
|
@ -9,9 +9,10 @@
|
|||||||
%-------------------------------------------------------------------------------
|
%-------------------------------------------------------------------------------
|
||||||
\begin{cvskills}
|
\begin{cvskills}
|
||||||
\cvskill{Interpersonal}{
|
\cvskill{Interpersonal}{
|
||||||
interdisciplinary communication,
|
Cross-team communication,
|
||||||
specification design and evaulation,
|
specification design and evaulation,
|
||||||
technical writing and documentation,
|
problem analysis,
|
||||||
|
incident triage,
|
||||||
security threat modeling
|
security threat modeling
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@ -58,8 +58,8 @@
|
|||||||
\name{Ethan}{Paul}
|
\name{Ethan}{Paul}
|
||||||
%\position{Systems Administrator / Development Operations Engineer}
|
%\position{Systems Administrator / Development Operations Engineer}
|
||||||
|
|
||||||
\mobile{+1 (617) 733-0601}
|
\mobile{+1.617.733.0601}
|
||||||
\email{me@enpaul.net}
|
\email{me@enp.one}
|
||||||
%\dateofbirth{January 1st, 1970}
|
%\dateofbirth{January 1st, 1970}
|
||||||
%\homepage{enpaul.net}
|
%\homepage{enpaul.net}
|
||||||
%\github{posquit0}
|
%\github{posquit0}
|
||||||
@ -77,7 +77,7 @@
|
|||||||
% \extrainfo{extra information}
|
% \extrainfo{extra information}
|
||||||
|
|
||||||
% How the letter is closed
|
% How the letter is closed
|
||||||
\letterclosing{\recipientaddressstyle{Ethan Paul\\218 Thorndike Street Unit \#101\\Cambridge, MA 02141\\U.S.A.}}
|
\letterclosing{\recipientaddressstyle{Ethan Paul\\13 Faxon St\\Newton, MA 02458\\USA}}
|
||||||
% Any enclosures with the letter
|
% Any enclosures with the letter
|
||||||
%\letterenclosure[Attached]{Resume}
|
%\letterenclosure[Attached]{Resume}
|
||||||
|
|
||||||
|
@ -1,64 +0,0 @@
|
|||||||
%-------------------------------------------------------------------------------
|
|
||||||
% 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.
|
|
||||||
}
|
|
@ -72,9 +72,9 @@
|
|||||||
% \photo[rectangle,edge,right]{./examples/profile}
|
% \photo[rectangle,edge,right]{./examples/profile}
|
||||||
\name{Ethan}{Paul}
|
\name{Ethan}{Paul}
|
||||||
\position{
|
\position{
|
||||||
System Administrator
|
Systems Administrator
|
||||||
{\enskip\cdotp\enskip}
|
{\enskip\cdotp\enskip}
|
||||||
Information Technology \& Security
|
Information Technology
|
||||||
{\enskip\cdotp\enskip}
|
{\enskip\cdotp\enskip}
|
||||||
Software Engineer
|
Software Engineer
|
||||||
}
|
}
|
||||||
|
Loading…
x
Reference in New Issue
Block a user