002 / ABOUT — NICHOLAS PERRYREV 2026.05
PLATE IPORTRAIT
Nicholas Perry
NICHOLAS PERRYSRE · ENGINEER

DOSSIER

An engineer bridging product, infrastructure, and reliability.

Since 2018 I've worked across the tech stack — starting in service desk and endpoint support, moving through retail systems and IT engineering, and arriving at cloud and reliability work.

I treat technology as a craft. Whether I'm architecting a cloud system or shipping a product surface, the goal is the same: a clear plan, working software, and code that a future engineer can pick up without friction.

03 / EXPERTISEDOMAINS

Cloud & DevOps

Building and optimizing infrastructure with AWS and Terraform, guided by modern DevOps practices.

Infrastructure & SRE

Ensuring reliability and performance through monitoring, automation, and incident response.

04 / EXPERIENCE5 ENTRIES
05

AUG 2024 — PRESENT

Site Reliability Engineer

PNC

  • Drive engineering stability through analytics and metrics
  • Implement monitoring systems and SLA/SLO management
  • Lead performance tuning and complex incident response
  • Mentor junior team members on infrastructure best practices
04

MAR 2024 — NOV 2024

DevOps Engineer Intern

Level Up in Tech

Intensive cloud internship focused on Linux, AWS, Python, Containers, Terraform, and AI integration. Worked on real-world projects with industry mentorship.

03

SEP 2023 — 2024

IT Engineer

Devoted Health

  • Optimized cloud integration with SSO and enhanced security protocols
  • Managed Jira boards and GitHub repositories for cross-functional teams
  • Pioneered Chromebook deployment and network infrastructure improvements
02

MAR 2022 — SEP 2023

IT Engineer

Circle K IT Retail Systems

  • Deployed and supported retail software and the technology behind it
  • Managed POS systems, fuel systems, and back-office infrastructure
  • Improved documentation and drove process-improvement initiatives
01

MAR 2020 — MAR 2022

Service Desk Tier 1-2

Belltechlogix

Provided technical support using ServiceNow, handling system configurations, user support, and detailed documentation of all interactions.

REV 2026.05ASC
05 / PRACTICE3 PRINCIPLES
01

Clarity first

A clearly scoped problem is half the solution. I start every engagement with shaping and tradeoffs.

02

Quality compounds

Type safety, tests, and observability aren't overhead — they're what let future changes ship quickly.

03

Ship, then refine

Working software in production beats elegant software on a branch. Iterate from real feedback.