Lead Solutions Architect
Summary
A hands-on Lead Solution Architect at Aculocity in Cape Town who turns the company's tech roadmap into governed solution and transition architectures spanning Microsoft platforms (Dynamics 365, Power Platform, Azure, Fabric), enterprise apps (CRM/ERP/PLM), integration, data, and AI/agentic solutions — with design authority from roadmap shaping through production readiness and legacy retirement.
Aculocity is modernising its application, data and integration landscape to support measurable business growth, lower operational friction, stronger resilience and an AI-ready enterprise. The environment spans Microsoft platforms, enterprise applications, custom-developed systems, manufacturing and engineering platforms, data and AI services, and specialist vendor solutions.
The Lead Solution Architect translates Aculocity’s strategic direction and technology roadmap into executable, governed solution and transition architectures. The role connects business outcomes, processes, applications, data, integration, AI, identity and operational controls, and remains engaged from portfolio shaping through production validation, value evidence and legacy retirement.
This is a hands-on architecture leadership role. It is not a documentation-only advisory position, a consulting-only role or a deep single-platform specialist role. The successful candidate must be technically credible, commercially pragmatic and able to make difficult trade-offs while helping teams deliver.
Key outcomes for the role
- Roadmap initiatives enter delivery with clear business outcomes, system boundaries, dependencies, architecture decisions, non-functional requirements and transition paths.
- Solution designs conform to agreed enterprise principles for reuse, interoperability, security, data ownership, observability, resilience and supportability.
- Reusable data, integration, identity and control capabilities are created through funded business releases instead of one-off point solutions.
- Architecture decisions are timely, traceable and explicit about options, rationale, risks, conditions, owners and review dates.
- Technical debt, coexistence and retirement work are visible, funded and managed as part of the business outcomes that depend on them.
- Vendor and partner designs remain aligned to Aculocity’s direction, with clear knowledge transfer and sustainable operational ownership.
Key responsibilities:
Portfolio and roadmap architecture
- Partner with business, portfolio, BTO and PMO stakeholders to translate outcomes, value streams and business processes into architecture options and executable roadmap increments.
- Provide architecture input before material delivery, budget and capacity commitments are made.
- Define current, target and transition architectures, including sequencing, dependencies, constraints, risks, run-cost implications, prerequisites and exit criteria.
- Contribute solution options and architecture readiness evidence for demand, project and quarterly funding gates.
- Maintain an architecture view across signature programmes, enterprise foundations, enhancements and lifecycle work.
Solution architecture and design authority
- Own solution-level architecture across CRM, ERP, PLM, service management, commerce, manufacturing, custom applications, data and integration services.
- Translate business and quality requirements into clear, pragmatic architectures and implementation decisions.
- Define and evolve architecture principles, reference patterns, standards and guardrails.
- Chair or lead architecture reviews within the approved governance model; approve, conditionally approve, reject or escalate designs within defined authority.
- Maintain architecture decision records and ensure material exceptions include risk ownership, compensating controls and review dates.
Application rationalisation and transition architecture
- Maintain solution and transition architecture across strategic, transitional and retirement systems.
- Define system-of-record boundaries, coexistence models, migration approaches, service-extraction patterns and controlled retirement paths.
- Identify duplicated capability, embedded business logic, point-to-point coupling, unsupported platforms and fragile specialist dependencies.
- Ensure new investments do not extend legacy dependency without an explicit, approved transition rationale.
- Work with application and platform owners to establish architecture debt, remediation actions and retirement evidence.
Integration, event and contract architecture
- Define API-first integration patterns, stable service contracts, ownership, versioning, schemas, authorization, error handling and operational expectations.
- Guide appropriate use of APIs, managed integration services, events, workflows, batch and change-data-capture patterns.
- Define event-driven and durable workflow-state patterns where real-time or long-running processes require them.
- Prevent unmanaged database access, shared credentials, brittle point-to-point integrations and ungoverned tool or MCP exposure.
- Promote discoverable, reusable integration capabilities across business domains.
Data, semantic and knowledge architecture
- Guide authoritative-source, master-data and data-ownership decisions with business and Data stakeholders.
- Ensure solutions define data flows, lineage, quality expectations, freshness, access boundaries and lifecycle requirements.
- Align application designs with governed data products, canonical entities, business glossaries, semantic models and knowledge sources.
- Ensure document retrieval and RAG patterns do not replace authoritative meanings, quality controls or system ownership.
- Clarify the boundary between operational data access, analytical consumption and governed write-back to systems of record.
AI and agentic solution architecture
- Provide architecture leadership for AI-enabled and agentic solutions without acting as the sole model-development specialist.
- Define agent boundaries, orchestration responsibilities, tool and API access, data context, memory, evaluation, observability and lifecycle controls.
- Classify autonomy according to business impact and reversibility, with proportionate human approval, exception handling and rollback controls.
- Ensure agents act through governed services and do not bypass application, data, identity, security or business controls.
- Promote reusable agent, evaluation and operational patterns rather than disconnected experiments.
Security, identity, resilience and operational architecture
- Embed identity, authorization, segregation of duties, privacy, security, compliance and auditability into solution design.
- Define non-functional requirements for availability, performance, recoverability, support, observability, scalability and cost.
- Ensure telemetry, support ownership, runbooks, disaster-recovery expectations, rollback and operational acceptance are addressed before production approval.
- Partner with Cybersecurity, Infrastructure, Data and operations stakeholders to resolve cross-cutting controls and dependencies.
- Consider licensing, cloud consumption, integration throughput and operating cost in architecture trade-offs.
Delivery enablement and lifecycle conformance
- Engage early and continuously with delivery teams to clarify architecture, remove blockers and guide implementation trade-offs.
- Work with engineering leads on environments, CI/CD, testing, deployment, release, rollback and architecture conformance.
- Review material design changes during build and ensure the delivered solution remains aligned to approved decisions.
- Validate production readiness and operational evidence, not only design documentation.
- Capture learning from delivery and operations to improve standards and patterns.
Vendor and partner alignment
- Act as the primary solution-architecture counterpart to implementation partners and specialist vendors.
- Set architecture boundaries, required evidence, review expectations and decision rights at the start of partner engagements.
- Challenge vendor designs constructively and protect Aculocity’s long-term supportability, portability and ownership.
- Require appropriate documentation, knowledge transfer, maintainability and operational handover.
- Support build, buy, partner and reuse decisions with clear architectural reasoning.
Architecture practice and knowledge
- Maintain a usable architecture repository containing context, container and integration views, decisions, standards, risks, transition states and lifecycle information.
- Develop lightweight templates and review paths proportionate to solution risk and complexity.
- Coach delivery teams and technical leaders in architecture practices and decision quality.
- Build communities of practice and reusable knowledge across Solutions, Data, Infrastructure and Security.
- Use architecture metrics and feedback to improve decision speed, reuse, conformance and delivery outcomes.
Decision authority and accountability
The role exercises architecture authority within the approved Aculocity governance model. Administrative reporting does not limit the enterprise scope of solution-design decisions. Authority limits, escalation routes and risk-acceptance rights must be defined in the role charter and architecture-governance RACI.
- Make and record solution architecture decisions within approved standards and delegated authority.
- Condition or stop progression where material architecture, security, resilience, data or supportability evidence is missing.
- Escalate decisions that require enterprise policy, material risk acceptance, funding, platform ownership or cross-company resolution.
- Remain accountable for architecture coherence and conformance while delivery and operational owners remain accountable for implementation and service outcomes.
- Ensure business owners retain accountability for business meaning, process decisions, value measures and acceptance of business outcomes.
Required experience and capabilities:
Core architecture experience
- Proven experience as a Lead Solution Architect, Principal Solution Architect or equivalent hands-on architecture leader in a complex enterprise environment.
- Experience designing solutions across multiple systems, vendors and technology domains rather than within a single product boundary.
- Demonstrated experience with enterprise application modernisation, integration, migration, coexistence and retirement.
- Experience operating as a design authority and making difficult, evidence-based trade-offs.
- Experience working with business sponsors, portfolio or programme stakeholders, delivery teams and implementation partners.
- Experience taking architecture from option and design through build, production readiness and operational learning.
Technical capability
- Strong grounding in application, integration, data and operational architecture.
- Practical architecture experience with several of the following: Dynamics 365, Power Platform, Azure integration and identity services, Microsoft Fabric and semantic models, Azure AI services, enterprise ERP or PLM, service management, commerce, manufacturing or custom-developed platforms.
- Working knowledge of API management, service contracts, event-driven architecture, managed integration, data ownership, MDM, lineage and observability.
- Ability to evaluate AI-enabled and agentic solutions, including tool access, data context, human oversight, evaluation and operational controls.
- Ability to reason about security, identity, resilience, performance, supportability, lifecycle and cost implications.
- Ability to read and challenge solution diagrams, interface specifications, data flows, deployment designs, code-level constraints and operational evidence.
Leadership and communication
- Clear, concise communicator who can explain architecture in business and technical language.
- Confident influencing senior stakeholders, delivery teams and vendors through evidence, pragmatism and credibility.
- Comfortable operating in a lean, high-ownership environment with incomplete information and competing priorities.
- Able to facilitate decisions, surface assumptions and create alignment without relying on hierarchy.
- Committed to coaching, knowledge transfer and growing architecture capability across teams.
- Outcome-oriented and willing to remain close to delivery and operations.
Preferred experience:
- Architecture experience in manufacturing, automotive, industrial, supply-chain or engineering environments.
- Experience with combinations of CRM, ERP, PLM, MES, service management, commerce and data platforms.
- Experience designing reusable enterprise APIs, events, domain services or data products.
- Experience with architecture review boards, architecture decision records and risk-based governance.
- Experience with cloud FinOps, observability, resilience engineering or production-readiness reviews.
- Relevant architecture, Microsoft, cloud, security or data certifications. Certifications are supportive evidence, not a substitute for practical architecture leadership.
Reasonable Accommodations (ADA Compliance)
Aculocity, a GVW Group company, complies with the Americans with Disabilities Act (ADA) and provides reasonable accommodations to qualified individuals with disabilities. If you need assistance or an accommodation, please contact Human Resources.
We are committed to Employment Equity, diversity, and inclusion, and encourage applications from all suitably qualified candidates.
Skills
Sign in to read and join the discussion.