Systems Engineer

Who We Are We are an ambitious, committed and seasoned team of systems engineers, cryptography specialists, security analysts, data scientists, and customer-facing managers. We are looking for people that embrace an engineering mindset to build what hasn’t been built and can apply their skills to solve hard, complex problems. We develop the security infrastructure of mobile apps to allow app developers to work with clean first-party data. We believe data is critical to making informed decisions for any organization, be it in understanding the app’s user base or in protecting their operations. We build software that operates in big data pipelines that spans millions of devices a day and is subject to constant and rigorous adversarial threats. We operate in a wide variety of platforms and chip architectures, each with their own quirks and faults. Above all, we deliver reliable and frictionless technologies that enhance the life of a mobile app using a cross-disciplinary tech stack. To give some examples: Zero-knowledge and privacy-preserving cryptographic protocols Embedded systems Networking protocols Compiler theory Data science Security analysis Deployment infrastructures Web analytics Web microservices and job queues Data aggregation in real-time across millions of records In several of these areas, we work with state-of-the-art research. We actively read, implement and encourage reading research papers. You will work with seasoned engineers that have built performant production systems that process petabytes of data for billions of end users on daily basis. About the role We’re looking for a systems engineer to own, maintain and innovate in our core library technology that runs on mobile apps. There will be a lot of protocol design, applied cryptography, adversarial thinking as well as low-level optimizations to cryptographic protocols. Everything we do on the library must support hundreds of different manufacturers, different platforms, and different compilers. Must haves A strong C/C++ background and understand the different cross-compilation toolchains involved in that world Have shipped and maintained production code that ran on client devices Are fluent in concurrency, profiling, and keeping latency down Think adversarially by default. Almost every protocol we build is public-facing and will be attacked Are comfortable reading a cryptographic protocol spec and reasoning about what it does and doesn’t guarantee Able and keen to learn new technologies: in-between the backend, library and frontend, there are about 7 different programming languages and even more frameworks Able to look at time series graphs and understand the real-life impact of the systems you’ve built and algorithms you’ve implemented Are able to look at a binary from an attacker’s point of view as well as a defender’s point of view Are able to outline how compilation pipelines work in the Android and iOS worlds Nice…