Moraru Ion

Within Chanel's Web Factory, I hold the position of React developer, integrating a team composed of 2 back-end developers and 2 front-end developers. My main role consists of managing the development and maintenance of existing projects as well as the design of new projects intended for internal use, primarily focused on back-offices.

The team works according to an agile methodology, organized into two-week sprints, punctuated by ceremonies led either by project managers or by the developers themselves, according to a rotation system for the Scrum Master role.

Main missions:

- Improvement of code quality

Implementation and configuration of standardization tools and best practices:

ESLint, Prettier, Husky, Commitlint.

Configuration of the environment for functional integration tests.

Introduction and adoption of TypeScript to strengthen code robustness.

Implementation of a modular front-end architecture

- Creation and maintenance of packages to organize and reuse functionalities:

Technical modules such as ts, vite, eslint.

Functional modules such as authent, storage, bricks, and Design System (storybook).

Design, development, and bug fixing

- Active participation in project design phases.

Development of new features and bug fixing in a proactive and collaborative approach.

- Technical documentation

Use of Docusaurus to create and maintain clear, structured, and accessible documentation for the team.

At PMU, I joined the 'Equipment' team as a front-end developer to participate in the creation of internal HMIs for monitoring and managing remote terminals and kiosks, as well as their configuration.

The team was also responsible for the communication part of the Electron/React application with the terminal.

Organized in agile mode with 2-week sprints and 3-month PI's, the team consisted of 2 Front-end devs, 2 Back-end devs, 3 SysOps, 1 QA, 1 PO, and 1 SM.

The main missions were:

- Implementation of the Micro Frontend architecture and development of HMIs from scratch (Vitejs, React, Typescript, React Query, ChakraUi…)

- Development of features on the Electron/React Desktop application for terminals and kiosks

- Implementation and maintenance of the GitlabCI pipeline

- Development of Storybook components

- Development of a shared module for common HMI logic and UI

- Implementation of the Sonar code quality tool

- Creation of documentation

- Implementation of end-to-end tests with Playwright and Cucumberjs

- Incident tracking and production deployment of the deliverable.

- Maintenance of code quality through Code Reviews, Sonar analysis, pair programming

- Communication with other teams for the development of cross-functional features.

- Organization and facilitation of technical discussions on common HMI topics.

At FnacDarty, I had the opportunity to work in the checkout tunnel team, whose main focus is managing the shopping cart (cart summary, delivery, payment, etc.). The team was organized in agile mode with a 2-week sprint and 6-sprint Program Increments (SAFe) and consisted of 3 Front-end Devs, 6 Back-end Devs, 1 QA, 1 PO, and 1 Business Analyst.

My main missions:

- Creation, automation, and optimization of the GitlabCI pipeline (GitlabCI, Proget, TFS, Sonar)

- Bug fixing.

- Progressive code refactoring.

- Improvement of the front-end application architecture (Redux Toolkit, Typescript, Domain-driven architecture, creation of custom hooks, creation of HOCs, lazy-loading, improvement of the data model)

- Creation of the FNAC Design System

- Creation of shared modules (fnac-config, fnac-helpers)

- Deployment of a static site on Microsoft Azure

- Creation, facilitation, and participation in the React Community of Practice

- Continuous improvement of organizational processes (agile rituals, branch management, documentation)

- Development of new features

- Facilitation of agile rituals (retrospective, daily)

- Incident tracking and production deployment of the deliverable.

- Maintenance of code quality through Code Reviews, Sonar analysis, pair programming

- Communication with other teams for the development of cross-functional features.