Portfolio

Owen Schuyler

Senior Computer Science Student | Full-Stack Developer | Former CCIT NOC Automation Intern

I build automation tools, backend systems, and full-stack applications using Python, SQL, REST APIs, Linux, and cloud infrastructure. My recent work includes operational automation for Clemson CCIT's Network Operations Center and deployed web applications with database-backed workflows.

View Featured Work View GitHub

Python + Flask SQL + REST APIs AWS + Linux Automation + Monitoring

Who I am

Senior Computer Science student preparing for full-stack and backend engineering roles.

What I build

Automation tools, database-backed applications, reporting flows, and operational integrations.

Where to start

Begin with the featured capstone project, then review Persistent Waters for team project progression.

Featured Work

Featured Projects

These are the projects I would lead with in an interview because they show full-stack delivery, role-based workflows, deployed systems, and concrete engineering decisions.

Senior Capstone

Live App

Good Driver Incentive Program

A full-stack incentive platform for the trucking industry where sponsors reward drivers with points for safe driving behavior and drivers redeem those points through sponsor-managed catalogs.

Full-Stack Web App Role-Based Workflows Reporting Audit Logging AWS Deployment

Sponsor catalogs and point tracking Database-backed admin workflows Responsive UI for multiple user roles

View Live App Read Case Study

Team Project

Live + Code

Persistent Waters

A multi-phase Battleship-style web application that progressed from API foundations to a deployed, backend-authoritative gameplay experience with persistent match state.

Python Flask REST APIs Deployment

View Live App View Code Project Details

Project Details

Good Driver Incentive Program case study

The Good Driver Incentive Program is a full-stack web application for trucking sponsors, drivers, and administrators to manage points, rewards, reports, catalogs, and audit-ready account activity. It is interesting because it supports multiple user roles with different workflows while keeping the overall experience usable and responsive. A key architecture decision was keeping point tracking, reporting, and audit-sensitive actions tied to database-backed server logic so business rules remain consistent across roles.

Why it matters

Full-stack workflow depth

This project demonstrates more than a landing page or CRUD demo: it includes role-aware navigation, sponsor-managed catalogs, driver redemption flows, reports, and admin-level controls.

Architecture focus

Data-backed accountability

Point balances, reports, and audit logs are strongest when the backend owns the logic, making the application easier to reason about and safer to extend.

Deployment

AWS-hosted capstone delivery

The live application is deployed and accessible, which makes it easy to demo real workflows quickly during a portfolio review or interview conversation.

Team Project Phases

Persistent Waters progression across three phases

Each phase has one working destination so the project story is easy to follow without sending reviewers into broken or ambiguous paths.

Phase 1

View Code

Backend API foundation

Established Flask routes, match state handling, and server-owned gameplay rules as the project baseline.

Phase 2

Open Live Build

Playable web application

Added the live board, move flow, polling updates, and player-facing interactions for a complete demo path.

Phase 3

View Code

Refinement and presentation

Polished the project story, contribution details, and demo flow into a clear final presentation.

My Contributions

I focused on work I can explain clearly, from backend logic and routing decisions to deployment and project presentation.

Persistent Waters

Structured backend route responsibilities so game creation, move submission, and match retrieval stayed organized around server-owned state.
Implemented or supported gameplay validation logic for turns, shot resolution, and consistent match updates returned to the frontend.
Connected the playable board flow to backend endpoints so player actions passed through the same validation path as the API layer.
Helped keep the project demoable across phased deliveries by supporting iterative deployment and presentation polish.

Good Driver Incentive Program

Built and presented a full-stack incentive platform centered on sponsor, driver, and admin workflows instead of a single-user demo path.
Emphasized database-backed features such as point tracking, catalog management, reporting, and audit-oriented activity visibility.
Shaped the project around operationally useful flows where multiple roles manage users, rewards, and accountability across the same system.
Delivered a responsive, publicly reachable capstone demo suitable for quick portfolio review.

Other Projects

A few additional projects highlight my experience with Flask, automation, and infrastructure-focused tooling.

Book Collection Manager

Live App

Flask and PostgreSQL CRUD application with search, filtering, sorting, validation, pagination, and persistent data.

Flask PostgreSQL Jinja

View Live App View Code

StatusHub Slack Integration

Automation

Slack bot integration for StatusHub incident workflows with HMAC SHA-256 request validation, replay attack protection, and Linux systemd deployment for stable service operation.

Slack API StatusHub API systemd

View Code