# Core member **CHAN WOEI LIH**\ **Position**: CEO\ **CHAN WOEI LIH** has over 15 years of experience in software engineering and blockchain development. A pioneer in decentralized systems, she leads the technical vision of NexaFusion, focusing on innovative AI and blockchain integration. **Daniel Rodriguez**\ **Position**: Chief Technology Officer (CTO)\ With a Ph.D. in Artificial Intelligence, Daniel specializes in machine learning algorithms and AI-driven decision-making systems. His expertise is instrumental in developing and optimizing AI models within the NexaFusion platform. **Megan Collins**\ **Position**: Lead Blockchain Architect\ Megan is an expert in blockchain infrastructure with over a decade of experience working on scalable, secure blockchain networks. She leads the development of NexaFusion’s decentralized applications and ensures seamless integration with AI technologies. **Liam Johnson**\ **Position**: Senior Full Stack Developer\ Liam is a seasoned developer with expertise in both front-end and back-end technologies. He plays a crucial role in building user-friendly interfaces and ensuring the smooth operation of the platform across various devices and networks. **Emily Carter**\ **Position**: Director of Product Management\ Emily brings extensive experience in product strategy and user experience design. She oversees the product development lifecycle at NexaFusion, ensuring that the platform meets the needs of developers, businesses, and end-users alike. These team members are prepared to contribute to projects leveraging their respective expertise in various Web3 development languages and technologies. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nexa-fusion.gitbook.io/nexafusion-whitepaper-v-1.0/team/core-member.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.