| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Belmont Lavan Ltd | United States | $90k - $105k | |||
Belmont Lavan Ltd | United States | $54k - $87k | |||
O1labs | Remote | $88k - $150k | |||
Provable | San Francisco, CA, United States | $68k - $80k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
Nexus | New York, NY, United States | $87k - $150k | |||
Succinct | Remote | $125k - $175k | |||
Provable | San Francisco, CA, United States | $90k - $90k | |||
Nexus | San Francisco, CA, United States | $87k - $150k | |||
Anza | United States | $90k - $150k | |||
Succinct | Remote | $125k - $175k | |||
Aztec | Remote | $140k - $150k | |||
IO Global | Remote | $105k - $150k | |||
ether.fi | New York, NY, United States | $150k - $200k | |||
Matter Labs | Remote | $90k - $150k | |||
Aztec | Remote | $84k - $112k |
As Web3 Architect, you will be responsible for defining and shaping the overall technical strategy for blockchain-based systems. You will lead architectural design, tooling decisions, protocol selection, and ensure secure, scalable, and interoperable solutions. You will work closely with other architects, engineering teams, product managers, and external partners to ensure we deliver cutting-edge Web3 products.
Key Responsibilities
- Define system architectures for decentralised applications , smart contracts, blockchain networks, side-chains, layer-2 solutions and/or roll-ups.
- Select appropriate blockchain protocols , consensus mechanisms, and scaling solutions based on use case.
- Lead smart contract design and audit reviews to ensure security, gas optimisation, upgradeability, and best practices.
- Design and integrate interoperable systems, bridges, or cross-chain communication where required.
- Evaluate and adopt decentralised storage, identity, oracles, oracles, zero-knowledge proofs, and privacy enhancing technologies.
- Oversee decentralised governance, tokenomics design, and incentive mechanisms in line with business objectives.
- Define and enforce security, compliance, and regulatory best practices where applicable.
- Guide tooling, CI/CD pipelines, developer SDKs, testing frameworks, and infrastructure required for Web3 deployment.
- Mentor engineering teams to embed Web3 engineering culture and practices.
- Monitor emerging developments in the Web3 / blockchain space and recommend adoption where beneficial.
- Strong experience (5+ years) in designing and delivering blockchain / decentralised solutions, smart contracts, or Web3 platforms.
- Proficiency in one or more smart contract languages.
- Deep understanding of various blockchain architectures ,layer-2 (optimistic / zk-rollups), side-chains, sharding, and scalability trade-offs.
- Familiarity with formal verification, gas profiling, security auditing, threat modelling.
- Experience integrating and managing oracles, identity protocols (DID), privacy technologies.
- Strong software architecture skills: microservices, modular design, event-driven systems, API design.
- Excellent understanding of cryptography fundamentals, consensus algorithms, distributed systems.
- Skilled in infrastructure and operations: node operation, wallets, key management, deployment pipelines.
- Good experience with cloud platforms and container orchestration (Docker, Kubernetes) is advantageous.
- Excellent communication skills; able to explain complex technical topics to non-technical stakeholders and lead cross-disciplinary teams.
What is Zero-knowledge?
Zero-knowledge is a concept in cryptography that allows two parties to exchange information without revealing any additional information beyond what is necessary to prove a particular fact
In other words, zero-knowledge is a way of proving something without actually revealing any details about the proof
Here are some examples of zero-knowledge:
- Password authentication: When you enter your password to log into an online account, the server doesn't actually know your password. Instead, it checks to see if the hash of your password matches the stored hash in its database. This is a form of zero-knowledge because the server doesn't know your actual password, just the hash that proves you know the correct password.
- Sudoku puzzles: Suppose you want to prove to someone that you've solved a particularly difficult Sudoku puzzle. You could do this by providing them with the completed puzzle, but that would reveal how you solved it. Instead, you could use a zero-knowledge proof where you demonstrate that you know the solution without actually revealing the solution itself.
- Bitcoin transactions: In a Bitcoin transaction, you prove that you have ownership of a certain amount of Bitcoin without revealing your private key. This is done using a zero-knowledge proof called a Schnorr signature, which allows you to prove ownership of a specific transaction output without revealing the private key associated with that output.
- Secure messaging: In a secure messaging app, you can prove to your contacts that you have access to a shared secret without revealing the secret itself. This is done using a zero-knowledge proof, which allows you to prove that you have access to the secret without actually revealing what the secret is.