Software Architect

Position: Software Architect

Role Summary

The Software Architect is the senior technical authority for the entire platform - approximately 40 repositories spanning 16+ Python (Flask) microservices on Amazon EKS, a Java 21 / Spring Boot platform on ECS, seven React web applications, native Android and Flutter mobile components, and a Salesforce org. This role defines the target state, governs API contracts, and leads consolidation of legacy systems while keeping delivery moving.

Key Responsibilities

• Produce and maintain architecture decision records (ADRs), a full service dependency map, and current/target state architecture diagrams none exist in the repositories today.
• Own API governance: enforce OpenAPI-first design across the Flask services and the Spring Boot digital-platform (frontends generate typed clients from OpenAPI specs).
• Define and drive the retirement path for legacy systems.
• Standardize the microservice template loosely shared by all the Flask services (structure, config, auth, logging, testing, deployment).
• Own data architecture across MySQL (legacy) and PostgreSQL, and govern schema change through the central Alembic migrations repository.
• Own the security architecture: JWT auth flows, secrets handling, WAF posture, and the platform dependency-upgrade policy.
• Decide and rationalize the EKS-vs-ECS split (Python services on EKS; Java platform on ECS) and the long-term platform strategy.
• Review all cross-service API changes; mentor the team and set engineering standards (code review, CODEOWNERS, testing bar).

Required Qualifications

• 10+ years in software engineering, 3+ years in an architect role for a distributed / microservices platform.
• Working fluency in both Python (Flask/FastAPI, SQLAlchemy) and Java (Spring Boot, Maven) — must be able to read and review both halves of this codebase.
• Deep AWS experience: EKS/Kubernetes, ECS, CloudFront, S3, IAM, WAF, CodeBuild.
• Strong API design record (REST, OpenAPI/Swagger, API gateways, versioning strategies).
• Relational data modeling at scale (MySQL and PostgreSQL) and migration governance (Alembic or equivalent).
• Demonstrated legacy-modernization leadership: framework upgrades, service consolidation, strangler patterns.
• Application security fundamentals: OAuth2/JWT, secrets management, OWASP, dependency/CVE management.