Contact tracing is an example of a semantic network.Advocating for the responsible and ethical use of artificial intelligence [AI]. Experienced performing requirements analysis and leading development efforts leveraging conversational AI [chatbots] and AI marketing decisioning technologies. With a background in liberal arts and databases, knowledge engineering and representation using graph databases and/or semantic networks is my forte rather than machine learning [ML]; from a natural language processing [NLP] perspective, ML provides predictive analysis and semantic networks or graph databases provide meaning and context for natural language understanding, or NLU. For chatbot technology, I’ve been exposed to IBM Watson. For marketing decisioning technology, I’ve been exposed to Pega Next Best Action. For semantic networks, I’ve been exposed to Neo4j graph database and a plethora of SQL databases. For content delivery, I’ve been exposed to GraphQL micro services used for graph and/or SQL database API querying. For graph database sourcing, I’ve been exposed to near real time [NRT] Hadoop kafka feeds and SQL queries, for SQL database sourcing I’ve been exposed to Informatica ETL.Systems Engineer [SE] duties have included performing the Product Owner role at the development team level and Product Manager role at the project level for the Agile Scrum development methodology and producing ROM [Rough Order of Magnitude] estimates for the SDLC [Software Development Lifecycle] methodology.In the Agile Product Owner role, worked at the development team level and was responsible for authoring the technical development team user stories, maintaining the team user story backlog, and attending all team scrum ceremonies; technical requirements at the team level are defined by User Acceptance Criteria. In the Agile Product Manager role, worked at the project level and was responsible for authoring epic/feature stories, or the high level minimum marketable product requirements [MMPs] that formed the umbrella over the supporting development team user stories. The Acceptance Criteria at this level are in the language of the business where the technical implementation details are hidden (unless required by bounds scoping). As a Product Manager, facilitated weekly PO Sync meetings to coordinate the activities and dependencies of the participating project development teams and performed PI planning.