Harrison Stephan | Software Engineer

Position / 00

Software that holds up in production.

Full-stack software engineer building React/.NET systems, internal tools, and debugging workflows that hold up in production.

Software engineer working across React, TypeScript, C#, .NET, Redux Toolkit, RTK Query, SQL-backed systems, production diagnostics, and systems-level C contributions.

harrison@stephanclan.com linkedin.com/in/harrisonstephanBoise, Idaho

Selected evidence ↓Résumé PDF ↓

export class DepGraphDiagnostics {
  private collection: vscode.DiagnosticCollection;
 
  update(graph: GraphData): void {
    this.collection.clear();
    const root = getWorkspaceRoot();
  

UTF-8hstephan23/dep_graph

Trace plate / reviewed 2026

Novion / systems observer / origin 00

Systems proof / S01–S07

Trace the whole workflow.

S01ReactInterface layer
S02ReduxClient state
S03RTK QueryAPI data flow
S04C# / .NETBackend services
S05SQLService data
S06DiagnosticsProduction tracing

S07C SystemsParallel lower-level practice

Project register / P01–P033 records / 2 public / 1 private

Selected evidence.

Engineering decisions, observable outcomes, and reviewable source receipts.

P01 / Lead record

Dependency Analysis

DepGraph

Dependency analysis / editor-visible signal.

Proof note / Signal lands where developers work.

Problem: Dependency risk becomes dangerous when high-reach files and cycles remain invisible before a change.
Decision: Favor fewer, explainable diagnostics and place the signal inside the developer's normal VS Code workflow.
Outcome: Graph analysis becomes reviewable file-level evidence instead of a detached report.

TypeScript / Python / VS Code Extension / Graph Analysis

Source receipt / publichstephan23/dep_graphRepository verified

View source ↗View project

P02 / Systems record

C++ Game Prototype

2D Shooter Looter

C++ extraction-shooter prototype.

Proof note / Frame order stays auditable.

Problem: Combat, loot, room state, and extraction pressure must grow without hiding side effects.
Decision: Keep frame order explicit and architecture deliberately plain until playtesting proves the right abstractions.
Outcome: A playable three-room loop with auditable update, collision, transition, and render phases.

C++ / raylib / CMake / Game Loop / Playtesting

Source receipt / publichstephan23/2D_shooter_looterRepository verified

View source ↗View project

P03 / Lifecycle record

C Game Systems

Retro Game

Lower-level C systems practice.

Proof note / Explicit state over clever abstraction.

Problem: Timing, input, rendering, multiplayer behavior, and shutdown become fragile when lifecycle boundaries blur.
Decision: Keep state transitions visible rather than abstracting the main game lifecycle too early.
Outcome: Readable control flow across input, timed movement, rendering, state application, and cleanup.

C / CMake / ncurses / Game Loop / Networking

Source receipt / privatePrivate excerpt available on this siteReviewable code proof

View project

Working brief / WB-01

I build software from the user workflow down to the system boundary.

Method note / learn the system before changing it

My path runs through teaching, chemistry, and software engineering. That mix shapes how I work: explain the problem clearly, trace the full workflow, and build interfaces and tools that stay calm under real use.

Now: Software Engineer at In Time Tec building production applications across React, TypeScript, C#, .NET, SQL-backed services, and C contributions.
Focus: Full-stack product engineering, production reliability, observability, debugging discipline, and codebase comprehension.
Direction: Production-ready internal tools and lower-level systems practice with explicit, testable state boundaries.

Contact

Let's build something that holds up.

Open to software engineering opportunities and interesting technical problems.

Download Resume View on LinkedIn