Senior Technical Advisors (2): Post-Quantum Cryptography and Migration; Space and Critical Systems

We are looking for two senior technical advisors. Not for today's problems. For the ones that show up in 2032 and 2036.
A short note on how we think, so you know whether this is for you.
We do not treat a claim as true until a third party can verify it offline, without trusting the people who made it. Most of what passes for security is a promise with a logo on it. We are building the opposite: systems where every decision, every key change, every migration step leaves a signed record that a stranger can check years later, with a verifier they wrote themselves. If the proof cannot survive without us, we have not built anything.
We also believe the post-quantum migration everyone is discussing is the small part. The real question is what comes after. Algorithms will fall again. Keys will move again. Machines will sign for machines at a scale no human reviews. Satellites and autonomous systems will take decisions out of reach of any operator, and someone will have to prove afterwards that the right rule was followed. Whoever owns the evidence layer when that happens sets the terms. We intend to be there ten years early, with the hard parts already proven and the boring parts already boring.
What we are building, at the level we can say publicly: R-Series, a post-quantum trust and evidence programme. Hybrid signatures and key exchange, crypto agility from the first line, key lifecycle, zero knowledge proofs, hash chained receipts verifiable offline, and a staged migration path for estates that already run. The same base extends to critical infrastructure (OT and IoT in dams, refineries and utilities) and to space and autonomous systems. Our own engineers write the code. Independent reviewers from two different model families audit every candidate. Nothing is called certified until an independent certifier signs the record. Today that number is zero, and we say so.
We know our weak points. We keep a register of every finding since the first line of code, classified by fault pattern, and we publish the rules that came out of it to every engineer before they write a new path. What we want from an advisor is the finding our register does not have yet. The assumption that holds in 2026 and breaks in 2034. The downgrade path in a hybrid construction when one half falls. The clause in a standard that was politics, not mathematics. The part of a refinery network the vendor diagram leaves out. The failure mode of a command authoriser when the link is gone and the satellite has to decide alone.
The person we are looking for reads a design and cannot stop asking the next question. Who builds a mental model of the attacker that does not exist yet. Who knows the old paper that already answered what everyone is debating today. Who is more interested in being right in ten years than in sounding right today.
Who qualifies:
A PhD in post-quantum cryptography, lattice cryptography, protocol security, formal verification or cryptographic engineering, with published work. Fresh or established, both. The field is young and some of the sharpest people in it finished their thesis in the last few years.
Or a Master's degree with five years or more of hands on work in cryptographic systems, PKI, HSM and KMS design, key management at scale, or standards work at NIST, IETF, ETSI, ISO, or Indian bodies such as BIS, CERT-In, C-DAC or DRDO.
For the space and critical systems seat: flight software, satellite command and telemetry, or mission assurance, whether at a national space agency (NASA, ESA, ISRO, JAXA, CNES, DLR, UKSA, CSA or any other), a defence or research lab, a university satellite programme, or a private operator anywhere in the world; or industrial control security in oil and gas, power or water, with IEC 62443 or equivalent on record.
We will start with two advisors, one for cryptography and migration, one for space and critical systems, and each reads the full project, not a slice of it. Anyone, anywhere in the world. Your location, employer or current situation does not matter to us; your thinking does.
These two seats form the technical advisory board of DCS AI Technologies. Advisors are named on our website and in our certification record with their consent, and sit in the quarterly design review with the founder and the principal cryptographer.
Evidence we ask for: a published paper or thesis, a granted or filed patent, a standards contribution, cryptographic code you are free to show us, a conference talk, or an audit or review report you are free to share. Any one of these is enough; a CV alone is not.
Role details
Engagement: paid advisory, part time, hybrid. Remote from anywhere in the world; visits to our Hisar office optional and paid for.
Commitment: one or two long sessions a month plus written review of project documents, roughly six to ten hours a month, and the freedom to disagree with us in writing.
Minimum experience: five years in the field, or a completed PhD in a listed area.
Evidence we ask for: published papers, standards contributions, open source cryptographic code, conference talks, or audit and review reports you authored. Any one of these is enough; a CV alone is not.
Term: twelve months, renewable, with a review after the first ninety days on both sides.
Compensation: monthly retainer, discussed privately, paid in USD or INR as you prefer. After the six month review, advisors we want to keep for the long run are offered equity under our advisor option plan, in addition to the retainer.
Start: as soon as the NDA is signed and the first document pack is issued.
Confidentiality is a condition, not a formality. A mutual NDA with a five year term is signed before any document is shared, covering non-disclosure, non-use outside the engagement, no onward sharing of materials or findings, return or deletion of documents when the engagement ends, and no public reference to the work without written consent. Nothing moves until it is signed.
If you read this and already have an objection, that is the person we want. Apply here, or write to founder@dcslabs.ai, with your background, the seat you would take, and the objection.

Work arrangement
Hybrid