Jordan Allen

Senior Full-Stack Engineer & Technical Lead

Jordan Allen

I help teams turn ambiguous business problems into shipped software through strong architecture, full-stack execution, and practical product judgment.

I design and build software for complex workflows: AI-assisted sales tools, healthcare scheduling platforms, specialized design calculators, and operational systems used by real teams.

Delivery timeline

Discovery

Architecture

Build

Integrate

Shipped

Architecture notes

  • Modular boundaries
  • Workflow-first data model
  • Observable failure paths
  • Integration constraints mapped early
TypeScriptAIVoiceData

delivery-system.map

Mobile app
API
AI service
Data
Notifications
Team workflow

workflow.service.ts

async function publish(input) {
  validate(input);
  await events.write({
    type: "workflow.shipped",
    source: "portfolio"
  });
}

Selected outcomes

Healthcare scheduling platform

Shipped

AI-assisted sales iOS app

Shipped

Design calculator suite

Shipped

Core strengths

Where I add the most value.

The throughline in my work is practical ownership: making the problem clearer, choosing an architecture that fits, and carrying the product through delivery.

01

Clarify ambiguous work

Turn loose business goals, legacy behavior, and stakeholder input into a buildable product path.

02

Choose architecture that fits

Separate concerns, preserve important constraints, and avoid complexity that does not serve the workflow.

03

Ship across the stack

Own frontend, backend, data, integrations, deployment, and the practical details that make software usable.

04

Modernize without losing parity

Rebuild older systems into maintainable applications while protecting the behavior teams rely on.

Featured work

Selected projects with architecture, workflow, and delivery weight.

Four projects that show AI workflow development, healthcare modernization, specialized product logic, and full-stack operational software. Confidential work is intentionally anonymized.

Anonymized NDA Case StudyLead Engineer / ArchitectField-tested MVP

Case study 01

AI-Assisted Sales iOS App

Real-time call transcription, document parsing, and contract-field matching for sales teams.

Led architecture and development of a fully functional AI-assisted sales iOS app that combined telephony, real-time transcription, document parsing, and structured field matching to help agents capture contract-relevant information during live calls.

  • Led a small team with QA and PM/engineering support
  • Owned product and architecture decisions end-to-end
  • Built the iOS app, backend, AI/transcription flow, telephony integration, and notifications
  • Revised the call-stream architecture after early testing showed lifecycle/hangup issues
Live call intelligence pipelineField-tested MVP
01

iOS app

02

Voice stream

03

Transcription

04

Extraction

05

Field matching

06

Agent feedback

Read case study+

Overview

Led architecture and development of a fully functional AI-assisted sales iOS app that combined telephony, real-time transcription, document parsing, and structured field matching to help agents capture contract-relevant information during live calls.

Context

The work needed to connect live call behavior, mobile UX, AI transcription, document parsing, and structured business data without adding unnecessary overhead for agents.

My role

Lead Engineer / Architect

Technical approach

I kept the architecture explicit: mobile app state, voice stream handling, transcription, extraction, field matching, and feedback were treated as separate concerns with clear failure modes and practical observability.

Key challenges

  • Early call lifecycle behavior exposed hangup and stream edge cases that required a revised integration path.
  • Short audio chunks and noisy transcripts needed conservative parsing so the product stayed useful in real calls.
  • NDA constraints required keeping the demo abstract while still proving the technical system.

Outcome

Delivered a field-tested, production-ready MVP that combined iOS, telephony, AI transcription, document parsing, and structured field matching. Stakeholders responded strongly to the result and discussed production rollout before the project was paused for business reasons.

Stack

SwiftUICore Data/SQLiteNode.jsExpressTwilio Voice SDKTwilio Media StreamsWebSocketsOpenAI Whisper APIAzure Container InstanceAzure Storage
Production Migration Case StudyArchitect / Lead Software EngineerProduction migration

Case study 02

Healthcare Platform Modernization

Led migration of two production healthcare applications from legacy ASP.NET WebForms / .NET Framework to Blazor Server / .NET 8: a patient appointment-booking platform and a provider scheduling/profile-management system.

  • Migrated two live healthcare workflow applications
  • Apps are used by patients, providers, and admins
  • Legacy applications are being retired
  • Untangled deeply nested generated WebForms code from an older visual-builder style tool
Legacy-to-modern workflow mapProduction migration
Legacy WebForms
Blazor / .NET 8

Patient

Provider

Admin

Read case study+

Overview

Led migration of two production healthcare applications from legacy ASP.NET WebForms / .NET Framework to Blazor Server / .NET 8: a patient appointment-booking platform and a provider scheduling/profile-management system.

Context

Two production healthcare applications needed to move away from older generated WebForms code while preserving critical booking, provider, and admin workflows.

My role

Architect / Lead Software Engineer

Technical approach

I separated domain behavior from UI concerns, rebuilt the scheduling model around clearer concepts, and used the migration to improve responsiveness without losing behavior parity.

Key challenges

  • The legacy code was deeply nested and generated from an older visual-builder style tool.
  • Scheduling and availability rules had to be reconstructed coherently rather than copied as tangled UI logic.
  • The migration had to balance new feature work, parity, time, and budget.

Outcome

The modernized applications improved UX, responsiveness, maintainability, and loading performance while the legacy applications move toward retirement.

Stack

ASP.NET WebForms.NET FrameworkBlazor Server.NET 8DDD-style architecture
Anonymized NDA Case StudySole Architect / BuilderLive version 1

Case study 03

Specialized Manufacturing Design Calculator

Architected and built a web-based design calculator that replaced a spreadsheet-driven process for a specialized manufacturing and training workflow. The app guides users through structured inputs, performs domain-specific calculations, and generates visual diagrams to support estimating, training, and production planning.

  • Replaced a spreadsheet-based workflow with a guided application
  • Built calculation logic and generated visual diagram outputs
  • Worked closely with the domain owner to understand specialized requirements
  • Validated Shopify/theme extension constraints before committing to the implementation path
Spreadsheet-to-guided-app conversionLive version 1
Read case study+

Overview

Architected and built a web-based design calculator that replaced a spreadsheet-driven process for a specialized manufacturing and training workflow. The app guides users through structured inputs, performs domain-specific calculations, and generates visual diagrams to support estimating, training, and production planning.

Context

A specialized workflow lived in a spreadsheet that carried both business logic and training context. The goal was to make the workflow easier to use without losing the spreadsheet's known outputs.

My role

Sole Architect / Builder

Technical approach

I treated the spreadsheet as the source of truth, validated platform constraints early, and built tests around known outputs before expanding the guided app experience.

Key challenges

  • The implementation had to respect platform constraints inside Shopify integration points.
  • The app needed to generate useful diagrams without exposing proprietary formulas or design logic.
  • Domain understanding mattered as much as UI execution because the original workflow encoded specialized judgment.

Outcome

Version 1 is live for select invited users and is being used/demoed while preparing for a broader launch.

Stack

React RouterShopify theme app extensionShopify page integration
Live Public/Personal ProductSolo Full-Stack DeveloperUsed by the team

Case study 04

Laundry Co. Shift Scheduler

Built a production scheduling platform for a real small-business operation, used by managers and staff to manage shifts, time off, shift swaps, weekly hours, and notifications.

  • Managers can create, assign, edit, publish, cancel, and restore shifts
  • Supports standard and recurring schedules
  • Employees can view weekly/monthly schedules
  • Employees can request time off and shift swaps
Operational scheduling surfaceUsed by the team
Read case study+

Overview

Built a production scheduling platform for a real small-business operation, used by managers and staff to manage shifts, time off, shift swaps, weekly hours, and notifications.

Context

A real small-business operation needed a practical scheduling system for managers and staff, with enough workflow coverage to replace manual coordination.

My role

Solo Full-Stack Developer

Technical approach

I built the product as an operational tool first: schedule creation, publishing, employee visibility, requests, swaps, and notifications were designed around repeat use by a working team.

Key challenges

  • Recurring schedules, cancellations, restoration, and weekly hours all needed predictable behavior.
  • Notifications had to support multiple channels without making the workflow noisy.
  • The product needed to stay compact enough for small-business use while covering real scheduling cases.

Outcome

The scheduler is live and used by the business team to manage shifts, time off, swaps, weekly hours, and notifications.

Stack

Next.js 14ReactTailwind CSSshadcn-style componentsNextAuthPostgreSQL/Vercel PostgresDrizzle ORMResend emailWeb Push/VAPID

Approach

Architecture, implementation, and product judgment in one loop.

I work best where requirements are still becoming clear, systems need to fit real operational constraints, and the path from prototype to production matters.

Clarify

Ask the questions that turn ambiguity into concrete workflow, data, and delivery constraints.

Structure

Separate product behavior, integration risk, and UI state so teams can reason about the system.

Ship

Build the working product, verify behavior, and keep the implementation maintainable after launch.

Resumes

Resume versions tailored to senior engineering and technical leadership roles.

Each PDF highlights a different angle of the same experience: senior full-stack product engineering, or technical leadership across architecture, planning, and delivery.

Contact / links

Interested in architecture-heavy product engineering work.

I am interested in senior full-stack, technical lead, and architecture-heavy product engineering roles where judgment and delivery both matter.