Product Manager - Semantics Adoption & Knowledge Modeling

About Nagarro

Nagarro is a rapidly expanding global digital product engineering firm delivering innovative products, services, and experiences at scale. Our presence spans over 18,000 professionals across 39 countries. We foster a dynamic, flat organizational culture encouraging growth and collaboration. We seek motivated individuals ready to contribute beyond skills and coding — to guide teams strategically and continuously improve our solutions.

Role Purpose

The primary objective is to facilitate seamless acceptance and integration of the semantic abstraction layer within the EcoStruxure Platform teams and Lines of Business (LoBs) by building solid domain knowledge. This role demands expertise in ontology modeling and the ability to bridge semantic technologies with operational team realities unfamiliar with ontology-based methodologies.

Key Responsibilities

• Empower EcoStruxure platform architects and engineers through training on semantic modeling basics such as OWL, RDF/S standards, graph databases, ontology design patterns, and common errors.
• Guide the engineering team in effective ontology management service implementation aligning technical choices with business goals.
• Define and establish semantic standards including naming conventions, annotation rules, foundational ontology alignment, and shared vocabularies, collaborating closely with other Schneider teams.
• Collaborate hands-on with LoB subject matter experts and data modelers to co-create their initial canonical domain models, facilitating structured sessions for domain knowledge transfer and formal semantic modeling.
• Progressively build autonomy within LoBs by initially guiding, then coaching, and finally enabling them to operate independently.
• Develop reusable resources such as modeling guidelines, real-world domain examples, and decision-making frameworks addressing common modeling queries.
• Evangelize the tangible business benefits of the semantic layer to stakeholder groups emphasizing findability, interoperability, intellectual property protection, and cost savings.
• Present clear outcomes showing how a well-designed canonical model accelerates application development, clarifies data product definitions, and improves inter-LoB understanding.
• Address skepticism by openly recognizing overheads of semantics while justifying returns on investments.
• Serve as an expert reviewer during platform releases ensuring model structural quality, pattern compliance, and interoperability preparedness.
• Define benchmark standards for canonical models with explicit examples and identify modeling anti-patterns early to prevent adoption across LoBs.

Qualifications and Experience

• Proven practical experience in ontology development in industrial or enterprise scenarios beyond academic use.
• Expertise in semantic web technologies including OWL, RDF/S, SKOS, and SPARQL as an active practitioner.
• Experience working with open-standard graph databases encompassing configuration, data loading, querying, and performance tuning.
• Strong aptitude for translating complex domain knowledge into formal semantic models collaboratively with experts.
• Track record of successfully introducing semantic technologies to novice teams with demonstrated adoption.

Skills and Competencies

• Ability to articulate semantic modeling concepts in accessible language tailored for non-technical audiences.
• Competence in extracting coherent domain models by engaging various stakeholders such as control engineers, grid specialists, and building managers.
• Comfortable working in uncertain environments with new technology requiring patience, pragmatism, and clarity.
• Strong advocacy for modeling quality balanced with flexibility considering practical constraints.
• Exceptional written communication skills capable of producing clear, practical guidance documentation.
• Effective verbal communication skills, straightforwardness, and ease operating within multicultural contexts.

Additional Information

• This position is distinct from software engineering roles – it focuses on adoption facilitation rather than coding or platform infrastructure construction.
• The Product Manager does not hold governance responsibility; policy ownership lies separately while this role ensures proper implementation.
• The role is transitional to enable self-sufficiency of teams within 12–18 months, moving from active contribution to advisory support.