Software Engineer

SAP
Sep 2018 - Present

Software engineer part of the SAP cloud platforms team.
SAP Cloud Platform is a flagship product which used by strategic customers worldwide.
We are working with scrum & agile development methods.
Using Java, Spring, databases (Hana, SQL).
Responsibilities on CI, DevOps, quality and performance.
CI and DevOps using Jenkins, groovy, Git and monitor tools developed by the team.
Emphasize the design of the product and mission for high quality and structure.

DevOps and Automation Engineer

SAP
Dec 2017 - Sep 2018

Part of the product team. Working with product owners, program leaders, and development line managers. Drive and promote the quality of the project. Implement and maintain automation scripts and tests using Python and Java applications on virtual environments as a part of software development cycle.

Develop automatic applications for E2E tests using Jenkins and Grafana.
Creating dashboards for stability analytics using Python, Java, and JavaScript.

Combat & Intelligence Officer

Israeli Defense Forces (IDF)
July 2013 - Aug 2017 | 4 yrs

During the service, I served in special units of the Air Forces, Ground Forces, and Intelligence, roles of an officer. Intelligence includes analysis information mission. Establishing a team and team leading experience.

Web Developing

epsilontal
2004 - Present | 12 yrs

Developing websites, using - HTML5, CSS3, MySQL, PHP, JAVASCRIPT. Projects: shlifim.com, CVwave.com

whistle.live

Communication platform.
Backend: nodeJS; Frontend: Angular; Database: MongoDB.

CVwave.com

Personal website for your resume (CV)

Shlifim.com

Educational Social Network

Social educational network for students which allows students to share their knowledge, share files and communicate. A website for students who look for high-quality of school summaries. The site is a big reservoir of information for students.

Computer Science (JAVA)

The Open University of Israel
2015 - Present

Computer Programming (C#)

ORT Rabin, Gan Yavne
2010 - 2012

Instructor

Otzma
2010 - Present

Otzma is a government project of the ministry of education and ministry of defense which direct students while high-school to join the Israeli army for significant service, instilling values of leadership and love of the homeland. During the project, I instructed the students.

Karate blue belt

2010 - Present

Database performance

December 26th, 2018

Last engineering TAKT, I got a BLI that should support a new version of our product on the Cloud Platform. The feature was part of a backend service, API controller that represents Metering data (usage and billing) to our costumers on their Cockpit view of their account on our system. The API service built on SQL templates which involve logics on many tables using JOINs and conditions. We had a design and review at the beginning of the TAKT and decided, in order to avoid regression, to use a LEFT OUTER JOIN on the the current view using two conditions. LEFT OUTER JOIN SCHEMA.TABLE NAME ON (CONDITION_1 OR CONDITION_2) I was happy to finish the BLI and started the tests on it. The results seemed OK and we had no regressions at this part. But when I started the get deeper into the tests results, I found some regression on the performances. I received the result from the server after around 3secs. The change was from 200ms to 3secs which is a huge change. I started to investigate, being assisted by experts in my team and organization and we found some points: 1. Our new table that we used for the LEFT OUTER JOIN, set as a ROW store table which was not the best for that type of table. We change the table settings to COLUMN store which helps us with indexing. HANA-DB optimizes the indexes depend the store settings. 2. The main issue that caused the regression on the performances was the fact that I used two conditions for the ON of the LEFT OUTER JOIN. The OR condition of the JOIN turned to be a non effective because it creates cartesian product on the database on two big groups of data. Therefore, we decided to split the JOIN with the two conditions to two JOINs, each one with single condition. After that we have to add some logics to the select