Developer gesucht für Encrypted Stream Processing API Engine

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.

• Go
• Frontend
• Backend
• Cryptography
• Privacy
• Security

Du bist gut mit...

• Zahlen, Daten und Logik
• Dinge vorantreiben und erledigen
• Strukturen und strategischem Denken

Du hast bereits...

• als Vollzeitbeschäftigter gearbeitet

Back-end development (Go): Write and maintain Go code for the encrypted stream processing engine, and integrate Go with C++ and WASM components as needed.

Front-end development: Develop user interfaces using JS/HTML/CSS for the web survey and analytics dashboards. Connect front-end components to the engine and ensure smooth data flows.

CI/CD setup and automation: Set up and maintain continuous integration and deployment pipelines.

General product development: Collaborate on architectural decisions for both the engine and product development. We will need to do some serious design work to create a seamless streaming and funneling architecture for encrypted streams.

(Optional) Research publications and projects: Our work implements products based on the bleeding edge of security and privacy research. If our results are promising, we may consider publishing at scientific conferences.

- The chance to fulfill your desire to actively combat the lack of real privacy and security with your own hands. If this doesn’t resonate with you, then you’re not the target audience. This is not about money, it’s about a calling at this stage.

- Co-founder position with equity. Later a CxO position that makes sense for you. Or not. You are a co-founder, so you decide with us.

- We have contacts with VCs; funding may become an option in the near future, though (as always) it’s uncertain.

- Our wishfull thinking is to create a working and profitable business with a four-day cycle. We’ll see how this works out.

Don't advertise with privacy first. First, build a top-quality service then say: By the way, everything is fully private. That’s privacy-by-design.

A wide range of web services for streaming data analytics are currently available, such as web surveys, web analytics, product usage analytics, stream filtering, and much more. However, most of these services hardly respect privacy. And if they claim to do so, it usually just means: (A) We use TLS, (B) We don’t log your metadata, or (C) We solemnly promise not to share your data. This is not enough, as the current state of the art in Privacy-Enhancing Technologies (PETs) has progressed much further.

We are developing an encrypted stream processing engine that can enable all these use cases in a truly private way. A first MVP for web surveys is already available. A second MVP, a private alternative to Google Analytics that is just as easy to integrate, has already been tested. The front end for this will soon appear on our landing page. The code is openly available for anyone interested.

Herausforderungen

The team currently consists of only one person. Accordingly, the main focus is on the typical tasks of an early-stage project.

Currently, the most important priority is:
- Gaining initial traction with a functional MVP. We are therefore looking for support in development.

Zielgruppe

Our “final” target group consists, on the one hand, of citizens as end users of our products, and on the other hand, of companies and self-employed individuals who process personal or otherwise sensitive data.

As long as our services have not yet reached full maturity, we are initially focusing on user groups with a strong affinity for privacy and security.

Target groups with compliance requirements are currently not explicitly addressed, but they are not excluded either.