Elías Hernández

BBVA is a global bank operating in more than 25 countries with over 80 million active customers. BBVA Mexico is the country’s largest financial institution, serving 27 million digital customers through its mobile app. Design, engineering standards, regulatory requirements and technology are governed centrally from Spain.

• Deliver customer journeys end to end for the retail banking app: Figma handoff, composition from the bank’s component catalogue, business logic built from scratch, service integration, demos, unit and accessibility testing, functional and analytics end-to-end testing, CI/CD, documentation and production troubleshooting.
• Compose each journey from 20 to 30 catalogue components following atomic design, extending non-atomic components such as lists through their public property and event APIs where the design calls for behaviour the catalogue does not provide.
• Meet a SonarQube quality gate of 85% unit coverage in the Jenkins pipeline, with reviewers holding pull requests to roughly 90% across all scenarios rather than overall, branch coverage being the demanding part. End-to-end coverage is measured against acceptance documents written by the product owner with the business.
• Contributed to the group-wide migration of the Mexican app to a new stack and design language, directed from Spain, in teams ranging from 2 to 15 front-end developers. Rebuilt the payroll upgrade journey with a reduced step count, and migrated the Buy Now Pay Later journey.
• Built the address module on the new stack, letting customers upload proof of address in-app to update their identity data.
• Currently completing Pay by Bank, which lets customers pay third-party merchants from deeplinks and push notifications.
• Work to a monthly release train on two-week sprints, with journeys typically taking 6 to 12 months from architecture to release depending on dependencies. Own each journey for six months after release, through feature-flag rollout by percentage, before handover to the central maintenance team.

Spanish technology consultancy. Placed with BBVA Mexico for the full engagement, and offered a direct role by the client at the end of it.

• Built the payroll account upgrade journey (account tier N2 to N4) from scratch as one of two front-end developers, spanning around 15 screens including error scenarios. Upgrading customers to a complete profile made them eligible for credit and other products, so the journey carried direct commercial weight.
• Designed the flow as independent modules that reused existing back-end services without modifying them, since those services were shared and locked. The modular boundaries had to absorb the constraint instead of the services adapting to the flow.

• Developed responsive web and mobile interfaces in Angular and vanilla JavaScript for Walmart Mexico’s health services and mobile telecommunications products, building reusable components and integrating back-end APIs.
• Led a small front-end team, coordinating implementation and unblocking delivery across releases.

Paid client project, sourced through Ajusco Coding Bootcamp: the client chose our team of six developers from competing demos.

• Owned the community feature of a React and Firebase web app end to end: a real-time feed of posts and comments, with media uploads (images, PDFs and links) validated by file type, sorted by date and editable in place.
• Built the role-based flows behind it for members and the instructor, including admin moderation and event management, and fixed client-side routing for the GitHub Pages deployment.

Mobile app for practising the New Zealand practical driving test, built solo. The exam logic is a pure, dependency-free TypeScript engine with no framework, globals or clocks, so sessions replay deterministically and are covered by 254 tests; React Native sits behind an adapter layer as the only code that touches the outside world. Scoring is modelled on official NZTA error categories, session state is checkpointed to Supabase, and no provider keys ship in the app: AI and speech calls are proxied through an authenticated Supabase Edge Function. Architecture decisions are recorded as ADRs in the repository. Built as a work sample for AI-assisted engineering, where the discipline lives in the decision records and the test suite rather than the prompt. In development, not yet published.

Portfolio and writing platform built and maintained by me, including a component system of my own design, covering front-end, content and deployment.