前端架构师 20k-35k

Role Summary
Lead the front end architecture for a large scale enterprise platform, enabling Micro Frontend solutions with Angular, Module Federation, and Routing Slip patterns. Define standards for Clean Architecture, cloud native delivery, and performance/security best practices.

Key Responsibilities
61 Design and maintain an Angular based MFE host and remotes using Webpack Module Federation.
61 Implement the Routing Slip pattern for dynamic, multi step workflows across MFEs.
61 Collaborate on cloud native, microservice backends and ensure seamless integration with the front end.
61 Drive an Event Driven Architecture (EDA) across client 62 services, integrating message queues/streams (MQTT, Kafka, RabbitMQ).
61 Enforce Clean Architecture, modular boundaries, and contract *** integration between MFEs and services.
61 Lead performance optimization, Core Web Vitals compliance, and observability (real user metrics, tracing, dashboards).
61 Ensure security (CSP, DOM sanitization, OAuth2/OIDC) and accessibility (WCAG 2.2).
61 Standardize CI/CD pipelines, shared libraries, and progressive delivery (feature flags, canary/blue green).

Required Technical Skills
61 Architecture Communication & Diagramming: Ability to create and present architecture diagrams (including UML, sequence diagrams, component diagrams) to collaborate with US system architects and guide ***** teams on execution.
61 Angular (expert): Angular 16+, RxJS, SSR/CSR strategies, rendering performance (Signals/OnPush).
61 Micro Frontends: Webpack 5 Module Federation, shared dependency governance, version orchestration.
61 Routing Slip pattern: Dynamic route orchestration for multi step flows across MFEs.
61 Frontend SDK/Library Development: Proven experience designing and publishing reusable SDKs or UI libraries for enterprise-scale applications.
61 Low-Code Development: Ability to design and integrate low-code solutions or frameworks for rapid feature delivery.
61 Clean Architecture: Layered design, dependency rules, anti corruption boundaries for legacy integration.
61 Cloud Native & Microservices: Containers (Docker), Kubernetes (Helm/Ingress), service discovery, config/secret management, autoscaling; IaC (Terraform/ARM/CDK) preferred.
61 Event Driven Architecture: MQTT, Apache Kafka, RabbitMQ; pub/sub patterns, outbox and idempotency strategies, schema governance (e.g., Schema Registry), and eventual consistency (sagas).
61 Performance & Security: Core Web Vitals (LCP/INP/CLS) targets, bundle budgets, CSP, OAuth2/OIDC, DOMPurify/trusted types.
61 Observability: OpenTelemetry for client, distributed tracing, RUM dashboards, SLOs/error budgets.
61 Tooling: Nx monorepos, Webpack 5, Storybook, CI/CD (Azure DevOps/GitHub Actions), artifact/version strategies.
61 Web Components: Interop via Lit/Stencil and design token theming across MFEs.
61 Progressive delivery: Feature flags, canary/blue green releases with automated rollback criteria.