Domain Specialist

Job Title Oracle Simphony Specialist POS Systems Architect Location UK Remote  Hybrid Grade FTE Primary Stack Oracle Simphony  Oracle Opera  REST APIs  Mews POS Preferred Role Overview As a Simphony Specialist  you will serve as the primary subject matter expert for our hospitality technology ecosystem This is a consultant first role where you will lead the design  planning  and implementation of Oracle Simphony across diverse global sites You will be responsible for defining configuration standards that ensure scalability while maintaining the flexibility required for individual properties Beyond simple setup  you will own the integration architecture  ensuring that Simphony communicates flawlessly with Oracle Opera PMS and other third-party platforms via advanced REST APIs Key Responsibilities 1 Technical Design and Implementation Solution Architecture: Lead the design and planning phases for Simphony rollouts  creating blueprints that account for menu hierarchies  revenue centers  and tax localizations Standardization Consulting: Advise customers on Enterprise Configuration best practices You will drive the move away from fragmented site-level setups toward a unified  standardized global template Hands-on Configuration: Expertly navigate the Enterprise Management Console EMC to build and maintain complex menu items  service charges  and discount structures 2 Integration and API Strategy Oracle Opera Synergy: Design and troubleshoot the Simphony-Opera Integration  ensuring seamless room charges  guest lookups  and financial posting between POS and PMS API Leadership: Leverage Simphony Transaction Services STS and BI APIs to connect the POS with third-party apps  kitchen display systems KDS  and mobile ordering platforms 3 Consulting  Project Leadership Site Readiness: Conduct discovery sessions to identify unique site requirements and document them in a formal Technical Design Document TDD UAT  Go-Live: Oversee User Acceptance Testing UAT and provide train-the-trainer support to ensure local teams are self-sufficient post-rollout