Principal Software Architect — Quantum Platform
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 initially; technical leadership across the engineering group
Mission
Own the architecture of the software platform on which Constructor Labs' quantum group builds. The platform drives physical quantum hardware end to end — calibration, orchestration, experiment execution and device state — and must work both in our own cloud and on customer premises, including restricted and air-gapped environments. The Principal Architect sets the technical direction, makes the structural decisions, and is the senior engineering voice in a group where research and engineering sit closely together.
Responsibilities
Pillar 1 Platform Architecture
- Own the end-to-end architecture across backend services, job orchestration, hardware abstraction and device state management.
- Define the interfaces between the scientific layer and the platform layer so physicists can work without engineering support.
- Make and carry the build-versus-buy and framework decisions; document them so they survive the people who made them.
- Lead the migration of the platform onto the Constructor technology stack.
Success Metrics and KPIs: architectural decisions documented and adopted, platform stability, migration delivered to plan.
Pillar 2 Hands-on Engineering
- Write production code in the core of the system, not only design documents.
- Own the hardest components personally — those where correctness and performance both matter.
- Set and enforce engineering standards: testing, review, structured logging, dependency governance.
- Remove single points of failure so no component has only one person who understands it.
Success Metrics and KPIs: test coverage, review discipline, bus factor above one on every core component.
Pillar 3 Working with Research
- Work day to day with research physicists, translating experimental workflows into software.
- Keep the research and engineering collaboration model intact as the group grows.
- Support the product function with realistic estimates and honest technical constraints.
Accountability: research team able to run experiments without engineering bottlenecks.
Requirements
Experience
- 10+ years building production software systems, with real depth in Python, C#/.NET or C++.
- Distributed systems, job scheduling, and interfacing with instruments or physical hardware.
- Track record as the senior technical voice in a small team.
- Delivered software into on-premise and restricted environments, not only cloud.
Skills & Competencies
- Able to hold an architecture in your head and explain it simply to people who are not engineers.
- Comfortable in a scientific domain. A physics degree is not required, genuine interest is.
- Pragmatic about trade-offs; able to ship rather than perfect.
- Strong written communication. Decisions that are not written down do not exist.
Education & Languages
- Degree in computer science, physics, engineering or equivalent practical track record.
- Fluent English. German useful, not required.
What This Role Is (and Is Not)
This role IS
- Deeply hands-on, with real authority over technical direction.
- Central to everything the quantum group builds.
- A role where you will have peers and a platform behind you.
This role is NOT
- A management track role.
- An architecture-committee or advisory position.
- A role where someone else writes the hard code.
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.