Job Description & How to Apply Below
Translator and architect between customer tech teams and Beroe.
What this role exists to do
Owns the technical relationship with each MAX customer once they sign. Bridges the customer's IT, data, and procurement-systems teams with Beroe's engineering, data, and analyst teams. Runs the technical onboarding — understands the customer's tech stack, shapes how MAX connects into it using the platform's pre-built connectors and tooling, and shapes the high-level configuration choices that make MAX work for that customer's category mix and procurement maturity.
The role is built to be repeatable — onboarding many customers off a standard playbook and product tooling, however each customer will have their own nuances related to data that needs to be accommodated during data ingestion process to ensure all (or most) of MAX's features could be effectively enabled.
What they actually do
Technical discovery. Run technical onboarding workshops. Map the customer's ERP, CLM, spend analytics, supplier master, contract repository, and data warehouse. Understand their data quality and master-data fragmentation Highlight the impact on product features basis data (and quality thereof) received from the customer
Configuration choices. Make the high-level configuration choices for the customer — which external and internal signal sources are switched on, alignment to customer taxonomy, etc.
Integration design decisions. Shape the integration approach jointly with the customer's IT team — APIs vs SFTP, batch vs real-time, which pre-built connectors to switch on. Translate the decisions into a clear specification that the will guide the data ops team to setup MAX for success.
Direct and challenge engineering. Scripting and data transformations are built by the Beroe Data Engineering Team. The Solutions Architect specifies what's needed, reviews what's delivered, and is technically credible enough to challenge engineering on scope, effort, and timelines rather than accepting estimates at face value.
Put product tooling to work. Run onboarding through MAX's product capabilities — pre-built connectors, the mapping workbench, and migration and validation tools — for a first few customers though it will have to be done manually. Where a need recurs across customers, route it back to product as a feature request instead of solving it by hand each time.
Own data readiness. Be accountable for getting ingested data complete, correctly mapped, and clean enough for MAX's LLM and insight layer to reason over before anything surfaces to the customer. Direct the data analysts who do the mapping, classification, deduplication, and validation, and sign off on the result.
Customer technical contact. Be the named technical escalation point for the customer during onboarding and build. Resolve issues without pulling Beroe Engineering into customer calls wherever possible.
UAT and enablement. Walk the customer's CM/CPO team through MAX as Evaluators come live. Train customer-side champions. Walk them through all the test scripts during UAT. Hand off to customer success into go-live.
Steady-state ownership. After go-live, run quarterly technical reviews with the customer's tech leadership.
Feedback loop into product. Feed customer learning back into MAX's roadmap. Distinguish between pattern-level needs (become product features) and customer-specific quirks (stay in configuration).
Scale and team leadership. Standardize onboarding into a repeatable playbook so the model scales to dozens or hundreds of customers, not a handful of bespoke builds. As customer count grows, build and lead a small team of onboarding architects — shifting from running onboarding personally to running the function, and flagging recurring manual work so it can be productized and the team kept lean.
What they don't do
They don't write production code (engineering does).
They don't hand-build connectors, data pipelines, transformations, or migration scripts — those are productized engineering capabilities, not per-customer manual work (product and engineering own them).
They don't run the product roadmap (product management does).
They don't drive…
Note that applications are not being accepted from your jurisdiction for this job currently via this jobsite. Candidate preferences are the decision of the Employer or Recruiting Agent, and are controlled by them alone.
To Search, View & Apply for jobs on this site that accept applications from your location or country, tap here to make a Search:
To Search, View & Apply for jobs on this site that accept applications from your location or country, tap here to make a Search:
Search for further Jobs Here:
×