Vetted Front End Developers

“Software engineer with experience at PayPal and JPMC building large-scale onboarding/account setup systems using React/TypeScript with Spring Boot/Node microservices and Kafka. Also built an Ignition-based SCADA monitoring tool at Mainspring Energy that became the default for manufacturing/test engineers by aggregating real-time telemetry and historical test data.”

“Backend/data engineer with strong AWS production experience across containers (ECS) and serverless (API Gateway/Lambda/SQS), plus Glue-based ETL to Parquet for Athena/Redshift. Demonstrates hands-on reliability and security depth (Cognito OAuth2/JWT with JWKS rotation, idempotency/DLQs, monitoring) and measurable performance wins (Redis caching + query tuning), along with legacy-to-services modernization using parallel-run parity and feature-flagged cutovers.”

“Frontend engineer with insurance-domain experience (AAA Insurance and insurance quoting flows) who has delivered Angular/React/Next.js products end-to-end. Notable for building a complex drag-and-drop email template/code-generation UI and for modernizing React codebases (Redux->Context, lazy loading, memoization) to improve performance and reduce security vulnerabilities, while using feature flags and strong QA automation for fast, controlled releases.”

“Backend-focused engineer who built a Python/Flask task-management API with JWT/RBAC, modular service/repository architecture, and PostgreSQL/SQLAlchemy performance optimizations (indexes, lazy loading, bulk ops, pooling). Also implemented multi-tenant data isolation strategies and built an OpenAI-powered document summarization workflow using chunking, async processing, Redis background workers, and caching to improve throughput.”

“Frontend-focused engineer (~8 years) with strong React/TypeScript and Angular experience who leads end-to-end UI architecture, performance budgets, and quality practices at scale. Known for restructuring large, tightly coupled codebases into feature-based domains to eliminate UI freezes and improve team throughput, and for tight Product/Design/QA alignment via a “3 Amigos” process that catches workflow gaps early. Currently seeking a new frontend role due to GE Vernova outsourcing; has been acquired twice by large companies.”

“Frontend engineer who led the 2025 end-to-end launch of the Score Casino web platform, integrating a new regulated brand into an existing monorepo with scalable theming, Next.js routing changes, and supporting Docker/SRE deployment work. Emphasizes quality at scale through visual regression testing, Datadog/Bugsnag observability, and test-suite redesign (parameterized theme tests) that reduced CI flakiness; shipped the launch two months ahead of schedule while meeting GLI submission standards.”

“Backend-focused Python/Flask engineer who owned REST APIs for a video analysis system, including preprocessing, ML inference integration, and post-processing into time-aligned predictions consumable by a React UI. Demonstrated practical performance/scalability work by decoupling API request handling from CPU-heavy processing and adding timing instrumentation to identify and optimize bottlenecks.”

“Frontend engineer with 2 years at WestJet building an agent-facing booking UI layered on top of guest flows, including creating a dedicated agent UI library packaged in JFrog Artifactory for reuse across microfrontends. Also delivered a highly interactive Micron brand site using GSAP for scroll-driven animations and implemented resilient audio state/transition logic to handle rapid user scrolling. Experienced partnering closely with design/product (e.g., Corient) to prototype and ship polished, responsive experiences on tight timelines.”

“Frontend engineer who led end-to-end delivery of a complex, real-time dashboard/discovery and admin workflow module using React + TypeScript + Redux. Emphasizes quality at scale through automated testing (Jest/Playwright), accessibility validation (NVDA/axe), and reusable component architecture (Storybook), and has hands-on experience solving performance issues via bundle analysis and route-based lazy loading/code splitting.”