Joey King

Seeking roles with larger ownership across software engineering, technical programs, technical operations, and internal platforms

I turn complicated technical and operational problems into systems teams can ship, run, and improve.

I’m Joey King. I started in software engineering (automation, internal platforms, and developer tooling) and have increasingly owned the whole arc of the work: finding the real problem, making the calls, lining up the people, and seeing systems through launch.

See selected workjoey@joeylking.com

How complex work comes together

PeopleWho feels the problemWho owns the callStakeholders and reviewersContributors and mentoringSupport and handoffFeedback from users
ProcessHow the work runs todayScope, risks, success measuresWhat depends on whatReview gatesRollout and rollbackWhat to change next
TechnologySystems already involvedOptions and their costsInterfaces and contractsWorking softwareRelease and monitoringRecords and measures
  1. 01 / 06

    Understand

    Find the operational problem behind the requested feature.

    In the workAutomation audit & retention platform

    Turned an incident the logs could no longer explain into a research spike, then worked with the analytics team and prospective users before proposing a shared service.

  2. 02 / 06

    Decide

    Set scope, constraints, risks, and what success will look like.

    In the workGoverned vulnerability remediation

    Cut AI from an eight-week prototype when its approval path was unclear, and delivered a deterministic workflow where a person approves every change.

  3. 03 / 06

    Coordinate

    Make dependencies, ownership, and tradeoffs visible.

    In the workLegacy platform modernization

    Released one or two endpoints at a time, with users validating each release while the legacy implementation stayed available.

  4. 04 / 06

    Build

    Turn the plan into maintainable technical work.

    In the workAutomation audit & retention platform

    Built the service plus reusable Spring Boot, Go, and C# integrations, so teams could adopt it through an API or Kafka.

  5. 05 / 06

    Launch

    Prepare rollout, rollback, documentation, and support.

    In the workLegacy platform modernization

    Rolled back a release that reproduced a legacy timeout, removed unnecessary SQL joins, and re-released it within days.

  6. 06 / 06

    Learn

    Check the outcome and let the evidence shape the next decision.

    In the workAutomation audit & retention platform

    A late-found data-routing problem taught me to set recurring checkpoints with the teams that own critical dependencies.

Selected work

2 case studies · 2 project notes

PrototypeFirst place in an internal innovation competition · 2025

Governed vulnerability remediation

Fixing routine security findings had become repetitive, labor-intensive work that pulled engineering time away from products and platforms.

My role
Came up with the project, formed a three-person team, set the scope, and built most of the working prototype in Go.
Key decision
High and critical findings got an immediate merge request; lower-severity fixes were batched to keep review manageable. Nothing merged without a person’s approval.
Outcome
First place in an internal innovation competition. It ran end to end on mocked findings and a test repository and was not developed further.
Read the case study
ProductionIn production since about May 2025

Automation audit & retention platform

When an internal automation incident was investigated, the logs needed to reconstruct it had already expired. Teams had no durable, consistent execution history.

My role
Owned the service from discovery and design through architecture review, build, release, and support, then added retrieval APIs and a UI.
Key decision
A common required schema with a flexible field for team-specific context, accepted through an API, Kafka, or ready-made Spring Boot, Go, and C# integrations.
Outcome
Adopted by about four teams and ten automation applications, as of May 2026, with seven-year retention through an analytics-owned Snowflake path.
Read the case study
Project note

Legacy platform modernization

Primary implementer, technical lead, and subject-matter expert, including business validation and every release-or-rollback call.

Project note

Multichannel notification service

As a new junior engineer, built most of the shared service, including Slack and email delivery, then released and supported it.

Now

Experience

Dec 2022 – May 2026USAA
Software EngineerInternal platforms, workflow automation, legacy modernization, and developer tooling. Owned shared services end to end and directed two intern cohorts.
Feb – Aug 2022Centuri Group
Application Developer IImplementation and debugging across six internal applications (TypeScript, Vue.js, C#, .NET), plus testing, deployment, and post-launch support for three enterprise go-lives.
EducationB.S. in Computer ScienceMBA in IT Management, expected February 2027

Hiring for work where engineering credibility and delivery ownership both matter? Let’s talk.

joey@joeylking.comLinkedInGitHubRésumé (PDF)