RYAN ZERNACH

Senior AI Systems Engineer

Ryan_Zernach_2025_Senior_AI_Systems_Engineer_Remote_United_States

BUILDING RELIABLE

HEALTHCARE AI

SCALING PRODUCTION

LLM SYSTEMS

ENGINEERING TRUSTED

AI INFRASTRUCTURE

DELIVERING INTELLIGENT

PATIENT IMPACT

🌱 Landscape Supply: Checkout Is The Easy Part

Landscape Supply was built around an important operational reality: preventing costly delivery mistakes before they happen. I architected and shipped the platform across a TypeScript React Native app and a TypeScript Express backend, then layered in AI automation for scheduling, payments, and customer coordination. I approached it as operational software, not just eCommerce, because field teams need precision more than polished marketing copy. The work pushed me, and that was exactly the point: every release had to earn trust in real-world execution.

Related Links
Visit Landscape Supply Website
Download on Apple App Store
Download on Google Play Store
🌱 Landscape Supply: Checkout Is The Easy Part

Landscape Supply presentation

🧱 What I Built

Landscape Supply is an operations-heavy commerce platform where order quality matters more than vanity conversion metrics. I owned the build end to end in TypeScript, across product design, frontend architecture, backend workflows, AI-assisted coordination, communications infrastructure, and growth systems. The result is one connected experience that helps buyers discover materials, ask better questions, schedule correctly, pay quickly, and receive cleaner handoffs into fulfillment.

⚙️ Technical Spine

TypeScript everywhere: React Native (iOS, Android, web), Express services, queue workers, LLM workflows, Twilio VOIP, OpenAI voice, IMAP and POP email handling, Stripe, and campaign scheduling logic. One typed system from interface to background jobs.

🤝 Ownership Model

End-to-end ownership with direct feedback loops from real buyers and operations realities.

🧭 How The System Comes Together

The sections below break down full ownership, cross-platform product architecture, automation infrastructure, and communications systems that keep execution clean after checkout.

Full Ownership Without Hand-Off Gaps

One Product Across iOS, Android, and Web

Automation Infrastructure With Guardrails

Communication and Growth As Product Surfaces

🚧 Why This Problem Is Hard

Landscape Supply sits at the intersection of commerce and field operations. Buying material is easy. Delivering the right quantity, to the right location, in the right window, with the right site constraints captured, is the real work. The software has to remove ambiguity before trucks are assigned.

🎯 What I Owned

I owned the build end to end: product direction, UX, frontend architecture, backend orchestration, AI integration, queue-driven workflows, communication systems, and growth automation. That scope let me remove friction across the entire lifecycle instead of optimizing one narrow layer.

📈 What Success Actually Meant

Success was not just more checkouts. Success was fewer preventable mistakes after checkout: cleaner scheduling handoffs, faster clarification cycles, better delivery readiness, and less operational thrash between buyer intent and field execution.

🧠 Confident Build, Humble Posture

I moved quickly and made strong technical bets, but I kept listening to where operations disagreed with product assumptions. That balance mattered: confidence drove execution speed, humility kept the system honest when real-world constraints showed up.

🔍 Deep Dive: Product and Operations

This section covers the customer-facing product surface, full-stack implementation choices, TypeScript rationale, field constraints, and where AI created practical leverage.

Core Product Surface

Buyer confidence must come before buyer conversion

What I Built Across The Stack

A unified implementation across product and engineering

Why TypeScript Is My #1 Language

Safe and maintainable under pressure, while still fast to ship

Operational Constraints

Delivery software has to model physical jobsite reality

What Makes It A Strong AI Fit

This category combines repetitive communication with structured ambiguity

📡 Communication Layer As The Multiplier

A major part of this project was communications infrastructure because this category depends on follow-up quality as much as interface quality. I built voice workflows, email handling, and automation logic in TypeScript on the TypeScript Express side, wired to the TypeScript React Native client, so the product could behave like an active coordinator instead of a passive storefront.

Voice, Email, and Follow-Up

The communication layer was part of the core product, not an add-on

Queues, LLMs, and Automation

The AI layer had to support real operations, not only demos

What The Product Is Really Optimizing

The goal is not only order volume; it is cleaner execution after the order

Marketing, Growth, and Product Positioning

Growth was part of the build, not work handed off to a separate team

Portfolio Fit

Landscape Supply represents the kind of engineering work I care about most: building software that has to survive real operations, not just demos. It combines a TypeScript React Native frontend, a TypeScript Express backend, and the connective tissue of scheduling, communication, and fulfillment in one disciplined system.

How I Work

My approach is straightforward: take ownership, model the system clearly, and reduce avoidable friction. TypeScript remains my favorite language because it keeps high-velocity work honest. It gives me confidence to move fast, and enough structure to stay accountable when complexity grows.