# Vinh Vu - CTO & Co-founder

<div align="left"><figure><img src="/files/w69dIFcpfB73dJsBSxqc" alt="" width="125"><figcaption><p>Vinh Vu</p></figcaption></figure></div>

Meet Vinh Vu, the <mark style="color:purple;">Chief Technology Officer</mark> and co-founder of Fizen.io. Vinh has over 12 years of extensive experience in the field of information technology development.&#x20;

He has made significant contributions and possesses in-depth knowledge in various key areas, including:

✔️Database ✔️ Backend ✔️ Mobile applications&#x20;

✔️ blockchain ✔️ Artificial Intelligence - AI&#x20;

✔️ System architecture  ✔️ Cloud services

Before joining Fizen.io, Vinh Vu worked at FPT Software, one of the largest software development companies in Vietnam and the region. At FPT, he held the position of Head of the Blockchain Department and gained over 4 years of experience collaborating with Leo on various blockchain projects.

Vinh Vu's expertise and experience as a seasoned professional in the technology field have played a pivotal role in the rapid growth of Fizen. In just one year, Fizen has created a [diverse product ecosystem](/docs/general-introduction-to-fizen/fizens-story/fizen-ecosystem.md), focusing on application and security to meet the needs of users and partners. Additionally, Vinh Vu has maintained a [high-quality technical team](/docs/teams/building-the-project/teams/technical-team.md), which has been with Fizen since its early days.


---

# 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://fizenio.gitbook.io/docs/teams/building-the-project/board-of-director/vinh-vu-cto-and-co-founder.md?ask=<question>
```

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.
