First and most important:
To work on this project, you should have a genuine passion for privacy and security, and a deep belief in the importance of real privacy, especially in a world where so many overlook it. The general lack of awareness about privacy among users and companies can be frustrating, so having your own drive and conviction will be essential to keep you motivated and inspired.

Next:
For this position, I’m looking for someone who can shape our marketing strategy, build our brand, and communicate the unique value of our products, such as the encrypted web survey MVP and the “private Google Analytics” MVP, to the world. You’ll be instrumental in developing messaging that resonates with privacy-conscious users and organizations, creating campaigns, building partnerships, and driving traction for truly private analytics. Eventually we would like to progress the industrial state of the art in the same fashion is signal did.

You’ll also work closely with me to help translate complex privacy technology into clear, compelling stories for different audiences. While you don’t need a technical background, a basic understanding of privacy-enhancing technologies (or a willingness to learn) will help you succeed in this role.


Optionally:
If you have experience in tech marketing, product launches, or even a background in security or privacy, that’s a big plus. Ultimately, I’m looking for someone who can take the lead on marketing and help us disrupt the analytics market with a privacy-by-design approach.

First and most important:
To work on this project, you need to have a strong affinity for privacy and security, as well as a solid conviction about the current lack of privacy and a personal drive to do something about it, regardless of the outcome. Otherwise, the widespread lack of awareness about privacy among end-users and companies will eventually sap your motivation to continue (speaking from experience).

Next:
For this position, I’m looking for someone to join me in coding the actual engine, or building products that use this engine, such as the web survey MVP or the “private Google Analytics” MVP. There’s plenty of “non-cryptographic” implementation work to do, involving standard back-end and front-end development. The engine itself is written in Go, with several bindings to C++, WASM, and JS/HTML/CSS components for the front ends. We’ll also need to set up a CI/CD toolchain sooner rather than later.

Optionally:
In the very unlikely (but not impossible) case that you’re a cryptology researcher—or at least familiar with concepts like homomorphic encryption—that’s a bonus, but not required. I am a cryptographer myself, and the engine is designed so that I can handle the cryptographic programming, while you can focus on other areas. But ideally we can do all things on par.