Responsible for defining new features, behaviours and implementations for both Starknet and StarkEx product families. Architectures involve backend systems in AWS, GCP (Python, Rust, Kubernetes, Aerospike) and also contracts in blockchains (Ethereum and Starknet, Solidity and Cairo). Also a member in the company's management forum. Starknet (https://starknet.io) is our layer2 blockchain that allows writing smart contracts at more than two orders of magnitude scale (TPS) comparet to Ethereum. The backend is a cluster of machines that create the blocks: accepting transactions in gateway instances, validating, ordering for inclusion in the block, executing and producing the output. An extensive RPC layer provides information about the blockchain status. StarkEx, our decentralised exchange product, processes 1M transactions a day with total worth of $2B a day and has cummulatively process more than $1 trillion in transactions. It is a large capacity backend that accepts transactions from the exchanges that build on top of it, packages them and sends them for proving.STARK is a cryptographic protocol in the family of Zero Knowledge proof systems. It allows prove a computation was done without revealing it. This means one can verify it was executed without the need to spend the same time as the execution itself. In fact, while proof generation takes O(nlog(n)) (n being the size of the computation), verification is done at O(log^2(n)). In the context of Ethereum, it means paying reduced fees and being able to execute much more. Cairo is a language that allows to define computations (such as trading, transfers, or anything) such that a proof can be generated for them.

Manager of managers of an organization of 38 people (20 US, 9 PLN, 9 IND), in charge of creating and operating cloud components and infrastructure to support our different products backends. In parallel of being Chief Architect for the BU.

As the chief product architect of the Web Cyber Security BU (>$1B revenue, ~1500 people, ~500 R&D, and growing), in parallel to my role as cloud infrastructure manager, I'm responsible for managing a team of 12 product architects (3 IL, 8 US) that defines the end to end architecture of security/cyber products over Akamai's massively distributed and high scale SAAS/Cloud architecture (~200,000 edge servers, handling 25% of the entire internet traffic). These products are used by thousands of the largest enterprises in the world. I specialize in security, distributed architectures, and big data processing ( ~3000 machines in two Hadoop clusters, 500 TB compressed data per day, 8PB total).I personally created several new products in domains that were new to Akamai (Client Reputation, ETP DNS protection, Page Integrity). See my projects for more information on each.Participated in M&A diligence for several companies.

As CTO at Tikal I have two hats: Like all Tikalists, I'm a senior team member of a client. As CTO my job is to recognize new trends and technologies and internally promote them in Tikal so we know them before our clients and day-to-day marketing efforts (conferences, site, presentations)During my time at TIkal I've been hands-on working for customers. This meant joining the R&D team and leading the architecture and implementation of their infrastructure. I've had positions at 3 customers (see projects)Professional work in Java, Scala, Ruby, Javascript, using OSGi, Actors, Spring

During my 6 years at Qlusters I created its flagship product QRM (qlusters' resource management), later openQRM. The product was essentially a cloud management platform, before its time. It allowed to managed matching applications with physical or virtual pool of machines, allowing automatic scalability. The system was highly pluggable and customizable to allow it to match any customer needs. Its largest user was NetApp that used it to manage its 2000 machine lab for customers to test storage servers.I created the product from its initial vision: selecting the technology, design, coding, recruiting people, developing methodologies etc. I coded major parts of the system and also worked with PM and PS to define future features and customer solutions. I introduced some new technologies (then) such as using the SEDA paradigm to allow scalability and locking, wicket for componentize our web interface, REST for APIs, JPF for making it pluggable, maven for the build. The product was managed in an Agile way: virtual teams were formed for complex features, releases were made every 3-4 months, with intermediate drops. A total of 12 versions were released, all on time. The product was developed by 2 teams (java & system) of about 10-12 people in total and included working with remote developers

Team member in the engine (core) team, developing heuristic algorithms and data structures in Java for a semantic web crawler server.

Infrastructure team, developing a technology that allows to embed CAD models in Robcad and interact with them through the CAD system, to get more accurate information. Worked in C++. Was a guru of the company in C++