Remote Cryptographic Algorithim Designer Jobs Turing

Job Responsibilities: • Develop highly performant in-database procedures to ensure that SQL results are tamper-proof and cryptographically guaranteed in collaboration with expert engineers, cryptographers, and mathematicians • Architect and develop a novel proof of SQL mechanism • Construct strategies, tools, platforms, and database connections • For outsourced Proofs of SQL, quickly test and iterate on various cryptographic techniques/commitment schemes/database designs/algorithms • Codify best practices for future reuse in the form of accessible, reusable patterns, templates, and codebases • Streamline the collection and management of metadata • Experience working with Cryptography/SNARK engineering research • Work with engineering leadership to design, prioritize, and guarantee that other operational components are deployed smoothly Job Requirements: • Bachelor’s/Master’s degree in Engineering, Computer Science (or equivalent experience) • At least 3+ years of software engineering experience (or academic research) around applied math programming • Fluent with the mathematics required for basic cryptographic primitives • Experience with Rust (or other similar languages) and math-focused algorithms • Ability to build a bigger, better, faster, more optimized SQL proofing mechanism • Solid understanding of elliptic curves and various cryptographic protocols (Diffie–Hellman key exchange, commitment schemes, hashing, etc.) • Knowledge and experience with SNARKs like Bulletproofs, Spartan, KZG • protocol, sum-check protocol, FRI commitments, etc. is nice to have • Experience writing/developing novel algorithms (such as sorts, searches, divide-and-conquer, etc.) • Ability to clearly communicate developed algorithms, e.g., by using pseudo-code • Ability to read and interpret research papers • Familiarity with Scala and other similar languages is desirable • Familiarity with SQL/database design is nice to have • Nice to have some familiarity and interest in Web3, blockchain, decentralization, and some understanding of how SNARKs and arguments play into this