Senior Frontend Software Engineer (Bridge) Canada, Remote

GetBridge is seeking a seasoned Frontend Engineer to take ownership of modernizing and maintaining our legacy application while planning and driving strategic feature development. In this role you will collaborate on project architecture, oversee our microfrontend frameworks and lead cross-functional team initiatives.

People Matter Most

We are a global team of Engineers, Product Managers, Designers, and Program Managers across North and South America, Hungary, and the UK.

Bridge is a software that people use for learning and career-development. Our goal? Help organizations build a culture where people thrive. Curious about what it looks like?

Here is a quick intro:

The Reality of the Role: Bridge Frontend

Engineering - Where Challenge Meets Ownership

This is a hands-on senior engineering role. You will own frontend work on our core product — a large, mission-critical application built up over many years — shipping new features, fixing tricky bugs, and modernizing code that needs it. You will work closely with product owners, designers, and backend engineers to get features over the line.

The Ideals & DNA of a Bridge Frontend Engineer

• Strong frontend fundamentals. Deep, production-proven experience with React, TypeScript and adjacent tooling.

• Accessibility above all. You treat accessibility as part of “done,” not a later cleanup pass — building to WCAG standards for keyboard and screen-reader users by default.

• A ‘No Fear’ Attitude: You have been in situations where there was no guide, no documentation, and no one else to fix the problem. You had to figure it out on your own. You don’t panic when facing an ugly codebase—you just roll up your sleeves.

• Abstract & Conceptual Thinking: Navigating a massive, under-documented monolith requires an exceptional ability to see the ‘big picture’ through a foggy window. You can easily grasp high-level architecture and connect the dots between messy legacy logic and modern services.

• Polyglot & Diverse Background: You have worked across many stacks. You aren’t attached to a single language — you understand trade-offs and treat technologies as tools to solve business problems.

• Direct Communicator: We value honesty, constructive friction, and direct feedback. You aren’t easily offended by sharp critique; instead, you look for the objective truth in every technical debate.

Our Tech Stack - and What This Role Requires

The list below is the environment you will work in, not a checklist you must already know. This is a frontend role on a full-stack team, so you will touch much of it — but we require depth in the frontend stack and only working familiarity with the rest. If you are strong in React and TypeScript and unafraid of a large legacy codebase, you can learn the backend and data specifics “on the job”.

Frontend — where you’ll spend your time

• React and TypeScript. Most of our frontends are on React 19 with strict TypeScript while parts of the monolith are still on older React and plain JavaScript.

• Microfrontend architecture with 20+ apps in production.

• Well-made and solid shared component library.

• Data and state with TanStack Query and React Context — not Redux.

• Testing as a default: Vitest, React Testing Library, Playwright and MSW, with Storybook-driven component development.

• Accessibility as a first-class requirement — semantic HTML, full keyboard and screen-reader support and WCAG conformance built into every component rather than bolted on afterward.

• Internationalization from the start — the product ships in many languages, so UI text is externalized with message formatting. Every screen is built locale-aware.

• Performance you can measure — we track real-user frontend metrics, including Core Web Vitals, and treat regressions as defects rather than nice-to-fixes.

Backend and data — you integrate with it, you don’t own it (working familiarity)

• Ruby on Rails monolith (the core application), plus Java/Kotlin Spring Boot REST services.

• PostgreSQL on AWS Aurora, Apache Pulsar messaging and a Debezium-based ETL pipeline.

• AWS Neptune (graph) and AWS OpenSearch.

DevOps and infrastructure

• CI/CD on GitHub Actions.

• Monitoring with Datadog.

• Infrastructure as code with Terraform.

Ways of working

• SAFe, Jira, Confluence, Slack and Google Workspace. MacBook Pro.

Bonus Points if you Have…

• Microfrontend or module-federation experience; Rails or JVM familiarity; Terraform and CI/CD depth; graph or search infrastructure.

• Hands-on experience using AI coding assistants and agents, such as Claude Code, as part of your day-to-day workflow to navigate, map, and accelerate work in a large codebase.

What You Get

• An async, trust-based culture:

• True Autonomy, No Micro-management: We don’t track your hours or care when or where you log in; we focus entirely on your impact and results.

• Trust & Availability: The rules are simple: show up for your scheduled meetings, keep the team updated if you step away, and be there to support your teammates when they need a hand.

The ‘Bridge Perks’ – Why It’s Worth It:

• Modern Dev Tooling: We embrace modern engineering efficiency—AI tools are provided to help you navigate, map out, and accelerate your work.

• Real Influence: This role will be placed on a team that is central to the success of Bridge as a whole. We are responsible for cornerstone pieces of the Bridge ecosystem and continue to build new features that will shape our future.

• Elite Mentorship: Our engineering team is a collection of passionate, collaborative, and mature software engineers who are always eager to team up. There will be opportunities to work directly with folks who are vastly experienced in software engineering and architecture.

• Hack Week: Hack week occurs three times a year and is one of the cornerstones of Bridge Engineering culture. Work on whatever you like for a week as long as it benefits Bridge in some way.

We are an Equal Opportunity Employer and do not discriminate against any employee or applicant for employment because of race, colour, sex, age, national origin, religion, sexual orientation, gender identity, status as a veteran, and basis of disability or any other federal, state or local protected class.