Aqora | Paris, France / US / Remote (EU) | Multiple roles | https://aqora.io
Aqora is the "Hugging Face for quantum computing". We host datasets, benchmarks, and use-case challenges, plus the orchestration layer to run quantum algorithms and workflows across hardware backends, so results are reproducible, comparable, and actually move the field forward. We grew out of the QuantX hackathons at École Polytechnique and now run competitions and a public datasets hub for partners across pharma, finance, energy, and defense.
We're hiring:
* Senior Full Stack Software Engineer (Rust/React). Build the platform end to end: datasets hub, challenges, leaderboards, and the workflow engine that orchestrates quantum jobs across backends. You own features from schema to UI and care about developer experience. Bonus: data, ML, or research-platform experience.
* Quantum Computing Expert. Design challenges, curate datasets, define benchmarks, and shape how algorithms and workflows run on the platform. Work directly with enterprise partners to translate their problems into something the community can solve. PhD or equivalent depth in quantum algorithms, QML, or optimization.
* Chief Commercial Officer, US. Own US go-to-market end to end: strategy, enterprise pipeline, team build-out. You've scaled commercial functions at a deep-tech, dev-tools, or research-platform company. Based in the US.
* Head of Marketing. Positioning, demand gen, and brand for a category still being defined. B2B technical marketing background required; quantum experience welcome but not necessary, curiosity is.
* Product Manager. Drive the roadmap across the datasets hub, challenges platform, benchmarks, and workflow orchestration. Strong technical instincts and experience shipping developer or research-facing products.
* Sales, EU. Enterprise sales into R&D and innovation teams across Europe. Long, technical sales cycles, consultative selling, comfort talking to PhDs and procurement on the same day. EU-based, remote.
Reach out to jannes[at]aqora.io with a short note on why this problem space and what you've built or sold before.
BlueQubit's CPU/GPU simulators are exact statevectors — they store the full 2^n amplitude vector, so 34–36 qubits is the hard ceiling regardless of circuit structure. We take a different approach: MPS/tensor-network representation that scales with entanglement rather than qubit count. For highly entangled circuits we're strictly worse. For structured circuits (most variational, most shallow) we can go much larger. Complementary tools really.
Very interesting! I’ll certainly try it out. I am wondering though what’s the advantage over doing it with a K8s operator (disclaimer, I created and maintain https://github.com/openclaw-rocks/k8s-operator)?
Also, I am genuinely curious about the choice of license.
Given the „new (agentic) way“ in that software is being developed now, don’t you think it can be copied easily and that this kind of license will hinder adoption at some point?
Thanks! The main advantage is simplicity. klaw is a single binary with zero dependencies, no k8s cluster required. For teams already running Kubernetes your operator makes a lot of sense, but most teams we've talked to managing AI agents don't have or want a k8s setup just for that. klaw gives them the same mental model without the infrastructure overhead.
On the license, fair question. The SaaS restriction is narrow, it only prevents someone from reselling klaw as a hosted orchestration service. Internal use, building on it, extending it is all fine. We looked at what Elastic and HashiCorp did and felt this was the right balance for now. Could it slow adoption? Maybe. But we'd rather start here and open up further based on how the community evolves.
OpenClaw is all the hype right now. I played around with it over the weekend and ended up writing a Kubernetes operator for it.
There have been a lot of security concerns around running OpenClaw, and rightfully so. This operator tries to mitigate the ones it can at the infrastructure level: non-root execution, all capabilities dropped, default-deny NetworkPolicy, a validating webhook that blocks root containers. It won't help with what the agent's skills do, but at least the blast radius is contained.
Full disclosure: this was largely vibe-coded with Claude Code. Some highlights of what came out of it:
- Config changes trigger automatic rollouts via SHA-256 content hashing
- Optional Chromium sidecar for browser automation, hardened with its own security context and shared memory tuning
- The whole thing is a single CRD, so going from zero to a secured instance is just a kubectl apply
thanks! Can you confirm it's working now? Apparently, Firefox's Enhanced Tracking Protection blocked the Ahrefs analytics script and the way it was handled ended in some endless loop. Should be fixed now
Repo: https://github.com/paperclipinc/mitos
reply