From November 2023 to July 2025, I worked as a Front-End Developer at MOJ SECURE (SaaS), where I collaborated with two cross-functional teams on several large-scale projects. One of my key contributions was to the Iranian Customs Administration (IRICA) system, where I improved the React codebase by restructuring routing, organizing API calls, and integrating TypeScript ā reducing errors by 40% and accelerating development of new components and pages.
During my time at MOJ SECURE, I also had the opportunity to lead an improvement initiative for the SIGMA project, a ReactJS-based platform that had grown increasingly complex. The project contained multiple instances of duplicated components, which made maintenance more difficult and introduced risks of inconsistency.
To address these challenges, I designed a three-step improvement plan with a focus on refactoring duplicated parts of the system into single, reusable modules ā all while ensuring performance remained a top priority.
šÆ Key Focus Areas
The improvement plan concentrated on three interconnected sections of the codebase:
- API Calls Module ā Unify API integrations through a single module for consistency and easier maintenance.
- Routes Handling Hook ā Standardize route handling so reusable components could reliably determine which procedure was active.
- Screen Components ā Consolidate duplicated screen components into modular, reusable ones to reduce redundancy and improve scalability.
Other parts of the project, such as atomic and composite components, assets, Redux, styles, and types, were set aside for separate review cycles.
š Available Reports
I documented this initiative in a series of reports. You can access each one here:
1. Main Proposal Report
This document introduces the duplication problem in the SIGMA project and proposes a structured refactoring approach, outlining why API calls, route handling, and screen components needed to be addressed together.
2. Step 1 ā Unified API Module
In this phase, all API calls were consolidated into a single module. This reduced redundancy, improved reliability, and ensured every component integrated APIs consistently.
3. Step 2 ā Standardized Route Handling
Here, I created a unified hook to manage routes. This allowed reusable components to detect active procedures consistently and eliminated discrepancies across different parts of the codebase.
4. Step 3 ā Reusable Screen Components
The final phase involved consolidating duplicated screen components into single, reusable ones. While the planning was completed and the approach documented, implementation was pending at the conclusion of my role.
š” Takeaway
Through this structured refactoring effort, the SIGMA project became significantly cleaner and more maintainable. By reducing duplication and standardizing core areas like API integration and routing, we improved reliability, simplified development, and built a stronger foundation for future growth.
This work marked the conclusion of my contribution to the SIGMA project at MOJ SECURE, and Iām proud to have delivered improvements that increased application stability by 60% and left the team with a more scalable codebase for the future.