Ghita Tazi

Work on many technical and functional topics in the context of applications developed in the field of food tech Examples for the technical part: implementation of the NextJS router app for a progressive transition from pages/ to app/; import of data from a legacy SaaS to our Postgres database following a user-centric approach working in close collaboration with the business team Participation in frontend and backend guilds We use the Shape Up methodology

Part of the core team and then within the B2B tribe, my role is to bring my technical expertise for the development of a Front End application and GraphQL BFF, in order to provide the CSE customers with a beautiful and powerful multi-tenant back-office. Special focus is put on code quality and good development and delivery practices

I worked for Dior for 3 years, on the e-commerce Website. It is a luxury company that has very high expectations in terms of user experience, and quality of delivery, with tight deadlines. It was a very challenging environment to evolve in. My experience could be divided into two main periods. During the first year, I worked as a senior developer for Dior Parfums, on two main subjects: a from-scratch customer account; and some features on the checkout (ex: offer a selection of free samples and miniatures to a buying customer, display delivery methods according to the customer location) After that, we offered me the opportunity to become a lead developer in a brand new team, to develop the new customer account for Dior Couture, on a dedicated React application. I was on the project from the beginning, I built the application, macro estimated the first features with the business, designed the technical solutions with the architects and helped the developers deliver quality code in time. We delivered in production after one year of hard work; and I continued working on the project for a year after that, adding new business features More generally, all the Front End developers were part of a big team, with a high technical level. We were splitted into dedicated feature teams and one core team that had the responsability to make our developing experience better and to work on the performance of the Website We worked in agile mode (SCRUM, Kanban and PI plannings) Our technical stack was the following: React, TypeScript, Next, Apollo GraphQL, Sass, Storybook We also had to work on making the website accessible

Wynd is a growing-fast startup, specialized in software solutions for retail companies. It is divided into two departments : Project and Product. The Product department is in charge of developing the core of the product (data modeling, database storage, API), and all the features that use that core (mobile applications, back-office, cash-registers, e-commerce websites). The Project department relies on the work of the Product department but adds new custom features to fit the customers specific needs. I worked within the Product department, in the back office team. What makes this back office specific is that it has been conceived to be generic. Within the team, we used some best practices of SCRUM (the well-known Agile method) as a conductive thread. We used merge requests on Gitlab as a pre-push method to insure that the code was clean and ready to be integrated into the project We used modern and well-tested JavaScript technologies such as ReactJS, ES6, TypeScript, MobX. We tested all our additional features using Jest and Enzyme and conducted functional tests via Cypress. As for the visual part of the interface, we worked with a UX/UI design team via InVision models. Keywords : JavaScript, ES6, ReactJS, JSX, TypeScript, MobX, Jest, Enzyme, Cypress, CSS3, Webpack, StyleLint, CSSLint, Prettier, InVision, Gitlab, Gitlab CI, Yarn, Nvm, SCRUM

Startup that sells a hardware and software solution to monitor energy in different environments using a network of sensors. The sensors transmit their data to a gateway that is then in charge of parsing, processing and logging it into a database. From an end-user point of view, the main role of the gateway is to offer, locally, a Web interface to visualize raw data and data after processing. My work was to develop all the gateway features to make it evolve with client expectations. It mostly focused on the Web interface (back-end and front-end) to make sure we offer to the client the best user experience in terms of graphics and ergonomics. In addition to that, I worked on the Python processing part when receiving frames from the sensors (we considered different transmission protocols such as USB and wireless protocols). When needed, considering the small size of the company, I could also help with other subjects such as the Linux part. As the gateway is an embedded system, we also had to deal with more low-level problems (such as memory and backlogs management). Keywords : Python, Flask Framework, Jinja2, JavaScript, jQuery, HTML5, CSS3, D3.js, Bootstrap, Require.js, InfluxDB, SQLite, Nginx, Gitlab, Raspberry Pi, Linux

Integrated within the team Java Integration at Open Wide, my internship aimed at putting me in concrete situation of IT projects in production. My missions were to study recent technologies such as the Spring Batch Framework, to take on client projects and their specifications, and to put into practice my knowledge during the development phase. From a technical point of view, the projects focused on the integration and the enrichment of Java solutions. They mainly treated the problem of the Electronic Management of Documents and were based on professional solutions of the market such as Alfresco or Nuxeo. They also brought in Open Source technologies such as Spring MVC and Spring Batch Frameworks. Keywords : Java, Spring MVC Framework, Spring Batch Framework