Solutions Architect

Solutions Architect

About the Role

As a Solutions Architect, you own the solution from the first technical conversation to the signed Statement of Work. You work with CTOs, CIOs, CDOs, and business leaders at large enterprises to understand how their data and operations actually work, design how Arkham fits into them, and prove it with a Proof of Concept built on their real data.

You sit between three teams: the Growth team, which owns the relationship and the commercial opportunity; the Forward Deployed Engineering (FDE) team, which deploys what you design; and Product and Engineering, which build the platform. Growth builds commercial trust. You build technical trust.

This is a pre-sales role with real architecture ownership. The solution you design is the one our FDE pods take to production, so it has to hold up beyond the demo, and you hand it over with scope, architecture, and expectations already clear.

What You’ll Work On

• Lead technical discovery with customer teams to map their data sources, systems, infrastructure, and existing architecture
• Design solution architectures for Arkham deployments: ingestion and integration, ontology and data model, forecasting and AI components, and fit with the customer’s cloud and security requirements
• Design and build Proofs of Concept on real customer data, end to end, and present the results to engineering teams and C-level executives
• Translate business problems in forecasting, inventory, demand planning, pricing, and supply chain into concrete Data & AI solutions with measurable outcomes
• Quantify the business case for each solution: KPIs, operational improvements, and ROI
• Define scope, integration requirements, and technical Statements of Work, and hand off to the FDE team with the architecture and expectations clear
• Answer technical RFPs and customer questions on cloud infrastructure, security, data governance, and platform capabilities
• Partner with Growth Managers on enterprise opportunities, from technical objections to architecture reviews with customer IT teams
• Bring customer feedback and market insight back to Product and Engineering to shape what the platform builds next

What You Bring

• Background in Computer Science, Data Science, Engineering, or a related technical field
• Experience as a Solutions Architect, Solutions Engineer, data consultant, or in another customer-facing technical role, ideally with enterprise customers
• Strong SQL and Python, and the ability to explore, model, and make sense of real-world transactional data
• Hands-on experience with modern data platforms and architectures: lakehouse and medallion patterns, Databricks, Snowflake, or BigQuery, Spark or dbt, data pipelines, and APIs
• Cloud infrastructure experience, preferably AWS, including the security and governance questions enterprise IT teams ask
• Experience building with LLMs (agents, RAG, evals, or similar) and daily use of AI tools to move faster
• Practical understanding of forecasting, inventory management, demand planning, or supply chain operations
• A track record of demos, prototypes, or Proofs of Concept that moved a deal forward
• Ability to explain complex technical concepts as business value to executive stakeholders, and to navigate ambiguous requirements
• Professional fluency in Spanish and English
• Based in Mexico City, with availability to travel to customer sites

Nice to Have

• Machine Learning experience, especially time-series forecasting
• Experience with enterprise customers in Retail, CPG, or Supply Chain
• Experience with enterprise planning platforms such as SAP IBP, Blue Yonder, o9, or RELEX
• Experience in a field engineering or solutions role at a data or AI platform company

Why This Role Is Different

At most companies, a Solutions Architect designs a solution and never sees it again. At Arkham, the architecture you design on real customer data is the one that goes to production for some of the largest enterprises in the region, and you see the impact.

You’ll work directly with decision-makers, own the technical journey from discovery to signed SOW, and have a direct line to Product and Engineering to shape what the platform does next. You see the problem first, design the answer, and watch it ship.