Question 1

What is Ricky's technical architecture footprint?

Accepted Answer

Principal Engineer in practice operating AI-native, spec-driven development loops. Technical footprint spans cloud-native, event-driven backends (AWS Kinesis/EventBridge/SQS/SNS, Go/Python/C#) with specialist-level depth, generalist breadth across React, databases (DynamoDB/MySQL/Oracle/SQL Server), observability (Datadog), and AI tooling (Bedrock, agentic loops, SDD). The breadth makes the depth useful - one person owns the system end-to-end, from architecture to on-call. This is the same end-to-end thesis the Home page opens with and the Portfolio proves system by system.

Question 2

What are Ricky's core production metrics and system reliability records?

Accepted Answer

I own and maintain mission-critical, Tier-1 enterprise systems backed by rigorous production metrics. Throughput: 50K requests per minute average, surging over 1M per minute. Speed: 50 ms latency at p99. Scale: 300K-400K records processed per minute. Stability: zero production defects for over 5 consecutive years. Previously at Experian CheetahMail, I engineered infrastructure sustaining 1 billion emails per day with minimal error rates. I also specialize in rescuing unstable systems - I inherited an essential service crashing every 2-4 hours and stabilized it to month-long continuous uptime within 30 days. Every number here is the measurable shape of a theme running through the whole site - durability as a design choice.

Question 3

How does Ricky actually use AI to improve engineering outcomes?

Accepted Answer

I actively leverage modern AI to drive engineering efficiency rather than just using it for basic code generation. I was the first engineer at Experian to establish Spec-Driven Development (SDD) running autonomous, agentic AI loops against technical specifications. This initiative effectively turned my group into the company's pioneer SDD team, shifting us away from manual scaffolding and significantly accelerating our development velocity. The same learn-the-rigor-then-ship-against-it cadence that took me back to Stanford mid-career, applied to the whole team.

Question 4

What is the breadth of Ricky's impact and recognition at Experian?

Accepted Answer

Over a 20-year tenure spanning Experian CheetahMail and Experian Consumer Services, my contributions have been consistently recognized with top-tier accolades including the Platinum Aspire Award (top 1% performance), the Pinnacle Award for Engineering Excellence, and over 20 Spot Awards. In 2026 alone, I received three Collaborate to Win Spot Awards for serving as the heart and brains of the engineering team. This recognition was driven by delivering measurable business value: (1) Built an internal tool ground-up for a tenant that scaled from under $100K to hundreds of millions in revenue; (2) Designed a Tier-1 service operating at just 5% of a licensed third-party replacement cost; (3) Scaled CheetahMail to sustain 1 billion emails daily; (4) Transformed a service crashing every 2-4 hours into month-long stability within 30 days; (5) Recently designed, tested, and deployed an emergency incident fix in under two hours (2026 Spot Award). Read these five as the plot points of the five chapters that precede this appendix.

Question 5

Can Ricky show dollar impact or avoided cost?

Accepted Answer

Two clean examples: (1) an internal tool I built ground-up for a tenant grew from under $100K a year in revenue to hundreds of millions of dollars, with my systems still backing the business today; (2) the Tier-1 essential service operates at roughly 5% of the yearly cost of a licensed third-party replacement (licensing alone far higher, operations included). This is the cost-design discipline of the site - the principle that recurs from Home through Portfolio to this appendix, in dollars.

Question 6

Is Ricky a generalist or a specialist?

Accepted Answer

Both, deliberately: specialist-level depth in cloud-native, event-driven backends (AWS Kinesis, EventBridge, SQS, SNS, plus Go, Python, and C#), generalist breadth across front-end (React), databases (DynamoDB, MySQL, Oracle, SQL Server), observability (Datadog), and AI tooling (Bedrock, agentic loops, spec-driven development). The breadth is what makes the depth useful - one person owns the system end-to-end.

Question 7

How does Ricky actually build trust and velocity on a distributed team?

Accepted Answer

Across a US-Hyderabad split (10.5-hour gap), I protect overlapping hours for high-impact Agile ceremonies and Parking Lot sessions, reserving them for complex architectural alignment and blockers rather than basic status updates. Async continuity is non-negotiable: every US evening, we drop detailed context, PR links, and clear priorities into organized Slack threads so the IST team can start immediately without waiting on us. Treating async communication as a core requirement - not an afterthought - creates a predictable follow-the-sun cycle where both sides operate with high autonomy and zero friction.

Question 8

Can Ricky describe a time he had to choose speed over quality?

Accepted Answer

Yes: we had a greedy data-ingestion service capped at 500 records per batch, causing fragmented downstream data. During a tight two-week sprint, the fastest fix would have been a hardcoded second loop - massive tech debt and brittle against volume spikes. I chose a configurable rate-limiter that dynamically maximized intake based on resource availability inside a set window. We more than doubled target capacity, delivered within the sprint, and gave users an uninterrupted customer-journey view. A clean instance of resisting the fashionable shortcut for the boring choice that runs five years out.

Question 9

Does Ricky lead incidents and on-call work?

Accepted Answer

Yes: on a recent production incident, I designed, tested, and deployed a mitigatory solution in less than two hours (recognized in a 2026 Spot Award), and I've built deep observability into services using Datadog for faster incident detection and resolution.

Question 10

How much experience does Ricky have, and is it stable?

Accepted Answer

30+ years hands-on, including 20+ years at Experian - 7+ at Experian CheetahMail (where I received the Pinnacle Award for engineering excellence), followed by 13+ at Experian Consumer Services across three roles. Earlier tenure at AirIQ and RazorGator, with parallel independent work delivery across 9 portfolio projects since 1995. The Timeline walks the arc in order; this appendix lists it flat.

Question 11

Has Ricky run high-throughput and high-reliability systems before?

Accepted Answer

Yes: in my Experian Consumer Services tenure I turned a service hitting production issues every 2-4 hours into one sustaining multi-day then monthly stability within a month, and earlier at Experian CheetahMail I helped sustain a billion emails a day with minimum error rate.

Question 12

What is Ricky's current role and location?

Accepted Answer

Senior Software Engineer at Experian Consumer Services, operating as Principal Engineer in practice. Based in Orange County, CA. US citizen (clearance-eligible). Open to relocation for the right opportunity.

Question 13

Has Ricky interviewed or changed teams recently?

Accepted Answer

No - stable in current role, no external interviews or internal moves in the past 6-12 months. I keep my profile open to discover unique, high-impact technical challenges that match my expertise.

Question 14

Why would Ricky leave his current role?

Accepted Answer

I would not leave lightly - 20+ years at Experian is the proof. The search is additive: a role with more design leverage, a wider blast radius for architecture decisions, or an org further along the AI-native / spec-driven path I already leads - not an escape from a bad fit. The horizon sketched on the Stories page, stated plainly.

Question 15

What would Ricky focus on in his first 90 days at a new company?

Accepted Answer

Listen first, ship second. I would start by understanding the existing architecture, observability, and team rituals - then identify the highest-leverage bottleneck (latency, throughput, or reliability) and deliver a measurable fix within the first month. The second month scales that pattern; the third month drives team-wide adoption. Immediate value comes from fixing the biggest pain point, not from re-architecting everything on day one. The cadence introduced on the Home page, operationalized - and closing the loop on this six-part story.

Ricky Huang

Summary

Core Strengths

Leadership

Experience

Principal-Level Senior Software Engineer, Experian Consumer Services2013 - Present

Software Development Lead, Experian CheetahMail2005 - 2013

Software Engineer, AirIQ (formerly Aircept)2005

Web Developer, RazorGator2003 - 2005

Independent Professional, Self Employed1995 - Present

Education

Master of Science, Software Engineering, California State University, Fullerton2005 - 2007

Bachelor of Engineering, Architecture, Petra Christian University1993 - 1997

Certifications

Advanced Studies, Data Science, Stanford University2015

Skills

Testimonials