Compare commits
	
		
			23 Commits
		
	
	
		
			371d7e8d27
			...
			2024-05/in
		
	
	| Author | SHA1 | Date | |
|---|---|---|---|
| aad2648e91 | |||
| ea60e5f2aa | |||
| 680d864aa9 | |||
| cd5076922a | |||
| 7081b174da | |||
| efa0f0760f | |||
| e349dc89bb | |||
| 3964c315df | |||
| 9dffb95070 | |||
| 52871bdf71 | |||
| b080d4af53 | |||
| b4a9e73113 | |||
| 64aab159fa | |||
| 8bdcf88fdc | |||
| 276c709e15 | |||
| 2e08eab36c | |||
| a5768cdb0a | |||
| f146b4b097 | |||
| 5a636bb9aa | |||
| 88a7198f3a | |||
| 6a3676e53d | |||
| 22675b8d45 | |||
| 03353d85ad | 
							
								
								
									
										10
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										10
									
								
								README.md
									
									
									
									
									
								
							| @@ -9,8 +9,14 @@ View the published version of this document at the permalink [here](https://cdn. | |||||||
|  |  | ||||||
| ## System requirements (Fedora): | ## System requirements (Fedora): | ||||||
|  |  | ||||||
| - `tetex` | - `texlive-scheme-tetex` | ||||||
| - `texlive-fontawesome5` | - `texlive-fontawesome5` | ||||||
| - `texlive-sourcesanspro` | - `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 |   \cventry | ||||||
|  |     {Bachelor of Science in Mechanical Engineering / Minor in Business Administration} % Degree | ||||||
|     {Worcester Polytechnic Institute} % Institution |     {Worcester Polytechnic Institute} % Institution | ||||||
|     {Bachelor of Science in Mechanical Engineering} % Degree |  | ||||||
|     {Worcester MA, United States} % Location |     {Worcester MA, United States} % Location | ||||||
|     {Class of 2017} % Date(s) |     {Class of 2017} % Date(s) | ||||||
|     { |     { | ||||||
|       \begin{cvitems} % Description(s) bullet points |     %  \begin{cvitems} % Description(s) bullet points | ||||||
|         \item {Minor in Business Administration} |     %    \item {Minor in Business Administration} | ||||||
|       \end{cvitems} |     %  \end{cvitems} | ||||||
|     } |     } | ||||||
|  |  | ||||||
|  |   \vspace{-4mm} % needed while no bullet points under education | ||||||
|  |  | ||||||
| %--------------------------------------------------------- | %--------------------------------------------------------- | ||||||
| \end{cventries} | \end{cventries} | ||||||
|   | |||||||
| @@ -11,33 +11,88 @@ | |||||||
|  |  | ||||||
| %--------------------------------------------------------- | %--------------------------------------------------------- | ||||||
|   \cventry |   \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 |     {Systems Administrator / Development Operations Engineer} % Job title | ||||||
|     {Starry Inc - Product Engineering} % Organization |  | ||||||
|     {Boston MA, United States} % Location |     {Boston MA, United States} % Location | ||||||
|     {June 2018 - Present} % Date(s) |     {June 2018 - August 2022} % Date(s) | ||||||
|     { |     { | ||||||
|       \begin{cvitems} % Description(s) of tasks/responsibilities |       \begin{cvitems} % Description(s) of tasks/responsibilities | ||||||
|         \item { |         \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 |           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 |           the needs of the Network Operations team and handle a thirty-fold workload | ||||||
|           increase. |           increase. | ||||||
|         } |         } | ||||||
|         \item { |         \item { | ||||||
|           Designed and deployed a testbed management network using Ubiquiti |           Provided 24/7 support for the NMS to ensure uninterrupted access | ||||||
|           EdgeRouters and Ansible that connected engineering equipment at all |           to alerts, data, and performance reports for the Tier 2 Support team and  | ||||||
|           eleven corporate offices across the country. |           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 { |         \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. |           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 interoperation 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, | ||||||
|           increased awareness of documentation and knowledge resources, and greater |           increased awareness of documentation and knowledge resources, and greater | ||||||
|           cross-team communication. |           cross-team communication. | ||||||
| @@ -47,88 +102,79 @@ | |||||||
|  |  | ||||||
| %--------------------------------------------------------- | %--------------------------------------------------------- | ||||||
|   \cventry |   \cventry | ||||||
|     {Development Operations Contractor} % Job title |     {Worcester Polytechnic Institute - Network Operations Center} % Company + department | ||||||
|     {Dassault Systèmes SE - SOLIDWORKS User Experience} % Organization |  | ||||||
|     {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 replace |  | ||||||
|           an existing unsupported image asset lifecycle management tool. |  | ||||||
|         } |  | ||||||
|         \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. |  | ||||||
|         } |  | ||||||
|       \end{cvitems} |  | ||||||
|     } |  | ||||||
|  |  | ||||||
| %--------------------------------------------------------- |  | ||||||
|   \cventry |  | ||||||
|     {Senior Network Technician} % Job title |     {Senior Network Technician} % Job title | ||||||
|     {Worcester Polytechnic Institute - Network Operations} % Organization |  | ||||||
|     {Worcester MA, United States} % Location |     {Worcester MA, United States} % Location | ||||||
|     {August 2013 - June 2018} % Date(s) |     {August 2013 - June 2018} % Date(s) | ||||||
|     { |     { | ||||||
|       \begin{cvitems} % Description(s) of tasks/responsibilities |       \begin{cvitems} % Description(s) of tasks/responsibilities | ||||||
|         \item { |         % \item { | ||||||
|           Developed procedures for technicians to follow when debugging WPA certificate |         %   Acted as first point of contact for users experiencing networking issues to | ||||||
|           authentication on Windows, Android, iPhone, and Ubuntu systems. |         %   triage problems and escalate to network engineers when appropriate. | ||||||
|         } |         % } | ||||||
|         \item { |  | ||||||
|           Acted as first point of contact for users experiencing networking issues to |  | ||||||
|           triage problems and escalate to network engineers when appropriate. |  | ||||||
|         } |  | ||||||
|         \item { |         \item { | ||||||
|           Assisted with regular maintenance of the three campus data centers, including |           Assisted with regular maintenance of the three campus data centers, including | ||||||
|           replacing faulty PDUs, organizing and documenting routed cables, and retiring |           replacing faulty PDUs, organizing and documenting routed cables, and retirement of | ||||||
|           network and server hardware. |           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 { |         \item { | ||||||
|           Planned and developed campus-wide documentation of network conduit to |           Planned and developed campus-wide documentation of network conduit to | ||||||
|           provide the Network Operations and Telecommunication departments with better |           provide the Network Operations and Telecommunication departments with better | ||||||
|           information sources when triaging problems, doing maintenance work, and |           information sources when triaging problems, performing maintenance work, and | ||||||
|           planning expansions. |           planning expansions. | ||||||
|         } |         } | ||||||
|       \end{cvitems} |       \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} | \end{cventries} | ||||||
|   | |||||||
| @@ -9,10 +9,9 @@ | |||||||
| %------------------------------------------------------------------------------- | %------------------------------------------------------------------------------- | ||||||
| \begin{cvskills} | \begin{cvskills} | ||||||
|     \cvskill{Interpersonal}{ |     \cvskill{Interpersonal}{ | ||||||
|         Cross-team communication, |         interdisciplinary communication, | ||||||
|         specification design and evaulation, |         specification design and evaulation, | ||||||
|         problem analysis, |         technical writing and documentation, | ||||||
|         remote triage and debug, |  | ||||||
|         security threat modeling |         security threat modeling | ||||||
|     } |     } | ||||||
|  |  | ||||||
| @@ -22,44 +21,41 @@ | |||||||
|         L2/L3 Routing, |         L2/L3 Routing, | ||||||
|         DNS, |         DNS, | ||||||
|         DHCP, |         DHCP, | ||||||
|         Docker, |         Containers, | ||||||
|         Microsoft IIS, |  | ||||||
|         Nginx, |         Nginx, | ||||||
|         Apache, |         Apache, | ||||||
|         MySQL/MariaDB, |         MySQL/MariaDB, | ||||||
|         MongoDB, |         MongoDB, | ||||||
|         Postgres, |         OpenSSH, | ||||||
|         OpenSSH |         CI/CD | ||||||
|     } |     } | ||||||
|  |  | ||||||
|     \cvskill{Administration}{ |     \cvskill{Administration}{ | ||||||
|         Windows Server, |         Windows Server, | ||||||
|         Ubuntu Server, |         Debian/RHEL Server, | ||||||
|         CentOS/RockyLinux, |         Active Directory, | ||||||
|         Microsoft ADDS, |         LDAP, | ||||||
|         OpenLDAP, |  | ||||||
|         Microsoft Hyper-V, |         Microsoft Hyper-V, | ||||||
|         KVM, |         KVM, | ||||||
|         RedHat Ovirt, |         VMWare ESXi, | ||||||
|  |         Google Workspace, | ||||||
|  |         Microsoft O365 | ||||||
|     } |     } | ||||||
|  |  | ||||||
|     \cvskill{Software}{ |     \cvskill{Software}{ | ||||||
|         Python3, |         Python, | ||||||
|         Tox, |         Bash, | ||||||
|         Poetry, |         TypeScript, | ||||||
|         Pylint, |  | ||||||
|         MyPy, |  | ||||||
|         SQL, |         SQL, | ||||||
|         HTML, |         HTML, | ||||||
|         CSS, |         CSS, | ||||||
|         Bash, |  | ||||||
|         Git, |         Git, | ||||||
|         Gitea, |  | ||||||
|         Gitlab, |  | ||||||
|         Github, |  | ||||||
|         CI/CD, |  | ||||||
|         Jenkins, |  | ||||||
|         Ansible, |         Ansible, | ||||||
|         GNU Make |         GNU Make, | ||||||
|  |         Terraform, | ||||||
|  |         PHP, | ||||||
|  |         PowerShell, | ||||||
|  |         Docker Swarm, | ||||||
|  |         GlusterFS | ||||||
|     } |     } | ||||||
| \end{cvskills} | \end{cvskills} | ||||||
|   | |||||||
| @@ -1,7 +1,7 @@ | |||||||
| %------------------------------------------------------------------------------- | %------------------------------------------------------------------------------- | ||||||
| %	SECTION TITLE | %	SECTION TITLE | ||||||
| %------------------------------------------------------------------------------- | %------------------------------------------------------------------------------- | ||||||
| \cvsection{Introduction} | \cvsection{Summary} | ||||||
|  |  | ||||||
|  |  | ||||||
| %------------------------------------------------------------------------------- | %------------------------------------------------------------------------------- | ||||||
| @@ -9,9 +9,12 @@ | |||||||
| %------------------------------------------------------------------------------- | %------------------------------------------------------------------------------- | ||||||
| \begin{cvparagraph} | \begin{cvparagraph} | ||||||
|  |  | ||||||
| %--------------------------------------------------------- | Computer engineer and system administrator with experience designing and  | ||||||
| Current Linux Systems Administrator and Development Operations Engineer at | operating a diverse set of digital infrastructure, including data center  | ||||||
| Starry Inc looking for opportunities in Development Operations, Site | equipment, core and edge networks, multi-cloud environments, end-user devices,  | ||||||
| Reliability Engineering, or Technical Support at socially conscious | and SaaS products. Proven ability to work independently or collaboratively to  | ||||||
| companies and organizations. | 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} | \end{cvparagraph} | ||||||
|   | |||||||
| @@ -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@enp.one} | \email{me@enpaul.net} | ||||||
| %\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{Sincerely,} | \letterclosing{\recipientaddressstyle{Ethan Paul\\218 Thorndike Street Unit \#101\\Cambridge, MA 02141\\U.S.A.}} | ||||||
| % Any enclosures with the letter | % Any enclosures with the letter | ||||||
| %\letterenclosure[Attached]{Resume} | %\letterenclosure[Attached]{Resume} | ||||||
|  |  | ||||||
|   | |||||||
							
								
								
									
										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. | ||||||
|  | } | ||||||
							
								
								
									
										14
									
								
								resume.tex
									
									
									
									
									
								
							
							
						
						
									
										14
									
								
								resume.tex
									
									
									
									
									
								
							| @@ -72,16 +72,16 @@ | |||||||
| % \photo[rectangle,edge,right]{./examples/profile} | % \photo[rectangle,edge,right]{./examples/profile} | ||||||
| \name{Ethan}{Paul} | \name{Ethan}{Paul} | ||||||
| \position{ | \position{ | ||||||
|   Systems Administrator |   System Administrator | ||||||
|   {\enskip\cdotp\enskip} |   {\enskip\cdotp\enskip} | ||||||
|   Development Operations Engineer |   Information Technology \& Security | ||||||
|   {\enskip\cdotp\enskip} |   {\enskip\cdotp\enskip} | ||||||
|   Software Engineer |   Software Engineer | ||||||
| } | } | ||||||
| % \address{Boston MA, United States} | % \address{Boston MA, United States} | ||||||
|  |  | ||||||
| % \mobile{} | \mobile{+1 (617) 733-0601} | ||||||
| \email{me@enp.one} | \email{me@enpaul.net} | ||||||
| \homepage{enpaul.net} | \homepage{enpaul.net} | ||||||
| \github{enpaul} | \github{enpaul} | ||||||
| \linkedin{enpaul} | \linkedin{enpaul} | ||||||
| @@ -122,12 +122,6 @@ | |||||||
| \input{content/education.tex} | \input{content/education.tex} | ||||||
| \input{content/experience.tex} | \input{content/experience.tex} | ||||||
| \input{content/skills.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} | \end{document} | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user