Senior Software Engineer (Web) (m/f/d)

Berlitz

Get hot jobs first on Telegram

New positions appear faster in our channel

Location: Colombia, Germany
Job Type: full-time
Work Format: 🌍 Remote
Salary: Not specified
Posted: October 11, 2026

Job Description

We're building a new global Berlitz, and this is your opportunity to help shape it. Nearly 150 years of expertise, meeting the ambition and technology to power a new era of learning.

If you are the kind of person who thrives in a fast-paced environment, isn’t afraid of a blank page, and is excited to help shape the future of a global company undergoing a significant transformation, you might belong at Berlitz!

We are seeking a Senior Frontend Engineer to help build the web client for our next generation global online learning platform, empowering users worldwide to master languages and new skills through interactive courses. The web app serves four distinct audiences: learners taking courses, teachers running and preparing lessons, Berlitz staff administering the platform, and enterprise customer representatives tracking their organization’s programs. In this role, you will take ownership of the web app end to end: the screens each of these users work in, the path that gets them there, and the build and release pipeline that puts it in front of them. You will work in an agile, parallel engineering environment with Claude Code woven into your daily workflow.

The role is frontend-first, but not frontend-only. You will read and extend backend code where a feature needs it — shaping an API contract with the backend team, adding an endpoint, debugging across the boundary rather than filing a ticket and waiting.

This is a 100% remote position with a preference for candidates operating within European time zones. You will work cross-functionally with backend and platform teams (consuming typed API contracts and the web CI pipeline) while enjoying high autonomy and low bureaucratic friction. Best of all, you will work primarily on a greenfield app, building a modern, clean client with no legacy debt.

Core Responsibilities

App Architecture: Design and build features in React and TypeScript, from screens and routing to state management, within a shared TypeScript layer also consumed by other client surfaces.
Multi-Audience UX: Build for learners, teachers, Berlitz staff, and enterprise customer reps in one app — distinct workflows, permissions, and data density, on a common design system.
Core Tech Stack: Utilize React and TypeScript as your primary stack, building on the team’s shared design-system package.
Across the Stack: Co-design typed API contracts with the backend team and make backend changes yourself when a feature calls for it.
Web Delivery: Own the path from code to production: build configuration, bundling, versioning, environment promotion, and release.
Performance & Accessibility: Own the numbers that decide whether the product feels good — load and interaction performance, responsive behavior across devices, and WCAG-level accessibility.
CI Integration: Trigger and consume the platform team’s CI/CD pipeline (GitHub Actions) to ship builds without owning the underlying infrastructure.
AI-Assisted Engineering: Actively integrate advanced tools like Claude Code into your daily GitHub and development workflow to maximize code quality and speed.
Clean Code Standards: Champion and apply best practices for type safety, testing, and accessibility across the app.

Required Skills & Qualifications

Experience: 5+ years of professional frontend development experience, with a proven track record shipping production web applications to real users.
Deep Tech Skills: Strong, production-proven experience with React and TypeScript, including modern rendering and data-fetching patterns.
Fullstack Capability: Demonstrated experience working server-side — designing API contracts, writing endpoints, and reasoning about data models — enough to own a feature across the boundary.
Product Range: Experience building both consumer-facing flows and role-based internal or B2B tooling — dashboards, admin screens, reporting.
Release Ownership: Hands-on experience owning web release engineering end to end: build pipelines, versioning, staged rollout, and post-release monitoring.
Craft: Demonstrated ownership of frontend performance, responsive design, and accessibility in a real product.
Modern Workflow: Proficiency with GitHub for version control, code reviews, and collaborating across parallel teams.
Architectural Knowledge: Working knowledge of shared design-system consumption, client-side state management patterns, and consuming typed API contracts.
Collaboration: Excellent communication skills to mentor peers and align with parallel engineering teams.

Strong Plus

Mobile Experience: Production experience with React Native, ideally on Expo’s managed workflow, including the New Architecture. Our web and mobile clients share a TypeScript layer and design system, and engineers who can move across both surfaces have outsized impact here.
Mobile Release Craft: Experience with signed builds, app versioning, and store submission (TestFlight/Play internal tracks, review, staged rollout).

What Makes This Role Great

AI-Native by Default: We build with Claude (code generation, API design, code reviews, architectural documentation, and debugging). You get first-class AI tooling that takes the boilerplate off your plate, so your time goes to product craft, judgment, and the genuinely hard client problems.
Pure Greenfield: No legacy code, no technical debt, you own the design of the web experience for our global EdTech platform.
Infrastructure Support: A dedicated Platform Engineering team owns the underlying CI/CD pipeline and cloud infrastructure, so you focus on the app and the release craft that gets it to users.
100% Remote: Work from anywhere in Columbia or Germany, with a preference for alignment with European time zones (CET/EET/WET).

At Berlitz, connecting people across languages and cultures is at the heart of what we do. Our global workplace reflects the diverse world we serve, bringing together different backgrounds, experiences and perspectives. We create an inclusive environment where everyone has an equal opportunity to belong, contribute and grow.

Ready to shape what’s next? Join us and help build the future with us.

🎯 Who is this job for?

Senior level: This role suits a frontend-focused engineer with 5+ years of professional experience delivering production web applications using React and TypeScript.

The candidate should be skilled in full-stack feature development, typed API design, state management, design systems, performance, responsive design, WCAG accessibility, testing, GitHub collaboration, and end-to-end web release engineering.

They should be comfortable building consumer and role-based B2B interfaces, working across frontend and backend boundaries, managing CI/CD releases, mentoring peers, and ideally contributing to React Native applications.

💬 Potential Interview Questions

How would you structure a greenfield React and TypeScript application serving learners, teachers, administrators, and enterprise representatives?

I would establish feature-oriented boundaries, shared UI and domain packages, typed routing, and clear separation between server state, client state, and presentation. Role-aware layouts and permissions should be enforced consistently in routing, data access, and UI components.

Which modern React rendering and data-fetching patterns would you use for this platform?

I would use colocated data requirements, cache-aware fetching, optimistic updates where appropriate, and error or loading boundaries. The exact rendering strategy would depend on the application framework, but I would prioritize predictable caching, minimal waterfalls, and accessible progressive loading.

How would you design a typed API contract between the React client and backend services?

I would define explicit request and response schemas, error formats, pagination rules, and authorization expectations, ideally generating or sharing TypeScript types from a single source of truth. Contract tests and backward-compatible versioning would help prevent client-server drift.

Describe how you would implement role-based access control in a multi-audience web application.

I would treat permissions as a backend-enforced security boundary and mirror them in the client for navigation and usability. A centralized permission model can drive route guards, feature visibility, and disabled actions while avoiding duplicated role logic throughout the component tree.

How would you improve initial load and interaction performance in a large React application?

I would measure with Lighthouse, Core Web Vitals, browser profiling, and real-user monitoring before optimizing. Typical improvements include route-level code splitting, asset optimization, effective caching, reducing JavaScript, virtualizing large lists, and preventing unnecessary renders.

How do you ensure WCAG-level accessibility in React interfaces?

I use semantic HTML, keyboard-accessible interactions, visible focus states, correct labels and relationships, sufficient contrast, and appropriate announcements for dynamic content. Automated tools such as axe are useful, but they must be complemented by keyboard testing and screen-reader checks.

What testing strategy would you apply to a shared design system and application features?

I would combine unit tests for logic, component and interaction tests for UI behavior, contract tests for APIs, and end-to-end tests for critical user journeys. Shared components should also have accessibility checks and visual regression coverage where visual consistency is important.

What should a web release pipeline include, and how would you use GitHub Actions?

The pipeline should validate formatting, types, tests, security checks, and production builds before publishing versioned artifacts. GitHub Actions can promote builds through environments with approvals, environment-specific configuration, rollback support, and deployment notifications without requiring ownership of the underlying infrastructure.

How would you diagnose a production issue that crosses the frontend and backend boundary?

I would correlate client logs, network traces, backend logs, metrics, and the affected API contract to isolate whether the problem is in data, authorization, transport, or rendering. I would reproduce it with a minimal case, add targeted instrumentation, and ship a tested fix with monitoring for regression.

How would you use Claude Code responsibly in your daily engineering workflow?

I would use it to accelerate scaffolding, refactoring, test generation, API exploration, and documentation while keeping design decisions and review human-owned. Generated changes must still pass type checks, tests, security review, accessibility checks, and normal GitHub code-review standards.

📋 Job Summary

Berlitz is transforming its 150-year language-learning expertise into a global, next-generation online learning platform. As a Senior Software Engineer (Web), you’ll build a greenfield React and TypeScript application for learners, teachers, staff, and enterprise customers, while contributing to typed APIs, performance, accessibility, testing, and GitHub Actions releases. This is a full-time, 100% remote role open to candidates in Colombia or Germany, with a preference for European time zones; salary details are not disclosed. Apply to shape a high-impact EdTech product with modern technology, AI-assisted development using Claude Code, strong autonomy, and no legacy debt.