> For the complete documentation index, see [llms.txt](https://docs.epiora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epiora.xyz/team.md). # Team #### Felicia Farris / CTO Felicia Farris serves as Chief Technology Officer at Epiora, bringing over 8 years of backend engineering experience across AI infrastructure, cloud systems, enterprise software, and scalable API development. Before joining Epiora, Felicia worked as a Backend Engineer focused on AI Systems at Cohere, where she integrated AI services into client-facing platforms and developed internal tooling for monitoring and improving large-scale inference workloads. Prior to Cohere, she worked as a Backend Engineer at Cisco, building microservices for networking and security products using Java and Python and contributing to authentication and authorization systems for enterprise applications. Earlier in her career, Felicia developed APIs connecting AI models with customer-facing dashboards, improved deployment workflows through Docker-based containerization, and worked extensively with SQL, backend automation, testing, and production infrastructure. She holds a Bachelor of Science in Computer Engineering from The University of Texas at Austin. At Epiora, Felicia leads the technical architecture, infrastructure, and backend engineering strategy, with a focus on building scalable, reliable, and AI-native systems. Linkedin: #### Ethan Walker / Protocol & Blockchain Lead Ethan Walker leads Protocol and Blockchain Engineering at Epiora, with around 4 years of experience working on blockchain applications and backend systems. Before joining Epiora, Ethan worked as a Blockchain Engineer at an early-stage Web3 startup, where he contributed to smart contract integrations, wallet connectivity, and transaction monitoring across EVM-compatible networks. Earlier in his career, he worked as a software engineer building backend services and APIs. His technical background includes Solidity, TypeScript, EVM networks, wallet integrations, smart contracts, and DeFi protocols. Ethan holds a Bachelor of Science in Computer Science from Arizona State University. At Epiora, Ethan works on protocol integrations, wallet infrastructure, onchain execution, and the systems connecting the platform with decentralized markets. #### Julian Park / Product Engineering Lead Julian Park leads Product Engineering at Epiora, bringing around 4 years of experience building web applications, dashboards, and data-driven interfaces. Before joining Epiora, Julian worked as a Frontend Engineer at a fintech startup, where he developed dashboards, portfolio interfaces, and real-time data components. Earlier in his career, he worked as a full-stack developer at a small software company. His technical background includes TypeScript, React, Next.js, WebSockets, APIs, financial charting, and frontend performance optimization. Julian holds a Bachelor of Science in Computer Science from California State University, Fullerton. At Epiora, Julian is responsible for the trading interface, market dashboards, portfolio experience, frontend architecture, and client-side integrations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.epiora.xyz/team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.