A closer look / 03

Hands-on technical leadership

Close tothe code.

Architecture / Implementation / People

The work behind it

The practice

Krystian Flores
Senior Software Engineer / Technical Lead

Complete résumé

Technical leadership that stays close to the code.

When the original technical lead left the earlier Admissions redesign, I took technical ownership of the Gatsby/Drupal implementation. I mapped editor-managed paragraph types to reusable frontend components and stabilized delivery. Today, I lead through implementation, code review, documentation, and mentoring; my supervision of two developers was a past responsibility.

Selected project notes

In practice.

Public products, internal systems, and prototypes, with my part in each.

01Historical university web workHistorical

Arizona Admissions: Gatsby / Drupal

EditorDrupal paragraphs
Content APIJSON:API + GraphQL
FrontendGatsby components
Historical architecture, illustrated from the project description. The earlier implementation is no longer live; today's university site is a later iteration.

My partFrontend technical lead

Owned frontend development for an earlier Gatsby/Drupal Admissions redesign after a technical-lead transition. This implementation is no longer live.

  • Owned the experience between the shared university header and footer.
  • Mapped Drupal paragraph types to reusable Gatsby and GraphQL-powered components.
Read the project notes

02University team collaborationCollaboration

Arizona + CWS: Shared Drupal Components

University team + CWS

arizona.eduadmissions.arizona.edu

Together under arizona.edu

BuildDrupal SDC
Test & documentStorybook
Explanatory diagram of the collaboration: Drupal Single Directory Components with Storybook for each component. Not an employer screenshot.

My partContributing team member

Partnered with CWS as part of the university team on the arizona.edu and admissions.arizona.edu redesign, bringing both under arizona.edu with Drupal Single Directory Components and Storybook.

  • Collaborated with CWS on the redesign of arizona.edu and admissions.arizona.edu.
  • Used Drupal Single Directory Components, with Storybook for each component for testing and documentation.
Read the project notes

03Public AI productShipped

MetaSculpt AI

MetaSculpt interface showing an action brief, visibility chart, account navigation, and login surface
Action brief: crawl findings become suggested fixes. I owned the crawler and reporting logic; the product shipped without gaining traction.

My partCo-Founder (technical lead) / 2024 - 2025

Co-founded and shipped a public product combining prompt tracking, citation capture, crawl analysis, weekly reports, and Schema JSON generation and validation.

  • Led product architecture, AI workflow design, frontend implementation, crawler and report logic, documentation, and code review in a two-person company.
  • Designed the Crawl → Generate → Validate → Fix flow and kept crawler and generator responsibilities separate.
Read the project notes

04Private AI governance workflowShipped internally

Logo Proposal Validation Agent

ProposalPolicy checksRetrieved guidanceHuman decision
ApproveDenyClarifyEscalate
Internal logo-review workflow I designed. Deterministic checks and retrieved policy context support the reviewer; ambiguous cases stay in human review.

My partTechnical lead · AI product architecture / 2024 - Present

Designed and shipped an internal logo-review workflow combining deterministic policy checks, retrieved guidance, structured output, and human review.

  • Owned project inception, architecture, development, publishing, documentation, and stakeholder coordination.
  • Routed clear cases through approve or deny paths and unclear cases through clarification or escalation.
Read the project notes

Connect the dots

Looking for a technical lead who can make architecture decisions and still ship?

View complete experience