Bryant Vu
Software Developer
7+ years exp
8+ years ML exp
Rust
Python
JavaScript
TypeScript
Node JS
C#
Go
Security & Auth: 6/10
API Design: 5/10
Scalability & Performance: 5/10
Active 3 days ago
+1 (408) 4717210 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Full-stack backend engineer working at a senior level with a strong practical focus on blockchain smart contracts and production web APIs. The strongest proven skill is building correct and well-tested blockchain contracts and clients as shown by the CosmWasm contract (contracts/soccer-betting-contract/src/contract.rs and tests) and the Solana Anchor program and client (solana/programs/.../src/lib.rs and apps/solana-web/lib/*). Public code lacks evidence of production-grade observability (centralized metrics/alerts, correlation ids), systematic load testing artifacts, and an evolution history of complex relational schema migrations.
Technical skills
Rust• Senior
Python• Senior • 7y+
JavaScript• Middle • 7y+
TypeScript• Middle • 7y+
Node JS• Senior • 6y+
C#• Middle • 3y+
Go• Middle
Python
Django
Django REST Framework
Celery
Boto3
FastAPI
Databases
PostgreSQL• 3y+
RabbitMQ• 3y+
Redis• 3y+
AI/ML
Prompt Engineering
RAG
LLM• 8y+
AI Agents• 3y+
Frontend
Next.js
RxJS
React.js• 6y+
Vue.js• 3y+
DevOps
Docker Compose
AWS Fargate
GitHub Actions
IaC
Containers
Rest API• 8y+
AWS• 3y+
CI/CD• 3y+
Docker• 3y+
Kubernetes• 3y+
Mobile
React Native
Timeline
Senior Software Engineer - Full Stack, AI
•
Senior
Loadstar Sensors
•
Full-Time
Led engineering for StockVUE, an AI- and IoT-enabled inventory monitoring platform connecting edge devices, cloud services, and web applications. Built Python- and LLM-driven diagnostic workflows for device log triage, test generation, and technical documentation with human review. Developed AI-assisted telemetry analysis, improved unattended device reliability with watchdog recovery, and delivered provisioning, OTA, and remote management workflows for distributed Raspberry Pi deployments. Mentored an 8-member product and engineering team across AI, backend, frontend, and edge software delivery.
Python
LLM
Go
Senior Software Engineer - Full Stack, AI
•
Senior
Confidential
•
Full-Time
Built AI-powered features and the full-stack foundation for a data-intensive enterprise platform. Designed high-concurrency Node.js, C#, and .NET backend services with separated API, business, and data layers, and introduced RabbitMQ-based asynchronous processing for long-running and event-driven jobs. Implemented REST APIs backed by PostgreSQL and Redis with caching and asynchronous data access, and deployed/operated distributed workloads on AWS with Kubernetes. Built frontend applications with TypeScript plus AngularJS and Vue.js, containerized services with Docker, strengthened CI/CD, and supported production troubleshooting while mentoring engineers.
Node JS
C#
Rest API
RabbitMQ
PostgreSQL
Redis
TypeScript
Vue.js
Docker
CI/CD
AWS
Kubernetes
LLMsince 2023
AI Agents
Senior Software Engineer - Full Stack
•
Senior
Futurewei Technologies, Inc.
•
Full-Time
Worked on H5-to-Huawei Quick App conversion tooling that helped migrate existing web applications into Huawei’s mobile ecosystem without full rewrites. Built Node.js services and REST APIs for conversion configuration, validation, and integration, and created developer-facing and user-facing tools with React and JavaScript to connect conversion workflows with backend services and mobile behavior. Adapted H5 applications for mobile execution, addressing navigation, authentication, API integration, lifecycle handling, and device interaction differences. Supported integrations for 50+ content partners and traced defects across frontend, backend APIs, mobile behavior, and platform integration to production-ready releases.
Node JSsince 2020
Rest API
React.js
JavaScript
Application Developer, Co-Founder
•
Executive
Steps Mobile Inc.
•
Cofounder
Co-founded a social fitness and rewards mobile application and owned its technical direction from backend architecture through production delivery. Led a cross-functional team across backend, frontend, Android, and product design, translating product goals into engineering priorities and release plans. Designed backend architecture and REST APIs for authentication, user activity, and rewards, separating business logic from the Android client to reduce coupling between product layers. Coordinated debugging, testing, and releases with stakeholders and contributed to Android/Java flows, especially authentication and account-related features.
Rest APIsince 2018
Software Engineering Intern - Full Stack
•
Junior
Aria Communications
•
Internship
Supported senior engineers on a client-facing production codebase, working on requirements, testing, debugging, and targeted changes. Assisted with client features using Java, JavaScript, HTML, CSS, and Android, translating requested behavior into UI updates, application logic, and test cases. Reproduced and narrowed customer-reported defects across frontend, application logic, and Android layers, then validated fixes against real client scenarios. Helped with client integrations while learning how to balance requested functionality with existing architecture and release timelines.
JavaScriptsince 2019
Senior Backend Developer
Confidence: High Generalist
Full-stack backend engineer working at a senior level with a strong practical focus on blockchain smart contracts and production web APIs. The strongest proven skill is building correct and well-tested blockchain contracts and clients as shown by the CosmWasm contract (contracts/soccer-betting-contract/src/contract.rs and tests) and the Solana Anchor program and client (solana/programs/.../src/lib.rs and apps/solana-web/lib/*). Public code lacks evidence of production-grade observability (centralized metrics/alerts, correlation ids), systematic load testing artifacts, and an evolution history of complex relational schema migrations.
API Design
5/10
How well APIs are designed
APIs are designed for multiple surfaces (Django/DRF, smart-contract Execute/Query messages, Solana client) with consistent request/response patterns, but versioning/idempotency strategies and explicit error contracts across services are minimal.
Evidence
the-phoenix/TinPennyVideos/app/TinPennyBackend/settings.py: REST_FRAMEWORK configuration (pagination, auth classes)
the-phoenix/rust-soccer-betting-platform/contracts/soccer-betting-contract/src/contract.rs: execute/query + ExecuteMsg/QueryMsg driven contract API handlers
the-phoenix/rust-soccer-betting-platform/apps/solana-web/lib/anchor-client.ts: queryConfig/queryMarket/queryBettor client methods
Data Layer & Database
4/10
Working with databases
Data layer shows correct use of Django models and migrations and careful state handling in contract storage, but lacks evidence of multi-stage schema evolution, advanced transaction isolation tuning or hand-optimized SQL.
Evidence
the-phoenix/TinPennyVideos/app/media/models.py: Django models with FK relations and custom S3PathField
the-phoenix/TinPennyVideos/app/media/migrations/0001_initial.py: initial schema migration
the-phoenix/rust-soccer-betting-platform/contracts/soccer-betting-contract/src/state.rs and src/contract.rs: persistent contract state and load_market usage
Scalability & Performance
5/10
Handling load and speed
Several scalability patterns are present (Celery tasks, SQS/S3 pagination, presigned URLs, TPS-aware BCH generator) and client-side batching, but no evidence of measured load tests or advanced cache-invalidation strategies.
Evidence
the-phoenix/TinPennyVideos/app/media/utils.py: SQS retrieval, S3 paginator helpers and presigned URL generation
the-phoenix/TinPennyVideos/app/TinPennyBackend/settings.py: CELERY and SQS-related settings
the-phoenix/bch-batch-transaction-generator/src/start.ts: TPS-limited transaction generator and RxJS orchestration
System Architecture
5/10
Overall system structure
Repository shows clear module/service separation (Django backend, React frontend, Celery workers, CosmWasm and Solana programs) and reasonable folder organization, but no explicit service decomposition trade studies or inter-service contracts beyond code-level clients.
Security & Auth
6/10
Protecting data and access
Good security practices are present: input validation in contracts, explicit auth checks, JWT in API settings, and validators on model fields; however runtime secret management and dependency-vulnerability evidence are limited.
Evidence
the-phoenix/rust-soccer-betting-platform/contracts/soccer-betting-contract/src/contract.rs: ensure_admin, validate_text, outcome checks and overflow-aware arithmetic
the-phoenix/TinPennyVideos/app/TinPennyBackend/settings.py: JWT_AUTH configuration and AUTH_USER_MODEL
the-phoenix/TinPennyVideos/app/media/models.py: custom S3PathField with validator (s3_path_validator)
Reliability & Observability
4/10
Stability and monitoring
Some reliability work exists (try/except around AWS calls, Celery for background processing, unit/integration tests for contracts), but structured observability (metrics/alerts, correlation ids), systematic retries with backoff, and graceful shutdown patterns are not broadly visible.
Evidence
the-phoenix/TinPennyVideos/app/media/utils.py: exception handling for S3/SQS operations and logging
the-phoenix/TinPennyVideos/app/media/tasks.py: Celery tasks and use of logger
the-phoenix/rust-soccer-betting-platform/contracts/soccer-betting-contract/src/tests.rs: extensive wasm contract tests exercising flows
Verified artifacts
Expertise
Python• Middle
Rust• Senior
Messaging & Real-time• Middle
Microservices & API Architecture• Middle
Industries
Blockchain & Crypto• Senior
Internet Services• Senior
Technologies
Go• Middle
Rust• Senior
C#• Middle • 3y+
PostgreSQL• 3y+
Redis• 3y+
Django REST Framework
Oracle• mentioned only
Rest API• mentioned only
Recommendations
- Develop and maintain financial/blockchain backends and smart-contract systems (CosmWasm/Anchor) including tests and client integrations.
- Build video and media backend services integrating S3, presigned URLs, Celery workers and SQS for asynchronous processing at moderate scale.
- Implement API-driven systems that require careful correctness and asset handling such as payout/refund flows, where precise edge-case handling and tests are required.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium App Engineer
App engineer (mid-level) focused on TypeScript React frontends and blockchain client tooling. The strongest proven skill is building blockchain-integrated client code and transaction flows as demonstrated by the Solana client and transaction logic in the anchor and execute client modules. Public code does not show extensive component-system design, accessibility engineering, measured performance audits, or advanced async state machines.
UI Component Architecture
2/10
How interface parts are built
Minimal custom component architecture evidence; styling is handcrafted but component boundaries and composition patterns in React are not present in the analyzed human-authored files.
Responsive & Cross-browser
3/10
Works on all screens and browsers
Responsive CSS is present with media queries and fluid typography, but no advanced cross-browser feature detection or explicit RTL/i18n patterns are shown.
Performance Optimization
3/10
Speed of the interface
Some pragmatic performance and concurrency choices appear in client code (parallel queries, careful transaction confirmation), but there is no measured optimization, bundle analysis, or advanced runtime tuning.
Accessibility & Semantics
1/10
Usable for everyone
Very little accessibility-specific work is visible; no ARIA, focus management, keyboard handling, or CI a11y linting evidence in the human-authored files.
State Management & Data Flow
3/10
Managing data in the app
Server-state and data-flow code shows pragmatic error handling and fallback responses, but lacks advanced async discipline like request cancellation, optimistic updates with rollback, or state machines.
UX & Visual Polish
4/10
Look and feel quality
High visual polish in authored CSS with thoughtful components, responsive layouts, and states like empty-state and status-pill, but interactive UX patterns and progressive enhancement are not deeply evidenced.
Expertise
React• Middle
Modern Web Frameworks• Middle
Industries
Blockchain & Crypto• Middle
Sports• Middle
Technologies
JavaScript• Middle • 7y+
TypeScript• Middle • 7y+
Node JS• Senior • 6y+
Vue.js• 3y+
Next.js
RxJS
React.js• 6y+
Tooling• mentioned only
Recommendations
- Develop end-to-end Web3 frontends that need robust on-chain transaction handling and client-side parsing for Solana and CosmWasm networks.
- Implement read-side dashboards and tooling where careful binary parsing and confirmed transaction flows are required.
- Maintain or extend blockchain integration layers and TypeScript client SDKs (wallet adapters, transaction builders, account decoders).
- Avoid tasks that require mature design-system ownership or audited accessibility compliance until more evidence of a11y and component architecture exists.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle DevOps Engineer
Confidence: Medium CI/CD Engineer
A middle-level DevOps/CICD engineer experienced building containerized Python services and deploying them to AWS Fargate with Terraform and GitHub Actions. The strongest proven skill is building end-to-end deploy pipelines and cloud infra-as-code as shown by fastapi--ecs-terraform/.github/workflows/deploy.yml and fastapi--ecs-terraform/terraform/main.tf. There is little evidence of advanced progressive delivery, SLO-driven alerting, remote terraform state locking, or mature security-hardening in the public code.
CI/CD Pipelines
3/10
Automated build and deploy
Basic but functional CI/CD automation for building, publishing and deploying container images with GitHub Actions; lacks advanced pipeline engineering patterns such as reusable workflows, signing, matrix builds or deployment gates.
Evidence
fastapi--ecs-terraform/.github/workflows/deploy.yml: workflow runs terraform init/validate/apply and builds/pushes Docker images
Infrastructure as Code
3/10
Managing servers with code
Practical Terraform usage to provision ECS, ECR, IAM and CloudWatch resources, showing end-to-end infra-as-code, but missing remote state, modules, locking or multi-environment separation and no explicit state migration patterns.
Evidence
fastapi--ecs-terraform/terraform/main.tf: aws_ecr_repository, aws_ecs_cluster, aws_ecs_service, aws_ecs_task_definition
fastapi--ecs-terraform/terraform/outputs.tf: exports for ecr_repository_url, ecs_cluster_name, ecs_service_name
Containerization & Orchestration
3/10
Working with containers
Containerization and orchestration for Fargate is implemented (Dockerfiles, ECS task defs and log configuration) but lacks multi-stage optimizations, non-root user hardening, readiness/liveness probes, resource justification beyond basic CPU/memory and Kubernetes-level resilience features.
Evidence
fastapi--ecs-terraform/app/Dockerfile: Python app image and uv runtime usage
fastapi--ecs-terraform/terraform/main.tf: aws_ecs_task_definition container_definitions with cpu/memory and awslogs configuration
Observability & Monitoring
2/10
Watching system health
Minimal observability as code exists (CloudWatch log group and container log driver), but there are no SLOs, burn-rate alerts, dashboards as code, structured tracing or alert routing present.
Evidence
fastapi--ecs-terraform/terraform/main.tf: aws_cloudwatch_log_group.app and container_definitions logConfiguration
Reliability & Incident Response
2/10
Keeping systems up
Some application-level reliability patterns exist (Celery tasks, deletion hooks) and deployment automation is present, but there are no explicit progressive delivery strategies, rollback gates, runbooks, postmortems or chaos/DR rehearsals.
Evidence
TinPennyVideos/app/media/models.py: Video.delete triggers Celery tasks and stream cleanup
fastapi--ecs-terraform/terraform/main.tf: aws_ecs_service.app with desired_count and no deployment strategy configurations
Cloud & Cost Optimization
2/10
Smart use of the cloud
Cloud usage demonstrates basic cost control decisions (Fargate with small CPU/memory), but lacks autoscaling, spot/eviction strategies, rightsizing analytics or least-privilege service identity patterns.
Evidence
fastapi--ecs-terraform/terraform/main.tf: aws_ecs_task_definition cpu = "256", memory = "512" and launch_type = "FARGATE"
TinPennyVideos/app/media/utils.py: boto3 usage for S3/SQS integration
Expertise
Infrastructure as Code• Middle
Cloud Platforms & Architecture• Middle
Industries
Media & Entertainment• Middle
Technologies
Containers
IaC
Python• Senior • 7y+
Docker Compose
GitHub Actions
FastAPI
Django
AWS• 3y+
Celery
Boto3
AWS Fargate
Rest API• mentioned only
Recommendations
- Build reusable, parameterized Terraform modules and add a remote state backend with locking (S3 + DynamoDB) to support multi-environment deployments.
- Enhance CI/CD pipelines with plan gates, terraform plan artifact review, canary or progressive deployment steps and artifact signing for supply-chain assurance.
- Add observability and reliability-as-code: SLOs/alerts, dashboards as code, structured tracing and automated runbooks for common incidents.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: