ismaelramos.dev
  • Search articles

    ~/ ISMAEL-RAMOS — main · Madrid · Remote

    Frontend Architect
    building scalable
    digital products.

    Modern frontend architecture, AI-assisted engineering, performance and user experience.

    I'm Ismael — I design and build web systems that stay maintainable as products and teams grow.

    LATEST ARTICLE Persisting Windsurf context across sessions with rules May 12 · 3 min →

    Twelve years, four numbers.

    8M+
    Users reached
    Santander scholarships platform, across markets
    12y
    Shipping web software
    2013 — today, frontend & full stack
    18+
    Products shipped
    Commercial platforms + personal projects
    2.4k★
    On open source
    Angular Example App + libraries on GitHub

    Selected platforms where I've shaped architecture, performance and accessibility over multiple years.

    1. 2017 — present · Madrid

      Santander Scholarships Platform

      Eight years evolving the frontend architecture of a global scholarship platform — from a Spanish portal to a system serving more than 7 million users across multiple countries and brands.

      Focus areas

      • Scalable frontend architecture
      • Accessibility as first-class concern
      • Performance & Core Web Vitals
      • Maintainability across teams
      • Developer experience
      • Reusable component systems

      Constraints

      • Legacy systems and incremental migration
      • Multi-team coordination
      • Core Web Vitals budgets
      • Strict accessibility requirements
      • Long-term maintainability over short-term speed
    2. 2019 — 2021 · Madrid

      Trust·u BBVA

      Alternative credit scoring platform for SMEs using transaction data analysis. Designed a multi-tier architecture handling sensitive banking data, complex algorithmic scoring, and regulatory compliance.

      Focus areas

      • Bank-grade security & compliance
      • Complex algorithmic design
      • Third-party banking APIs
      • Real-time data processing
      • Multi-department algorithm versioning
      • 50,000+ SME scoring

      Constraints

      • Secure credential & transaction handling
      • Multi-stakeholder algorithm review
      • Third-party API dependencies
      • Bank regulatory requirements
      • Transaction data lag (24-48h)
    • Open source · 2.4k★

      Angular Example App

      A reference architecture for Angular applications. Patterns for project structure, state and feature boundaries — used as a learning resource by thousands of developers.

    • Personal · 2026

      QuizCurious

      An AI-assisted quiz platform for curious minds — turn any topic into a tailored quiz and learn by playing.

    • Personal · 2024

      Randmenu

      A decision-reduction nutrition planner. Built around fast weekly planning and a usability-first interface.

    More work on GitHub →

    Six things I keep coming back to.

    1. Simplicity over complexity

      Building systems that remain understandable as they grow — fewer moving parts, sharper boundaries.

      Applied in Frontend architecture redesign →
    2. Product-driven engineering

      Technology decisions should improve user experience and business outcomes, not optimise for the resume.

      Applied in Cross-team component library →
    3. Performance is product

      Fast interfaces shape perception, usability and retention. Speed is a feature, not a polish phase.

      Applied in Performance optimisation →
    4. Accessibility by default

      Inclusive interfaces are part of good engineering. Semantics and keyboard paths come first, not last.

      Applied in Accessibility implementation →
    5. AI as augmentation

      Using AI to accelerate execution while keeping engineering judgement and architectural intent.

      Applied in AI features integration →
    6. Developer experience

      Internal tooling, clear conventions and short feedback loops compound product velocity.

      Applied in Angular standalone migration →

    Areas I'm actively building, writing and thinking about.

    • AI-assisted development workflows
    • Frontend architecture with Signals
    • Scalable Angular applications
    • Product engineering
    • Observability & performance
    • Design systems
    • System design
    • UX-driven engineering
    Architecture
    Scalable frontend systems · Monorepos · Feature-driven architecture · SSR / SSG · Observability · Performance optimisation
    Product engineering
    UX collaboration · Accessibility · Experimentation · Analytics · Developer experience · AI-assisted workflows
    Core technologies
    Angular · TypeScript · NestJS · PostgreSQL · Nx · Playwright · LitElement

    $ subscribe --newsletter

    Stay in the loop

    Occasional notes on architecture, product engineering and AI-assisted workflows. No spam — unsubscribe at any time.

    SUBSCRIBE →
    Browse all articles →

    A heatmap, but for posts.

    $ writing --year 2026 · cadence
    23 posts 9 drafts 14d longest streak 3d since last
    JANFEBMARAPRMAY JUNJULAUGSEPOCT NOVDEC
    MWFS
    LESS MORE

    How I draw a frontend.

    frontend-architecture.svg · layered, dependency-rule enforced
    own code platform data flow
    USER · BROWSERrequests, interactions, perceived performanceAPP SHELLrouterlayoutauth boundaryerror walli18n · theme · a11yFEATURES · bounded contexts, lazyscholarships/scholarshipsapplications/applyprofile/meadmin/admin+ next featureadd without touching othersSHARED KERNELdesign systemprimitivesdomain typesutilities · signalsADAPTERShttpstoretelemetryPLATFORM · not yours, but you depend on itREST · CMS · identity · analytics · CDN · observability stack

    The shell is the only place routing & auth live — features never reroute themselves.   Features depend down, never sideways: zero cross-feature imports, lazy by default.   The shared kernel is the only thing the platform talks to — swap an adapter, the app does not notice. The diagram is the rule; the rule is enforced by Nx module boundaries.