Staff Frontend Engineer
Trading212
Get hot jobs first on Telegram
New positions appear faster in our channel
- Location
- Poland
- Job Type
- full-time
- Work Format
- ๐ Remote EU
- Salary
- Not specified
- Posted
- November 18, 2026
Job Description
Our mission is to enable everyone to build wealth
We reinvent how trading and investing work by creating exceptional products people love.
That takes high standards, high velocity and engineers who own what they ship.
Today, we serve over 6 million clients, with more than €38 billion in assets under management. At that scale, frontend architecture, performance and product quality have material business consequences.
Our frontend platform spans web and mobile: TypeScript, React, React Native and React Native Web in an Nx and pnpm monorepo, with TanStack Query, Zustand, Playwright, Detox and Jest. Around 95% of our code is reused across web and mobile.
About the role
Staff Frontend Engineers shape architecture and engineering direction across product teams while remaining close to the code. Your scope will include shared libraries, platform capabilities, developer tooling and difficult product-system problems.
This is not a people-management role. Its leverage comes from technical judgement, credible execution and making other engineers and teams more effective.
What you’ll do
-
Set direction for frontend architecture across React, React Native and the shared monorepo.
-
Own cross-team problems in platform capabilities, shared libraries, design-system foundations, tooling and developer experience.
-
Lead decisions on boundaries, abstractions, state and data flow, performance, testing and migration strategy.
-
Diagnose systemic rendering, bundle, runtime and release-quality problems and create durable fixes.
-
Remain hands-on where implementation, prototyping or technical investigation is the fastest way to create clarity.
-
Partner with product, backend engineering and QA on risks and decisions that cross team boundaries.
-
Mentor senior engineers, raise review quality and make sound frontend judgement easier to reproduce across teams.
-
Balance standardisation with team autonomy, avoiding platform work that creates more friction than leverage.
What you need to have
-
Evidence of architectural or platform impact across multiple frontend teams.
-
Deep ownership of complex production systems built with React or React Native and TypeScript.
-
Strong judgement in application boundaries, shared libraries, state management, performance and migration design.
-
A track record of improving developer effectiveness, reliability or product quality through durable mechanisms.
-
Practical experience diagnosing performance and correctness problems across web or mobile systems.
-
The ability to influence technical direction through evidence, clarity and trusted execution rather than title.
-
Clear communication that helps teams act on complex technical decisions.
-
Strong engineering and product judgement, including knowing when not to introduce a new abstraction.
Staff scope is assessed through ownership, judgement and sustained organisational impact—not years of experience or familiarity with every technology listed.
What to expect
-
Recruiter conversation
-
Code Review
-
Experience Deep Dive
-
Managerial interview
Your recruiter will explain each stage clearly and follow up after every conversation.
Bring your ambition to Europe’s fastest-growing mobile broker!
We thank all applicants, but only candidates selected for interview will be contacted. All personal data of applicants is protected by law and treated with strict confidentiality.
๐ฏ Who is this job for?
This role is suitable for a Senior-to-Staff Frontend Engineer with proven architectural and platform impact across multiple teams, rather than a people manager. Required skills include deep expertise in TypeScript, React, React Native, frontend architecture, monorepos, state and data management, performance, testing, developer tooling, and migration strategy, along with strong communication and technical judgement. The candidate should be familiar with leading cross-team initiatives, designing shared libraries and platform capabilities, diagnosing web and mobile performance or correctness issues, improving developer experience, mentoring engineers, and remaining hands-on with complex implementations.
๐ฌ Potential Interview Questions
How would you design frontend boundaries in an Nx and pnpm monorepo shared by React, React Native, and React Native Web?
I would separate domain logic, platform-specific adapters, shared UI primitives, and application composition into clearly owned libraries. Public APIs should be small and stable, with dependency rules enforced through Nx project boundaries and automated checks.
How would you decide what code should be shared between web and mobile when approximately 95% of the code is reused?
I would share business logic, data access, state, validation, and platform-neutral components wherever behavior is genuinely consistent. Platform-specific implementations should remain explicit when interaction models, accessibility requirements, or performance characteristics differ.
How would you structure server-state and client-state management using TanStack Query and Zustand?
TanStack Query should own asynchronous server state, including caching, invalidation, retries, and optimistic updates. Zustand should be limited to local client state such as UI preferences, transient workflows, or cross-component interaction state, avoiding duplicated server data.
How would you investigate a slow React or React Native screen in production?
I would first measure using browser profiling, React profiling, mobile performance tools, and production telemetry. I would identify whether the bottleneck is rendering, JavaScript execution, network latency, serialization, memory pressure, or native work, then validate the fix with comparable measurements.
What techniques would you use to reduce web bundle size and improve startup performance?
I would analyze bundle composition, remove duplicated dependencies, introduce route-level code splitting, and defer non-critical features. I would also optimize module boundaries, asset loading, tree shaking, and data-fetch timing while tracking Core Web Vitals and real-user metrics.
How would you design a safe migration from an existing frontend architecture to a new shared platform or library?
I would define the target architecture, establish compatibility boundaries, and migrate incrementally using codemods, adapters, and clear ownership. Each phase should be measurable, reversible where possible, and supported by deprecation timelines rather than a risky all-at-once rewrite.
How would you ensure reliable testing across React, React Native, and React Native Web?
I would use Jest for deterministic unit and integration tests, Playwright for critical web user journeys, and Detox for high-value mobile flows. Tests should focus on business behavior and contract boundaries, with shared fixtures and a small number of stable end-to-end scenarios.
How would you enforce architectural standards without creating excessive friction for product teams?
I would standardize only decisions that provide clear leverage, such as security, reliability, accessibility, and common platform capabilities. Lightweight documentation, automated linting, templates, and well-designed APIs are preferable to heavy approval processes, while teams retain autonomy for local concerns.
How would you diagnose and prevent correctness issues caused by asynchronous data and concurrent rendering in React?
I would model loading, error, stale, and empty states explicitly and ensure request results are associated with the current view or query key. Abortable requests, stable cache policies, careful effect dependencies, and tests for race conditions help prevent stale updates and inconsistent UI.
How would you influence technical direction across multiple engineering teams without direct authority?
I would build alignment through concrete evidence, written decision records, prototypes, benchmarks, and clearly stated trade-offs. Demonstrating a working solution and making adoption easy is usually more effective than relying on mandates or organizational status.
๐ Job Summary
Join a fast-growing European mobile broker on a mission to help everyone build wealth, serving over 6 million clients and €38 billion in assets. As a Staff Frontend Engineer, you’ll shape cross-team architecture, shared libraries, developer tooling, performance, testing and design-system foundations while staying hands-on. Work remotely from Poland with a modern stack including TypeScript, React, React Native, React Native Web, Nx, pnpm, TanStack Query, Zustand, Playwright, Detox and Jest; salary is competitive and discussed during the process. Apply to influence products at meaningful scale, mentor senior engineers and create durable improvements across web and mobile.
Required Skills
Never miss a JavaScript opportunity
Subscribe to get similar jobs and weekly insights delivered to your inbox
Hiring JavaScript developers?
Post your job to 10,400+ registered developers. Starting free.
See PricingRelated jobs
Is this your listing? Claim or request removal