Preparation for a Solutions Architect interview at A. O. Smith requires a strategic mindset. You are not just proving your technical depth; you must demonstrate how you apply that depth to solve enterprise-level business problems in a manufacturing context.

Your interviewers will evaluate you against several core criteria:

• Domain-Specific Architecture – You will be assessed on your deep expertise in the specific track you are applying for, whether that is SAP Production Planning (PP) or OneStream Financial Systems. Interviewers want to see how you design, configure, and integrate these platforms within a broader enterprise ecosystem.
• Business Acumen & Process Mapping – Technical skills alone are not enough. You must show how you translate complex manufacturing workflows or financial reporting requirements into scalable technical solutions.
• Cross-Functional Leadership – You will be evaluated on your ability to influence stakeholders without direct authority. Interviewers look for candidates who can confidently guide business leaders through technical trade-offs and drive consensus.
• Problem-Solving at Scale – You must demonstrate how you approach system limitations, integration bottlenecks, and legacy technical debt, ensuring that your proposed architectures are both resilient and future-proof.

The interview process for a Solutions Architect at A. O. Smith is designed to thoroughly vet both your technical architecture capabilities and your alignment with the company's collaborative, operationally focused culture. The process typically kicks off with a recruiter screen to ensure baseline alignment on experience, location expectations (often Nashville, TN), and domain expertise.

Following the initial screen, you will engage in a deep-dive interview with the hiring manager. This conversation focuses heavily on your past project experiences, your approach to enterprise architecture, and your familiarity with manufacturing or financial systems. Expect probing questions about projects that failed or faced significant roadblocks, and how you navigated those challenges.

The core of the evaluation takes place during the technical and architectural panel rounds. You will face scenario-based questions where you must design solutions for specific business problems, such as integrating a newly acquired plant into the central SAP instance or standardizing financial reporting across global units using OneStream. The final stage usually involves a behavioral and leadership fit round with senior IT and business stakeholders.

This visual timeline outlines the typical progression from initial screening to the final leadership panel. Use this to pace your preparation, focusing first on your high-level narrative and past experiences before diving deep into technical whiteboarding and scenario-based architecture practice for the panel rounds. Keep in mind that depending on the specific business unit, you may face additional specialized technical assessments.

To succeed, you must demonstrate mastery across several key architectural and behavioral domains. Interviewers will probe your depth using real-world scenarios relevant to A. O. Smith's operations.

Enterprise ERP & Financial Systems Architecture

As a global manufacturer, A. O. Smith relies heavily on robust ERP and financial consolidation systems. You must prove your ability to architect solutions within these massive platforms.

• Platform Configuration & Customization – Understanding when to use out-of-the-box functionality versus when to build custom enhancements.
• System Integration – Designing seamless data flows between SAP, OneStream, legacy on-premise systems, and third-party cloud applications.
• Data Architecture & Master Data Management – Ensuring data integrity across supply chain and financial systems, which is critical for accurate reporting and production planning.
• Advanced concepts (less common) – Cloud-native ERP migrations, IoT integration from the factory floor to SAP, and advanced predictive analytics for supply chain forecasting.

Example questions or scenarios:

• "Walk us through how you would architect the integration of a newly acquired manufacturing facility running a legacy ERP into our central SAP PP environment."
• "How do you ensure data consistency when mapping complex financial hierarchies from multiple regional ERPs into OneStream?"
• "Describe a time you had to push back on a business request to heavily customize an ERP module. How did you handle it?"

Business Process Mapping & Solution Design

A great architect understands the business as well as the technology. You will be tested on your ability to bridge the gap between operational needs and technical execution.

• Requirements Gathering – Eliciting clear, actionable requirements from non-technical stakeholders like plant managers or financial controllers.
• Gap Analysis – Identifying discrepancies between current business processes and standard system capabilities.
• Solution Documentation – Creating clear, comprehensive architectural blueprints that developers and integration teams can easily follow.

Example questions or scenarios:

• "How do you approach mapping out a current-state manufacturing process before designing the future-state architecture?"
• "Tell me about a time when the business requirements constantly shifted during the design phase. How did you adapt your architecture?"
• "Walk me through your process for translating a complex regulatory compliance requirement into a technical system design."

Cross-Functional Leadership & Stakeholder Management

You will rarely build in isolation. Your ability to guide teams, manage expectations, and communicate trade-offs is heavily scrutinized.

• Influencing Without Authority – Gaining buy-in from diverse teams, including IT infrastructure, security, and business units.
• Communicating Trade-Offs – Explaining technical debt, cost, and timeline implications to executive leadership in plain language.
• Vendor Management – Working with external consultants, software vendors, and implementation partners to ensure architectural standards are met.

Example questions or scenarios:

• "Describe a situation where the engineering team and the business unit fundamentally disagreed on a solution. How did you mediate and drive a decision?"
• "How do you present a highly technical architectural change to a non-technical executive board?"
• "Tell me about a project where you had to rely on an external vendor to deliver a critical component of your architecture. How did you ensure quality and alignment?"