Skip to content
Currently practicingEarly-career Web Dev (B.S. Oct 2025) · React/Express demos · Learning AWS + AI-assisted workflows

Bradley Matera · Portfolio & Blog

Bradley Matera

Systems-focused web developer who builds with AI support

U.S. Army combat medic → B.S. Web Development, Full Sail 2025. I treat software like the field work I came from: stay calm, study the system in front of me, and get it working.

Recent AWS Cloud Support internship work was all about labs, monitoring dashboards, and automating repetitive support workflows. I pair with tools like ChatGPT and Copilot in nearly every session to scaffold code, then I debug, adapt, and ship the result.

AWSCloud Support Engineer Intern · Amazon
B.S.Web Development · Full Sail · GPA 3.8
FocusCloud, DevOps, APIs, AI workflows
01

Production cloud systems

Harden AWS workloads with IAM, logging, staged environments, and cost-aware design that keeps services stable and affordable.

02

Secure backend services

Ship Node.js APIs with real authentication, instrumentation, and documentation so teammates can build on top without surprises.

03

Automation-first workflows

Wire CI/CD, branch protections, and AI helpers into delivery pipelines so the right code reaches production every time.

Quick snapshot

Builder-first, AI-assisted, always learning

Here’s the reality: I build small systems, learn out loud, and let AI pair-program with me.

  • BackgroundArmy combat medic, 82nd Airborne — keeps me calm when debugging and unblocking systems
  • How I buildI don’t start from a blank file — ChatGPT/Copilot scaffold projects, then I review, adapt, and document
  • Recent workGraduated Full Sail (Oct 2025) + AWS Cloud Support internship focused on labs, dashboards, and automation exercises
  • Right nowLooking for entry-level teams where I can keep practicing front-end fundamentals, ops hygiene, and honest documentation
Current practice loops

Shipping small demos, tightening feedback loops, telling the truth.

My projects are prototypes: front-end UI reps, tiny DevOps experiments, and AI-assisted notes that keep me honest about what I can (and can’t) do yet.
UI

Front-end reps

HTML/CSS/React demos (Pokédex, soundboard) keep me practicing accessibility, responsiveness, and copy that sets expectations.

Ops

Automation experiments

I tinker with Express proxies, Docker starter kits, and GitHub Actions to understand modern delivery pipelines—even if they only run on my laptop today.

AI

AI pair-programming

I log prompts, keep changelogs, and make sure every project page states when AI scaffolding or tutorials were involved.

Featured work

Prototype case studies with transparent scope.

Everything here is a learning project. I keep the copy plain, cite AI usage, and link to code so you can see what really shipped.
Why I build in public

Building in public keeps me honest.

I bring medic discipline into shipping software: stay calm, state what’s true, and leave notes for whoever touches it next (often future me).

  • Messy notes welcome — Blog posts call out whether they’re drafts, AI-assisted, or polished.
  • Changelogs everywhere — Commits and project pages log what’s shipped vs. what’s still in TODO.
  • Progress over polish — I’d rather share a half-finished demo with context than pretend it’s production-ready.
Let's collaborate

Looking for entry-level teams that value honesty and mentorship

I’m candid about where I’m strong (front-end demos, docs, automation experiments) and where I need guidance (algorithms, large-scale systems). If that resonates, let’s talk.

Quick ways to connect

What to expect next

I'll respond within 24 hours with availability, relevant case studies, and a short plan for how we can collaborate. Happy to pair-program, audit an existing build, or present a portfolio walkthrough.

Latest writing

Keep exploring

Curious about the process behind these projects?

The blog breaks down what I learn from each build—architecture decisions, accessibility wins, and what I'd improve next time.

Skim the latest posts below or dive into the archives to see how each project has evolved. I include code snippets, diagrams, and checklists so you can reuse the patterns in your own work.