RTS Questionnaire · Question 21 of 52 · file: answers/q21.html
Have you worked on complex Angular applications? If yes, approximately how many modules did the application have?
AngularArchitectureFrontend
✅ Yes — I have worked on large Angular applications in the 15-30 feature-module range, plus shared libraries consumed by several apps.
Technical detail
- 🗂️ Typical scale — enterprise platforms with roughly 15 to 25+ feature modules (dashboard/analytics, contract and entity search, reporting, administration, authentication/authorisation, notifications, file management, audit trail) on top of core/shared modules, each lazily loaded with its own routes, state slice and API services.
- 🧱 Complexity sources — hundreds of components, dozens of routes with nested child routers and guards, role-based visibility, heavy data grids with server-side pagination and virtual scrolling, charts, file upload/streaming, and i18n.
- 🧩 How I keep it manageable — clear domain boundaries, feature-sliced folders, shared component library with a stable public API, strict lint rules preventing cross-feature imports, typed API layer, and consistent state conventions (smart containers / dumb presentational components).
- ⚡ Large-app performance work — OnPush change detection,
trackBy/trackin loops, deferrable views, route preloading strategy, bundle analysis and budget enforcement, and profiling to eliminate unnecessary change-detection cycles.
🏢 Real examples from my career include public-sector contracting/analytics platforms and enterprise internal systems where the front end had to aggregate many data sources behind a single, coherent UI.
🧾 CV evidence: Founder/lead of the SECOP public contracting analytics platform (multiple analytical report modules, Angular + Node.js) and enterprise front-end roles delivering large modular Angular/React SPAs (2024-present, 2023-2024).