Full-stack product engineering
Responsive, accessible front ends (React, TypeScript) wired to well-designed APIs β shipped end to end.
Currently at Capital One Β· Plano, TX
I'm Brian Ta. A senior engineer who ships across the whole stack β from polished front ends and Java / Spring Boot services to databases, cloud infrastructure, and data & AI pipelines β for payments and banking systems at Capital One, Square and JPMorgan Chase.
Responsive, accessible front ends (React, TypeScript) wired to well-designed APIs β shipped end to end.
Java / Spring Boot is my sharpest tool, alongside Node.js and Python, for resilient REST, gRPC and event-driven services.
PostgreSQL, MySQL, Oracle, MongoDB, DynamoDB, Redis and Elasticsearch β schema design, tuning and migrations.
AWS, Azure and GCP; containers, Kubernetes, Terraform, CI/CD and cost-aware architecture.
Batch and streaming pipelines with Kafka, Spark and Airflow feeding warehouses and analytics.
LLM-powered features, retrieval (RAG), embeddings and model-serving integrated safely into production systems.
Representative problem areas from my career. Details are kept general to respect employer confidentiality.
Problem: Payment volume had to grow without sacrificing correctness or latency.
Built: Idempotent Java / Spring Boot services with strict transactional consistency and safe retries.
Problem: Users needed fast, clear visibility into money movement.
Built: React / TypeScript front ends over typed APIs with real-time updates and accessible design.
Problem: Risk teams needed early, explainable signals.
Built: Streaming features and ML-scored decisions feeding rules with full audit trails.
Problem: Legacy infrastructure was slow to change and costly to run.
Built: Containerized services on AWS with Terraform, autoscaling and automated deployments.
Problem: Money movement needed a trustworthy, auditable source of truth.
Built: Double-entry ledger with immutable entries, balance checks and settlement jobs.
Problem: Internal teams lost time searching docs and runbooks.
Built: Embedding-based search plus an LLM assistant with guardrails, citations and evaluation.
Problem: Teams couldn't trust or easily query their data.
Built: Airflow-orchestrated ELT into a warehouse with quality checks and lineage.
Problem: Ops teams relied on manual scripts and spreadsheets.
Built: Self-service web apps with role-based access, workflows and audit logging.
Problem: Tightly coupled services made changes risky.
Built: Kafka-based events with the outbox pattern, schemas, replay and dead-letter queues.
Problem: Slow, manual releases made delivery risky.
Built: Automated build, test and deploy pipelines with quality gates and safe rollouts.
Problem: Incidents were noisy and slow to diagnose.
Built: Distributed tracing, dashboards and SLO-based alerting tied to customer impact.
Problem: Peak traffic stressed critical queries and services.
Built: Query and index tuning, caching, load testing and graceful degradation.
I start with the real goal and constraints before choosing any tool or pattern.
Incremental delivery, feature flags and fast feedback keep risk low and momentum high.
I measure, monitor and improve β the work isn't done until it runs well.
JavaSpring BootSpring CloudSpring SecurityNode.jsPythonRESTgRPCGraphQL
ReactTypeScriptJavaScriptAngularNext.jsHTML / CSSTailwindAccessibility
PostgreSQLMySQLOracleSQL ServerMongoDBDynamoDBRedisElasticsearch
AWSAzureGCPDockerKubernetesTerraformJenkinsGitHub Actions
KafkaSparkAirflowdbtSnowflakeBigQueryETL / ELT
LLMsRAGEmbeddingsVector DBsscikit-learnPyTorchModel serving
JUnit 5MockitoTestcontainersCypress / PlaywrightMicrometerGrafanaTracing
System designMicroservicesEvent-drivenSecurityAgileCode reviewMentoring
Open to conversations about engineering, systems, and new opportunities.