Lead Cryptography & Systems Architect

Project Overview We are building a groundbreaking, patent-pending healthcare and identity infrastructure: Federated Edgetic Weight Sharing (Holo-Q). Our architecture fundamentally changes how highly sensitive genomic and medical data is handled. Instead of centralizing 200GB raw genomes on vulnerable cloud servers, the raw data remains permanently locked in an institutional vault (Privacy-by-Localisation). Only a highly compressed, sparse Protein-Protein Interaction (PPI) network (~3MB) is provisioned to the patient’s mobile device. This mobile cache is maintained inside the hardware Secure Enclave, updating via federated learning, and acting as a high-entropy seed for Zero-Knowledge Proofs (ZKP) and future post-quantum authentication frameworks. We are looking for a Senior/Lead Systems Engineer with deep expertise in applied cryptography, mobile Secure Enclaves (iOS/Android), and secure federated systems to build out the Proof of Concept (PoC) and core data pipelines. What You Will Be Building You will be responsible for architecting and coding the core three-tier custody chain: The Secure Downlink: Creating a mutually authenticated, attested pipeline (TLS 1.3 + Remote HW Attestation) to securely provision the ~3MB sparse network payload from a server into a mobile hardware enclave. The Mobile Enclave Cache: Writing the on-device logic (Swift/CryptoKit for iOS, Kotlin/StrongBox for Android) to store, lock, and manage this ~3MB lattice inside the enclave. The Updatable Edge Dictionary: Implementing the federated update logic where the server broadcasts a "locked edge dictionary" and the phone locally calculates and returns encrypted delta weights (kilobytes) without exposing the underlying data. ZKP / Lattice Auth (Phase 2): Using the on-device lattice as an entropy seed—optionally combined with Quantum Random Number Generator (QRNG) inputs—to generate a zero-knowledge proof for third-party verification. Required Tech Stack & Expertise Applied Cryptography: Deep understanding of TLS 1.3, end-to-end encryption, remote attestation, and key escrow. Familiarity with Lattice-based cryptography (LWE) or Zero-Knowledge Proofs (zk-SNARKs/STARKs) is a massive plus. Mobile Hardware Security: Proven experience interfacing with Apple Secure Enclave (AES/CryptoKit) and/or Android Keystore/StrongBox. Data must remain encrypted in memory and execution environments. Backend & Systems: Python, Rust, or C++ for building the simulated Institutional Vault and the federated aggregator. Architecture & Threat Modeling: Ability to design systems resistant to device-tampering, jailbreaking, and man-in-the-middle attacks. What We Already Have You will not be designing the biology or the math from scratch. We have: Extensive patent documentation, architecture whitepapers, and biological network specifications. The exact size and shape of the data payloads (e.g., node mappings, fp16 weights, ~133M pair lookup tables reduced to sparse 450k-edge JSON/binary payloads). Defined workflows for QRNG integration and federated learning epochs. Project Phases / Milestones Milestone 1: Architecture Review & Threat Model. Finalizing the tech stack for the PoC. Milestone 2: Simulated Vault to Mobile Enclave Downlink. Successfully passing a dummy 3MB binary payload into an iOS/Android enclave using remote attestation. Milestone 3: Federated Delta Updates. Simulating a global model upgrade where the phone receives new "edge" definitions, updates its local lattice, and transmits a kilobyte-scale ZK/encrypted delta back to the server. Screening Questions (Please answer in your proposal): Have you previously built applications that directly utilize the Apple Secure Enclave or Android StrongBox for storing arbitrary secrets/payloads? Please describe. How would you approach verifying remote hardware attestation (ensuring the mobile device isn't jailbroken/rooted) before an institutional server releases a sensitive payload? What is your experience with implementing Zero-Knowledge Proofs or Lattice-based cryptographic schemes in production or PoC environments? Please link to any relevant GitHub repositories or past projects involving federated learning, cryptography, or secure mobile development. To Apply: Please start your proposal with the word "LATTICE" so we know you have read the full description. We prioritize engineers who can explain complex cryptographic trade-offs simply.