RTS Questionnaire · Question 20 of 52 · file: answers/q20.html
Have you developed an Angular application from scratch, starting from the initial architecture and project setup?
AngularArchitectureFrontend
✅ Yes — I have created Angular applications from an empty workspace, defining the architecture before the first feature was written.
Technical detail
- 🏗️ Project setup — Angular CLI workspace configuration, strict TypeScript/compiler options, ESLint + Prettier, path aliases, environment configuration per stage, SCSS theming pipeline, and CI build/test/lint jobs from day one.
- 🧭 Initial architecture — core/shared/feature structure, standalone components with lazy-loaded feature routes, HTTP interceptors for auth/error/telemetry, route guards and resolvers, typed API clients generated from the back-end contract, a design-system layer (Material/CDK + tokens) and a state strategy (signals or NgRx) chosen by complexity.
- 🔐 Cross-cutting foundations — authentication flow with JWT/OIDC, error boundary and notification strategy, i18n readiness, accessibility baseline, environment-based configuration and a documented folder/styling convention so the team scales consistently.
- 🧪 Quality gates — unit tests (Jasmine/Karma or Jest) with coverage thresholds, component tests, e2e smoke tests, and bundle budgets that fail the build when performance regresses.
📌 Delivering from scratch means the decisions are deliberate rather than inherited: I document them as ADRs and a short onboarding guide so new developers are productive in days, not weeks.
🧾 CV evidence: Current role (2024-present) delivers Angular 17/18 applications with architecture design responsibility; CV architectural competencies include 'POC development, Architectural Mechanisms, Performance Tuning'; SECOP public platform built from scratch as founder/lead (Angular + Node.js + ExpressJS).