XCEED - Job offers, offices and team

First name *

Last name *

Phone *

Email *

Personal URL *

Cover letter

Curriculum vitae *

Upload file (max. 10MB)

How did you hear about this job? *

Glassdoor / Indeed

Social Media (IG)

Wellfound

Music Job Portals (MBW, ROSTR)

University Job Portals

Other

Do you need visa sponsorship to work? *

Yes

No

Salary Expectations (+ OTE Split) *

Notice Period? *

Github *

Which frontend state-management or data-fetching paradigm are you most proficient in? *

React Context / Redux Toolkit

Zustand / Jotai (Atomic/Zustand style)

TanStack Query (React Query) / SWR

Apollo Client / GraphQL

I prefer native browser APIs / minimal external tooling

How many years of professional software engineering experience do you have? *

Less than 3 years

3–5 years

6–8 years

9+ years

Select the areas where you possess expert-level, production-tested experience (Select all that apply): *

Developing/maintaining shared component libraries or design systems

Web Performance Optimization (managing INP, LCP, bundle budgets)

Web Security & Sanitization (XSS mitigation, secure data handling)

B2B SaaS architecture and incremental legacy migrations

The B2B and B2C teams have solved the same technical problem in two entirely different ways. As a Staff Engineer, what is your default approach? *

Maintain the separation; B2B and B2C have fundamentally different user behaviors and scaling constraints, so forcing a single solution compromises team velocity.

Evaluate both implementations to understand their trade-offs, then work with both teams to converge on a shared solution only where the duplication incurs real maintenance or business costs.

Draft a technical standard based on whichever implementation has higher test coverage and better documentation, then roll it out across both orgs to ensure consistency.

Escalate the duplication to engineering leadership to establish a centralized architecture review board that can make a definitive, top-down decision.

A breaking change is needed in a component library shared across several of our apps. What is the best approach to handle this? *

Ship it to main directly; the consuming teams will adapt.

Never make breaking changes—only ever add new props.

Fork the component library per app so no one is affected.

Release it as a new major version with a migration guide, and deprecate the old API on a clear timeline.

Tell us about a specific feature or architectural change you successfully developed in a past role. What went well, what went wrong, and looking back, how would you improve it today? *

I have read and I accept the Privacy Policy

Yes, XCEED can add me to the talent pool and contact me about future job opportunities.

Something went wrong. Try again later.

Frontend Staff Engineer

Personal information

Application information

Questions

This website uses cookies