• EN|DE
  • Christian B. Eick

    I help product teams build frontends that last.

    Frontend engineer specializing in TypeScript, React, and interactive data interfaces.

    Christian B. Eick · Freelance Frontend Engineer

    Mainz, Germany · work@chriseick.com

    Trusted by teams at:

    What I focus on

    • Long-lived product frontends
      Building Frontends that evolve with changing requirements.
    • Existing codebases
      Improving, modernizing, and maintaining large codebases with tests, tooling, and clear structure.
    • Frontend architecture
      Structuring applications for scale with clear boundaries, reusable patterns, and maintainable code.
    • Interactive data interfaces
      Creating fast, accessible UIs for complex data with tables, charts, filters and real-time updates.

    Selected work

    • Interactive Data Visualization

      Built a reusable charting system for a large financial information platform, turning raw financial data into interactive visualizations for exploring complex time-series data. Designed the frontend architecture from the ground up, with support for zooming, exports, tooltips, and reusable chart components.

      Highlights
      • Frontend architecture
      • Complex rendering
      • Reusable abstractions
      • Product-driven design
    • Real-Time Operations Dashboard

      Designed and built the frontend architecture for a live operations map used to monitor autonomous vehicles in real time. Combined streaming updates with an interactive 2D map — supporting pan and zoom, operational overlays, and rich interactions with vehicles, routes, stations, and system state. Kept the codebase testable and maintainable throughout.

      Highlights
      • Real-time complexity
      • Complex interactions
      • Maintainable architecture
      • Operational complexity
    • SaaS Billing & Subscription Management

      Owned the frontend of a billing and subscription management surface within a B2B SaaS platform. Built workflows for managing subscriptions, payment methods, invoices, permissions, and account configuration — contributing to the platform’s frontend architecture and mentoring engineers along the way.

      Highlights
      • Domain complexity
      • Cross-functional ownership
      • Workflow design
      • Mentoring & leadership

    How I work

    I focus on pragmatic engineering that lets teams ship faster while maintaining quality. These principles guide every decision I make in a project:

    • Choose the right tools for the problem, not trends
    • Understand my tools deeply, including their trade-offs
    • Treat performance and user experience as central product concerns
    • Use abstractions to make code more readable and collaborator-friendly
    • Make engineering decisions that increase the output of the team as a whole

    Good fit

    Great matches:

    • Frontend teams that treat the codebase as a core product asset
    • SaaS products designed to evolve over time
    • Projects where maintainability, performance, and developer experience are priorities
    • Independent or collaborative work with designers and product managers
    • Teams at any stage, from early-stage startups to large engineering organizations

    Not a fit:

    • One-off marketing websites or landing pages
    • Short-term projects without ongoing product ownership
    • Projects where speed consistently takes priority over quality

    Get in touch

    If your project aligns with my focus, the easiest way to reach me is directly by email: