Anthony Laguan
Software Developer
9+ years exp
Python
C
Node JS
SQL
JavaScript
C++
Active 2 days ago
+57 (320) 5777386 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Web developer (Junior) focused on building client-driven web applications and integrating third-party APIs. Proven ability to implement API-driven frontends and simple state management as shown in Weather-Report/services/api.js and the fetch thunks in movie-discover/src/app/features/getMovies/index.js. There is little to no public evidence of production backend system design, transactional database work, migrations, observability, or scalable architecture patterns.
Technical skills
Python
C
Node JS• Junior
SQL• Middle • 9y+
JavaScript• 8y+
C++• Senior
Node JS
Axios
Databases
Databases
Redis
Frontend
Next.js
Tailwind CSS
Redux
Redux Toolkit
PostCSS
autoprefixer
ESLint
GraphQL• 6y+
React.js• 6y+
DevOps
Docker
Kubernetes
SLI/SLO/SLA
Vector
Git• 6y+
Rest API• 6y+
CI/CD
QA
Jest
AI/ML
Computer Vision
Embeddings
LLM
OpenCV
Prompt Engineering
Reinforcement Learning
Synthetic Data
RAG
Robotics
Digital Twin
Reinforcement Learning
Timeline
Senior Software Engineer, Omnichannel Commerce Platform
•
Senior
Abercrombie & Fitch
•
Full-Time
Designed and implemented microservices for international omnichannel e-commerce using C++ services and REST APIs. Built transaction processing for omnichannel orders and improved authorization success and latency through backend optimizations. Added Redis and SQL tuning to speed personalization requests, and orchestrated store availability updates via event-driven messaging to improve fulfillment SLA. Strengthened reliability and observability with CI/CD checks, structured code review standards, and performance-oriented monitoring.
C++
Rest API
Redis
SQL
CI/CD
Git
Full Stack Software Engineer, Digital Product Engineering
•
Middle
Azordev
•
Full-Time
Developed the DID Peru app with GraphQL data access and component-based UI patterns, including onboarding and QR identity flows. Built admin tooling for partner and attendee export workflows with authentication and role-based access controls. Implemented a real-time shipment view using React and GraphQL, improving state handling for frequent updates, and created a marketplace UI consuming a museum API. Maintained Linux deployment pipelines with Git-based collaboration and delivered reusable backend scaffolding with REST APIs, token authentication, validation, and automated migrations.
GraphQL
React.js
Rest APIsince 2020
Gitsince 2020
Backend Software Engineer, Credit Decisioning & Servicing
•
Middle
OnDeck
•
Full-Time
Implemented backend components for a term loan workflow using SQL data models and secure borrower portal patterns. Improved underwriting-to-offer consistency and reduced mismatched term records across production pipelines. Built and maintained service logic for loan servicing correctness, ensuring statement and repayment schedule alignment. Optimized backend data flow and performance to increase decision throughput while keeping evaluation latency within acceptable limits.
SQLsince 2017
Simulation Software Engineer, Robotics & Digital Twins
•
Middle
Vertex Studio
•
Full-Time
Developed 3D simulation components for robotics training by integrating physics-environment behaviors with scenario generation pipelines. Built geometry and scene utilities for digital-twin style simulations, including mesh generation and transformation logic to improve asset preprocessing reliability. Contributed to educational and XR training experiences with browser-based 3D rendering and event-driven scenario state. Added simulation instrumentation and debugging visualizations in an open-source experimentation effort using Git-based contribution workflows.
Universidad de El Salvador
Bachelor's Degree •
Mathematics
Junior Backend Developer
Confidence: Medium API Engineer
Web developer (Junior) focused on building client-driven web applications and integrating third-party APIs. Proven ability to implement API-driven frontends and simple state management as shown in Weather-Report/services/api.js and the fetch thunks in movie-discover/src/app/features/getMovies/index.js. There is little to no public evidence of production backend system design, transactional database work, migrations, observability, or scalable architecture patterns.
API Design
2/10
How well APIs are designed
Basic REST/HTTP integration and simple pagination patterns in client code; no evidence of formal API versioning, idempotency keys, or consistent error contract design.
Evidence
Weather-Report/services/api.js: simple axios wrappers for OpenWeather endpoints
movie-discover/src/app/features/getMovies/index.js: fetchMovies and fetchMoreMovies thunks using API_URL and page params
movie-discover/src/app/pages/Movie.js: direct use of API_URL endpoints for movie and credits fetch
Data Layer & Database
2/10
Working with databases
Uses a hosted realtime database (Firebase) with straightforward CRUD wrappers; no migration history, transactional control, or advanced query tuning is present.
Evidence
firebase-crud/init.js: firebase.initializeApp + export database (Realtime Database)
firebase-crud/CRUD/create.js: push/set wrapper that writes data with dates
firebase-crud/CRUD/update.js: simple update via ref.child(id).update(...)
Scalability & Performance
1/10
Handling load and speed
Minimal scalability work: no caching/invalidations strategy, no queue-based decoupling, and no measured performance optimizations; only small client-side caching via localStorage.
Evidence
movie-discover/src/app/pages/Movie.js: localStorage used to cache movie details for quick reloads
System Architecture
2/10
Overall system structure
Reasonable folder/module separation for small web apps (services, components, redux slices) but no evidence of deliberate service decomposition, graceful degradation, or multi-service architecture trade-offs.
Evidence
movie-discover/src/app/features/getMovies/index.js: Redux slice and async thunks
Weather-Report/pages/index.js and services/api.js: separation of page and API service
firebase-crud/CRUD/*: discrete CRUD modules and init.js for DB wiring
Security & Auth
1/10
Protecting data and access
Minimal security practices surfaced: environment variables used for API keys and Firebase config, but no auth lifecycle, token refresh/revocation, input sanitation, or dependency-audit artifacts.
Evidence
firebase-crud/init.js: reads firebase config values from process.env
Weather-Report/services/api.js: uses OPENWEATHERMAP_API_KEY constant for API access
Reliability & Observability
1/10
Stability and monitoring
Basic error handling exists (try/catch and promise .catch), but there is no systematic reliability instrumentation such as retries with backoff, timeouts, structured logging, graceful shutdown, or metrics.
Evidence
firebase-crud/CRUD/create.js: try/catch and .catch handlers for write errors
movie-discover/src/app/features/getMovies/index.js: .catch branches that dispatch failure state
Expertise
Node.js• Junior
Technologies
Databases
Node JS• Junior
Axios
Async• mentioned only
Recommendations
- Build and maintain API-integrated single-page apps (React/Next) that consume external REST services and handle client-side state and caching.
- Implement small Node.js backends (Express or similar) to expose controlled APIs and practice request validation, transaction boundaries, and structured error contracts.
- Harden existing Firebase projects by adding tests, input validation, and a migration/versioning story for data changes.
- Improve reliability practices: add timeouts, retries with exponential backoff, structured logging, and basic observability (metrics/traces) for services.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Frontend Developer
Confidence: Medium App Engineer
Frontend web developer (junior) focused on building small React and Next.js user interfaces with component-driven structure. The strongest proven skill is assembling client-side UI and basic app state flows, as shown by the React components and Redux slices in movie-discover/src/View and movie-discover/src/app/features/getMovies/index.js. There is little public evidence of advanced engineering practices such as robust testing, performance instrumentation, complex state machines, or production-grade server-state discipline.
UI Component Architecture
3/10
How interface parts are built
Basic component-driven UI structure with small reusable components, but no evidence of a custom design system, token system, or advanced composition patterns.
Evidence
movie-discover/src/View/index.js: composes HeroImage, SearchBar, FourColGrid and other components
Weather-Report/pages/index.js: Main layout composes MainInfo, SearchInput and Sidebar components
Responsive & Cross-browser
3/10
Works on all screens and browsers
Responsive layout via Tailwind and media queries is present, but there is no advanced cross-browser feature detection or RTL/i18n scaffolding.
Evidence
Weather-Report/tailwind.config.js: Tailwind content config for responsive utilities
Weather-Report/styles/Home.module.css: media query adjustments and Tailwind utility usage for layout
Performance Optimization
1/10
Speed of the interface
Little to no measured or deliberate performance work; no code-splitting, virtualization, or bundle analysis artifacts visible.
Evidence
movie-discover/src/app/features/getMovies/index.js: naive fetch usage and duplicated fetch calls with no caching or debouncing
Weather-Report/pages/index.js: single-threaded fetch flow driven by geolocation with no fallback caching strategy
Accessibility & Semantics
2/10
Usable for everyone
Some minimal accessibility-conscious rules are present, but there is no systematic a11y work such as ARIA on custom widgets, focus management, or automated linting in CI.
Evidence
Weather-Report/styles/globals.css: prefers-reduced-motion media query to disable animations
movie-discover/src/app/index.css: global typography and reduced-motion media query present
State Management & Data Flow
3/10
Managing data in the app
Basic state management and async flows are implemented using Redux and thunks; patterns are functional for small apps but lack advanced server-state discipline, cancellation, optimistic updates, or explicit race handling.
Evidence
movie-discover/src/app/features/getMovies/index.js: Redux Toolkit slice and async thunk patterns for fetching movie lists
movie-discover/src/app/features/search/index.js: search slice with async thunks
firebase-crud/CRUD/*.js: simple CRUD wrappers around Firebase Realtime Database
UX & Visual Polish
3/10
Look and feel quality
UI shows visual polish for small projects - themed backgrounds, responsive cards and loaders - but this is template-level polish rather than product-grade UX patterns like skeletons, detailed edge states, or undo flows.
Evidence
Weather-Report/pages/index.js: loading state with spinner, background images per weather type
Weather-Report/styles/Home.module.css: curated background images and card layout for visual presentation
movie-discover/src/View/HeroImage.js: styled hero component used in the Discover view
Verified artifacts
Expertise
React• Intern
Modern Web Frameworks• Intern
HTML & CSS• Intern
Technologies
Redux
GraphQL• 6y+
Tailwind CSS
Next.js
React.js• 6y+
PostCSS
ESLint
Redux Toolkit
autoprefixer
JavaScript• mentioned only
Webpack• mentioned only
Recommendations
- Use the developer to build small-to-medium React or Next.js frontends that need solid component composition and straightforward client state management.
- Assign tasks to harden state and server interactions by adopting RTK Query or React Query, adding request cancellation and cache invalidation patterns.
- Invest in TypeScript migration and unit/integration test coverage for critical flows to raise the codebase from tutorial-level to production-grade.
- Have the developer implement CI linting, basic performance measurements (Lighthouse or bundle-analyzer) and address the obvious fetch/caching issues shown in getMovies.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern QA Engineer
Confidence: Medium Generalist
Frontend JavaScript developer (junior) focused on small React/Next.js applications and basic unit testing. The strongest proven skill is building simple client-side web apps with API integration as shown by pages/index.js and services/api.js in the Weather Report project and the component tests in Owly-Bookstore/src/App.test.js. There is little evidence of test infrastructure, contract/integration testing, CI-driven automation, or performance/load engineering in the public code.
Test Automation Frameworks
2/10
Building automated tests
Minimal test automation artifacts present (basic Jest/react-testing-library unit tests and setup). No automation fixtures, mock servers, sharding, or selector discipline; evidence is limited to simple unit tests and CRA/Next test setup.
Evidence
Owly-Bookstore/src/App.test.js
movie-discover/src/app/App.test.js
movie-discover/src/setupTests.js
Test Coverage & Strategy
2/10
What and how to test
Tests exist but cover only trivial component behavior; there is no visible risk-based tagging, negative-path or property-based tests, mutation testing, or meaningful boundary testing.
Evidence
Owly-Bookstore/src/App.test.js
movie-discover/src/app/App.test.js
API & Integration Testing
Testing how parts work together
Not evidenced in public code
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
Running tests automatically
Not evidenced in public code
Expertise
Unit & Component Testing• Intern
Technologies
JavaScript• 8y+
Jest
Recommendations
- Develop small-to-medium React/Next.js user-facing features and single-page application pages (UI + API integration).
- Improve and expand unit and component tests using Jest and React Testing Library to cover negative paths and edge cases.
- Work on test automation tasks that add CI integration and deterministic test fixtures (mocked API responses, simple mocks/stubs).
- Refactor async data flows to avoid duplicate network calls and add centralized API client error handling.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: