Trevor GibbySenior Full-Stack Engineer
Résumé
Exploring senior engineering and hands-on technical leadership roles

Senior Full-Stack Engineer · Technical Lead

Senior Full‑Stack Engineer & Hands‑On Technical Lead

I build and modernize full-stack systems across product, platform, integrations, and infrastructure while helping small engineering teams deliver better work.

Explore My Work
portfolio.systemHANDS-ON
Trevor Gibby TG insignia
01 Product
02 Platform
03 Leadership
≈50%less new-site implementation time
2×0→1 prototype iterations
AWScost-conscious continuity system
HTML5CSS3SCSSJavaScriptTypeScriptjQueryBootstrapVue.jsReact.jsPHP 7PHP 8ApacheNode.jsExpress.js
01Selected case studies

Proof in the decisions.

Four stories about product ownership, reusable systems, operational resilience, and practical modernization.

01Personal product prototype
Independent in-progress prototype

Operations Platform for Agencies

A 0→1 operations platform built around the account hierarchies and communication workflows that agency teams actually manage.

Problem
Generic CRM and project tools do not cleanly model franchise brands, locations, and the relationships between them.
My role
I own the product direction, data model, architecture, implementation, and verification.
Evidence
Two working iterations now support core CRM, scoped access, team administration, and Gmail-based communication workflows.
  • Next.js
  • TypeScript
  • Prisma
  • PostgreSQL
  • Auth.js
  • Jest
Read the case study
Dark operations-platform interface showing a nested account hierarchy with filters and status labels
02Ninthroot · Oak CMS
Shipped production capability

Oak Component Engine

A reusable component system that replaced repeated page markup with understandable, centrally managed CMS capabilities.

Problem
Repeated HTML structures with unique content made each new site slower to implement and harder to update.
My role
I designed and built the syntax, definition UI, rendering engine, editor snippets, and conditional template behavior.
Evidence
It cut new-site implementation time by approximately 50% and became the primary implementation method for new Oak CMS sites.
  • PHP
  • HTML
  • SCSS
  • CMS Architecture
  • Developer Tooling
Read the case study
system / capability map02
Oak Component Engine
  • XML-style content syntax
  • Central component definitions
  • Conditional template chunks
  • Reusable editor snippets
03Ninthroot · Business continuity
Internal operational-resilience system

Chestnut Emergency Hosting

A low-cost continuity layer that keeps essential client pages and contact paths available during a primary-host outage.

Problem
A 24-hour hosting-provider outage exposed the risk of relying on a single production host.
My role
I helped lead the emergency response, documented the recovery process, then designed the longer-term continuity system.
Evidence
The system keeps a viable backup for all clients for a few dollars per month and reduces activation to two intentional operator actions.
  • Node.js
  • EJS
  • AWS Step Functions
  • Lambda
  • EventBridge
  • SNS
Read the case study
system / capability map03
Chestnut Emergency Hosting
  • Scheduled data synchronization
  • Normally powered-off backup host
  • Emergency brand and location pages
  • SMTP contact capability
04Ninthroot · Oak CMS
Ongoing production-platform modernization

Incremental Oak Modernization

A practical modernization program for a business-critical PHP platform where a rewrite was not the highest-value decision.

Problem
Legacy controllers, views, data access, and documentation had grown inconsistent across a long-lived CMS.
My role
I led compatibility work and introduced repeatable controller, view, data, documentation, and developer-instruction patterns.
Evidence
All CMS instances now run on PHP 8.4, with 50 standardized controllers, 20 updated views, and 3 modules on a structured ORM architecture.
  • PHP 8.4
  • ORM Architecture
  • MySQL
  • Structured Data
  • Documentation
Read the case study
system / capability map04
Incremental Oak Modernization
  • PHP 7.3 → 8.4
  • Standard controller configuration
  • Reusable helpers
  • Agent-ready development guidance
02How I work

Useful systems over impressive-sounding ones.

01

Pragmatic modernization

I improve established systems without treating a rewrite as the automatic answer.

Oak CMS: PHP 7.3 → 8.4, standardized controllers, and structured data.
02

Reusable product thinking

I turn repeated workarounds into capabilities the whole team can understand and reuse.

Oak Component Engine: approximately 50% less implementation time for new sites.
03

Hands-on leadership

I improve planning, tooling, debugging, review, and mentoring while continuing to contribute technically.

Engineering Team Lead responsible for delivery practices and developer growth.
04

Business-aware engineering

I weigh delivery speed, operating cost, risk, and maintainability before choosing an architecture.

Chestnut: emergency continuity for a few dollars per month instead of a full replica.
03Leadership & impact
Trevor Gibby
Based inTexas, USA

Product, platform, infrastructure, and the team doing the work.

Engineer, lead, systems owner

I take responsibility for the system around the feature.

I’m a senior full-stack engineer and Engineering Team Lead who works across product decisions, interfaces, back-end architecture, infrastructure, and delivery.

At Ninthroot, I progressed from student developer to Engineering Team Lead. My work has expanded from shipping web experiences to owning the capabilities behind them: a PHP framework and CMS, integrations, deployment workflows, business-continuity systems, and the engineering practices a small team relies on.

I’m most useful when a problem crosses boundaries. I can trace an issue from the user experience through application code, data, infrastructure, and team process, then choose a practical improvement that fits the business.

Outside that production work, I’m rebuilding an operations-platform concept with Next.js, TypeScript, Prisma, and PostgreSQL to keep sharpening my 0→1 product and architecture skills.

I earned a B.S. in Computer Science from Utah Valley University with Summa Cum Laude honors.

Read my résumé Download PDF
01

Platform ownership

I work across the CMS, integrations, infrastructure, delivery tooling, and new internal capabilities instead of treating each layer as someone else’s problem.

02

Team delivery

I introduced sprint planning and practical agile routines, trained developers on debugging and AI-assisted workflows, and improved code-review habits.

03

Technical judgment

I have shipped reusable systems, built proofs of concept, and recommended against deployment when operating cost or build-versus-buy tradeoffs did not hold up.

04Focused capabilities

Across the stack.
Beyond the code.

These are the capabilities I expect to use most in a senior full-stack or hands-on lead role.

01

Full-Stack Development

Product interfaces, application logic, APIs, data models, integrations, and delivery.

TypeScriptReactNext.jsNode.jsPHP
02

Software Architecture

Reusable capabilities, relational models, access boundaries, and incremental modernization.

PostgreSQLMySQLPrismaREST APIsSystem Design
03

Technical Leadership

Planning, mentoring, code review, documentation, debugging, and delivery practices.

Sprint PlanningMentoringDeveloper ToolingAI-Assisted Development
04

TypeScript & JavaScript

Modern TypeScript product work alongside deep JavaScript experience across front-end and Node.js systems.

TypeScriptJavaScriptReactVueExpress
05

Amazon Web Services

Cost-aware application and operational infrastructure built from focused managed services.

LambdaStep FunctionsEventBridgeSNSS3EC2

What I’m looking for

Ready for the next meaningful system.

I’m exploring senior full-stack and hands-on technical leadership opportunities where I can help build or modernize meaningful products.

View Résumé