About Thomas Robertson

Built from
scratch.
Twice.

From chemistry and near-death to computer science with zero prior programming experience — and from there to DoD research contracts, Fortune 100 AI engineering, an IEEE publication, and a founded consulting practice.

Not the most direct path. But the only one I would have taken.

Thomas D. Robertson II

The Story

The non-linear path.

Chapter 1

Before computers

Raised in rural Jamestown, Tennessee — an environment that actively discouraged ambition. Pursued a B.S. in Chemistry at Tennessee Tech with plans for medicine, working in pharmaceutical settings and as a clinical pharmacy technician while preparing for medical school. The paths I was actually excited about felt out of reach; mainstream medical practice felt more like liability management than the meaningful work I'd imagined.

Chapter 2

The reset

While working patient care during COVID, I contracted a severe strain and became critically ill — hospitalized with mass organ failure, lung collapse, and temporary brain damage. My physician told me I likely would not survive. Of 32 patients on my ward, four survived. Eighteen months of physical therapy followed. The experience made a clean break both necessary and clarifying. I needed to build a new future, entirely on my own terms.

Chapter 3

Zero to production

With zero prior programming experience, I found computer science through YouTube, took CS50x to test the interest, enrolled at Tennessee Tech in June 2023, and completed my B.S. with a 4.0 major GPA. In that window: a DoD research contract, an IEEE publication, a hackathon win, Fortune 100 AI engineering experience, and a founded company — while still holding my clinical hospital role until January 2026.

Background

The record.

Education
  • B.S. Computer Science — Tennessee Tech University (4.0 Major GPA)
  • M.S. Computer Science — Tennessee Tech (In Progress, May 2027)
  • CS50x — Harvard University
Certifications
  • CITI Responsible Conduct of Research
  • DevOps Foundation
  • Applied Cybersecurity Ethics
  • In Progress: PMP · PSM1 · Certified Ethical Hacker (CEH)
Recognition
  • IEEE Publication — GPS Spoofing Resilience in Autonomous Vehicles (MWSCAS 2025)
  • Portobello Hackathon — Best Technological Innovation (1st Place)
  • TTU Capstone Excellence Award (2nd Place)
  • Phi Kappa Phi · Kappa Mu Epsilon
  • CCDC Captain — Collegiate Cyber Defense Competition

How I work

What you can expect.

These aren't aspirational statements. They show up in the work itself.

Craft over speed

Hover states, texture layers, animation easing, type hierarchy — the level of care is not accidental. Built right over built fast, every time.

Systems over one-offs

If something has to be done twice, it becomes a template by the third time. The tools get built alongside the work.

Documentation as credibility

Every project gets a design decision log. What was chosen, what was rejected, why. The record is part of the deliverable.

Security by default

Most developers don't think adversarially. Threat modeling, secure architecture, and hardened code are part of the build — not a retrofit.

Attribution is a statement

Name on every site built. That's a deliberate professional commitment — not a courtesy.

Earned, not borrowed

Zero programming experience to DoD research, Fortune 100, and IEEE publication. The credibility came from the work itself.

Let's work together

Ready to build something that holds up?

Book a 30-minute consultation or browse the portfolio to see the work in context.