Enterprise Platform Architect

The Enterprise Platform Architect with JM Family Enterprises is a senior technical and strategic leader. They provide advice and influence the development of enterprise platform capabilities. Their work ensures that solutions are secure, scalable, and reusable across the organization.

The role works closely with platform teams, Business Enablement, and architecture governance bodies. It helps to shape platform standards and reference architecture. The focus is on providing guidance and recommendations. There is no direct ownership or enforcement involved.

The Enterprise Platform Architect works closely with the Business Enablement and Platform teams. This includes Sec Tech Ops  and OCTO/Dev Sec Ops . They make sure that platform services comply with enterprise architecture principles. They also ensure services align with the cloud strategy and support long-term business goals. The role balances near‑term delivery enablement with long‑term platform sustainability and modernization.

This position operates in a hybrid work model based in Deerfield Beach, FL (3 days per week onsite).

Key Responsibilities:

Platform Architecture & Standards
- * Advise on and influence the development of enterprise platform architectures. This includes creating reusable patterns. It also involves developing reference architectures and setting technical standards. Collaborate with platform teams and architecture governance bodies.

* Provide guidance on using shared platforms and services. These services include cloud, integration, identity, Dev Sec Ops , data, and middleware. Assist teams in aligning with enterprise principles. They should also be able to keep their delivery autonomy.

* Work closely with the Business Enablement, Information Security, and Platform teams. Make sure platform designs meet security standards. Ensure they are resilient, scalable, and operationally effective.

* Translate enterprise architecture principles into useful guidance. This involves creating platform blueprints, decision trees, deployment patterns, and reference examples. Teams can use these consistently.

* Influence and promote the adoption of reusable platform patterns, golden paths, and reference implementations that accelerate delivery and reduce cognitive load for development teams.

* Support platform teams in evolving standards and patterns by providing enterprise context, cross‑domain insights, and impact analysis, rather than direct ownership or enforcement.

Strategic Advisory & Enablement
- * Serve as a senior platform architecture advisor to Business Enablement and Platforms, guiding design decisions, trade‑offs, and roadmap alignment.

* Support the solution and delivery teams. Explain the platform's capabilities and limitations. Discuss integration methods. Provide direction for architectural decisions on complex initiatives. These initiatives involve shared platforms and enterprise services. They cross multiple domains.

* Provide architectural direction for complex projects. These projects use shared platforms and enterprise services. They span across different domains.

* Influence platform adoption and standardization through collaboration rather than mandate.

Governance & Architecture Review
- * Document decisions about platform architecture. Ensure they are traceable and meet enterprise security standards.

Technical Debt & Maturity Management
- * Lead the strategy to reduce technical debt from outdated and unnecessary technologies. This involves identifying issues. Then, prioritize them and create solutions to fix them.

* Develop and maintain platform maturity models, assessment frameworks, and tracking mechanisms.

* Create dashboards and metrics to provide visibility into platform health, adoption, and risk.

* Partner with engineering and operations teams to embed technical debt considerations into planning and delivery cycles.

Lifecycle & Roadmap Management
- * Lead practices for managing the platform's lifecycle. This includes forecasting technology needs. It also involves assessing supportability and planning for when the platform reaches end-of-life.

* Ensure architecture repositories and inventories reflect current and future‑state…