Vetted Amazon SNS Professionals

“Front-end engineer with experience at Optum and Wells Fargo maintaining internal React/Angular component libraries and design-system-aligned UI modules used across multiple apps. Known for stabilizing shared libraries via semantic versioning, Jest test automation, and high-quality documentation, plus measurable performance wins (≈40% faster dashboard loads) through profiling-driven React and API optimizations.”

“JavaScript full-stack engineer with experience at EY building secure, cloud-ready React/Node.js applications on AWS and currently at startup Juego Juegos owning the AWS backend and CI/CD via AWS Amplify. Demonstrated impact through performance tuning of a React analytics dashboard (reduced initial load time ~20%) and resolving real payment failures by debugging Stripe 3DS flows and updating AWS Lambda plus frontend error handling.”

“Backend/data engineer focused on production Python and AWS: built FastAPI REST services and a containerized ECS Fargate + Lambda architecture deployed via Terraform/CI-CD. Strong in data engineering (Glue/S3/Parquet/RDS) and operational reliability (CloudWatch/SNS, retries, schema-evolution handling), with experience modernizing legacy SAS reporting into Python microservices using feature flags and parity validation.”

“Backend engineer who owned an order management API built with Python/FastAPI and PostgreSQL, integrating payment and shipping providers with strong reliability patterns (idempotency, async workers, retries/backoff, circuit breakers). Experienced deploying services to Kubernetes using a GitOps model with ArgoCD (auto-sync, self-healing, pruning, rollbacks) and building high-volume Kafka streaming pipelines. Has also supported phased cloud-to-on-prem migrations with a focus on security monitoring/SIEM log continuity.”

“Founding engineer who built a multi-tenant AWS backend from scratch focused on ultra-fast, configuration-driven client onboarding and low operational cost. Automated tenant provisioning/deployments with Terraform + GitHub Actions (new client infra in ~13 minutes) and scaled to 62 production clients handling ~75k requests/day without a major rewrite. Hands-on with migrations (DynamoDB->MongoDB), reliability/observability, and performance tuning (indexes, Redis, queueing, connection management).”

“AI engineer at Cleveland Clinic building production LLM/NLP systems for radiology documentation, focused on HIPAA-aware, real-time performance across ~298 campuses. Re-architected infrastructure with AWS event-driven services to handle scaling and improved SLA compliance ~40%, and complements this with a personal multi-agent debate system (CrewAI) using local Llama/Mistral plus rigorous evaluation (A/B tests, red teaming, observability).”

“Software engineer with healthcare domain experience (patient monitoring and provider systems) who improves reliability and performance in complex React/Flask applications. Led API standardization for shared internal React utilities using an RFC + deprecation strategy, and optimized a live WebSocket dashboard to handle 3000+ concurrent clinics while reducing client CPU usage. Strong in production debugging, data ingestion validation, and operational improvements like structured logging and alerting.”

“Data engineer with healthcare/clinical trial domain experience who owned a 100TB+/month AWS pipeline end-to-end (Glue/S3/Redshift/Airflow) and drove measurable outcomes (20% lower latency, 99.9% reliability, 40% less manual reporting). Also built production data services and API-based ingestion on GCP (Cloud Run/Functions/BigQuery) with strong validation, versioning, and safe migration practices, and launched an early-stage RAG solution (LangChain + GPT-4) for researchers.”

“Early-career cloud/appsec-focused engineer with hands-on experience building secure, observable microservice systems on AWS (IAM least privilege, KMS encryption, Secrets Manager, CloudWatch, ALB) and troubleshooting autoscaling-related 500s down to connection pooling issues. Also deployed heavy ML workloads on Kubernetes by decomposing diffusion/transformer services, using workload identity to eliminate static credentials, and maintaining GitOps-style deployment audit trails.”