Senior Frontend Engineer — Scientific Applications
Free to start · No card · 5 credits the moment you sign up
Job description
Location: Remote within Europe, with regular presence in Bremen
Direct Reports: None
Working Model: Remote / hybrid. Regular time on-site in Bremen.
Mission
Own the interface layer for a scientific platform used by research teams to run complex physical experiments. The work is heavier than typical product frontend — live experiment monitoring, workflow graphs, large result sets, and users who are physicists rather than consumers. The Senior Frontend Engineer owns that layer end to end and sets the standard for it.
Responsibilities
Pillar 1 Frontend Ownership
- Own the architecture, code and standards for the platform frontend.
- Build and maintain complex interactive visualisation: directed workflow graphs, live monitoring, large-scale result inspection.
- Handle long-running asynchronous work properly — progress, failure states, partial results.
- Lead the migration to the Constructor React component library.
Success Metrics and KPIs: interface stability, adoption by the research team, migration delivered.
Pillar 2 Quality and Practice
- Bring test coverage and review discipline to a codebase built at research pace.
- Establish component standards and a shared design language with the wider Constructor frontend group.
- Reach into the backend when that is what unblocks the work.
Success Metrics and KPIs: test coverage, defects reaching users, review turnaround.
Pillar 3 Working with Scientists
- Work directly with the physicists who use the interface. Understand the experiment, not just the ticket.
- Turn vague scientific requirements into concrete interface decisions.
Accountability: researchers able to run and monitor experiments without asking for help.
Requirements
Experience
- 8+ years frontend engineering with strong React. We will also talk to you if your recent work has been Svelte, Vue or Angular.
- Data visualisation beyond charting libraries — D3, custom SVG, graph layout algorithms.
- TypeScript at production scale.
- Comfortable writing backend code in Python or similar when needed.
Skills & Competencies
- Able to own a layer alone and still work well in a team.
- Honest about technical debt and weaknesses in your own work.
- Good judgement on when to build custom and when to use what exists.
- Clear communication with non-frontend colleagues.
Education & Languages
- Degree in computer science, engineering or equivalent practical track record.
- Fluent English.
What This Role Is (and Is Not)
This role IS
- Full ownership of a complex, technically interesting frontend.
- A role with peers and code review, in a group that values the work.
- Hands-on individual contribution at senior level.
This role is NOT
- A design role.
- A management role.
- Standard CRUD product work.
Prepare your application
Use the description above to assess your fit for Constructor Labs. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.