Job Title: Operations ArchitectReports To: Chief Technology Officer (CTO)Position SummaryThe Operations Architect is a high-impact role designed to apply the principles of Industrial Engineering—optimization, systems thinking, and process improvement—to the broader business and technology landscape. Operating under the CTO, you will lead the charge in identifying organizational bottlenecks, architecting business intelligence solutions, and driving large-scale transformational projects. You will act as the bridge between technical infrastructure and operational excellence, ensuring that our growth is supported by efficient, data-validated processes.Key Responsibilities1. Process Engineering & Optimization

• Conduct end-to-end "Current State" audits of business workflows.
• Apply Continuous Improvement Methodologies to eliminate organizational waste and improve throughput.
• Design and implement "Future State" processes that leverage automation and modern software tools.

2. Business Intelligence & Data Strategy

• Collaborate with various teams to develop and own Key Performance Indicators (KPIs) and operational dashboards.
• Translate raw operational data into actionable insights for the operations, finance and executive teams.
• Ensure data integrity across business systems (ERP, CRM, VMS, etc) to create a "single source of truth" for decision-making.

3. Strategic Transformation Projects

• Lead cross-functional projects directed by the CTO, such as BI implementation, AI-integration initiatives, or other digital transformations.
• Manage the Change Management process, ensuring that new technologies are adopted smoothly by non-technical staff.
• Evaluate and recommend new technologies that align with the company's long-term technical and/or operational roadmaps.
• Interact with executives across the CEO, COO, and CFO organizations as well as business units across the White Cloud Keiretsu organization, including but not limited to consumer, healthcare, supply chain, media, hospitality, and entertainment related businesses.

4. Organizational Architecture

• Map the intersection of human workflows and software systems to ensure technology is an accelerator, not a barrier.
• Standardize Operating Procedures (SOPs) for a digital-first environment.

Demonstrated Impact & Expertise

• Education: Educational background in a field that emphasizes systems thinking (Engineering, CS, Math, Economics) OR equivalent practical experience building complex operational systems.
• Experience: Proven track record of building, scaling, or transforming operations in fast-paced, high-growth, environments. We value a history of 'intrapreneurship'—taking ownership of a problem and building a solution from the ground up.
• Technical Proficiency:
  • Advanced knowledge of Data Visualization tools (Power BI, Tableau, Looker, etc).
  • Familiarity with SQL and data modeling.
  • Experience with ERP/MRP systems and Business Process Mapping software (LucidChart, Visio).
• Methodologies: While we appreciate the principles of Lean or Six Sigma, we value your ability to deliver results using whatever tools and creative approaches are necessary for the situation.
• Soft Skills: Exceptional ability to communicate complex technical concepts to non-technical stakeholders; strong "influencing without authority" skills.
• First-Principles Thinking: You aren't tied to "how it's always been done." You can deconstruct a process to its core components and rebuild it for maximum efficiency.
• Comfort with Ambiguity: You thrive when there is no playbook and are excited by the challenge of defining your own roadmap.

How This Role Differs from a Standard IE

• Scope: While a standard IE focuses on a specific plant or production line, this role looks at the entire business lifecycle.
• Command: Reporting to the CTO means the focus shifts from "labor hours" to "digital efficiency" and "scalable technology."
• Output: The primary output isn't just a physical layout or a shift schedule, but a digital ecosystem where data flows seamlessly between departments.