Software Architect

Our Mission: Qblox is a deep-tech scale-up whose mission is to accelerate the worldwide race towards scalable quantum computers. We provide some of the world's most advanced quantum control stacks to laboratories and quantum startups across the globe. Our hardware and software sit right next to the quantum chips, giving experimentalists precise control and readout of their qubits. Through our open-source interfaces (qblox-scheduler and qblox-instruments), users can write and execute experiments and algorithms using Python—from defining quantum circuits to compiling down to our quantum assembly, Q1ASM. We offer a dynamic environment where engineering meets cutting-edge physics research. Your Mission: Architecting at the Edge of Physics and Engineering We need a Software Architect who understands the full stack—from FPGA firmware through embedded systems to high-level Python APIs—and can design the architecture that ties it all together. You will own the technical vision for how our control stack scales from hundreds to thousands of qubits and beyond. This role is both strategic and tactical: you will shape the long-term architectural direction while maintaining a firm understanding of the hardware realities underneath. You are shaping a vision, not micro-managing progress, and we need a leader who makes engineers better, unblocks them, and builds consensus around technical direction. Key Responsibilities Strategic Architecture Define the Control Stack: Design how firmware, embedded software, compilers, and high-level APIs work together as we scale to thousands of qubits. Plan for Scale: Architect solutions that work today and scale 10x without fundamental rewrites. Enable Product Vision: Work with product managers and application engineers to translate user needs into architectural decisions that actually work. Collaborative Direction: Build consensus on abstractions, interfaces, and trade-offs, and convince teams through clarity, not authority. Bridge Teams & Establish Patterns: Connect hardware, firmware, software, product, and application engineering teams around a shared technical vision, defining standards that teams actually want to follow. 2. Tactical Execution Unblock Teams: Jump into the hardest technical challenges when teams are stuck, including instruction scheduling bottlenecks, timing constraints, compiler optimization, and distributed control. Debug Across Layers: Trace issues from Python down through the compiler, firmware, and FPGA when things do not work as expected. Code When it Helps: Write critical code, prototypes, or proof-of-concepts to validate architectural decisions or show teams the path forward. Guide, Don't Gatekeep: Review designs with a focus on helping engineers succeed, rather than finding reasons to say no. Listen to Users: Work with customer-facing teams and customers to understand where the architecture is helping or getting in the way. Experience: 10+ years of software…