What HCMC Developers Are Actually Building Right Now

A field report on the tools, communities, AI workflows, and product experiments shaping Saigon's technical scene.

Ho Chi Minh City has no shortage of startup events, pitch nights, networking mixers, and founder conversations. But if you want to understand what is actually happening in the local technology scene, the useful signal is often somewhere quieter.

It is in the developer testing AI agents against a real workflow. It is in the data person trying to connect enterprise data to useful internal tools. It is in the product engineer moving from "shipping tickets" to asking whether the thing being shipped solves a real problem.

It is also in the small technical meetup where someone shows what worked, what broke, and what they would not do again.

This article is a field report, not a complete map of the ecosystem. It is based on public community signals, conversations around The Sandbox, and the patterns we are seeing across HCMC's developer and builder community.

The goal is simple: make more of the city's technical work visible, so the community can learn faster.

AI is becoming a developer workflow, not just a topic

The obvious trend is AI. The more useful trend is how developers are using it.

The local conversation is moving beyond "AI is changing everything" and toward more specific engineering questions:

• How do AI coding agents fit into a real software delivery process?
• Where does AI help with testing, documentation, refactoring, and migration work?
• What happens when an AI prototype needs governance, data quality, access control, and maintenance?
• How do teams use AI without losing engineering judgment?

This is visible in the public event layer. TECH Meetup HCMC describes itself as a community for software engineering, data, and AI. Its June 2026 event includes sessions on scaling E2E tests, upgrading React 19 with an AI agent, and the data realities behind AI projects.

AI Tinkerers Ho Chi Minh City is even more explicit: coding agents, orchestrators, automation workflows, conversational AI, and autonomous agents.

That matters because these are not abstract conference themes. They are workflow questions. They sit inside the daily work of engineers: testing, shipping, debugging, documenting, reviewing, migrating, and operating systems.

The technical conversation is becoming less about whether AI is impressive and more about where it survives contact with real software work.

Developers are moving closer to product

Another pattern is the shift from developer as implementer to developer as product-aware builder.

That does not mean every developer needs to become a founder. It means more technical people are getting closer to the full loop:

• What problem are we solving?
• Who feels the pain?
• What is the smallest useful version?
• How do we know if it worked?
• What can we learn before writing more code?

This shift shows up in the kinds of communities forming around HCMC. The GenAI Builders Meetup was designed around founders, software engineers, AI practitioners, product leads, and enterprise teams. Its format included people sharing what they were building, the challenges they were facing, and the support they needed.

That format is important. It moves the conversation away from job titles and toward evidence.

What are you building? What is blocked? What did users or stakeholders teach you? What support would move the work forward?

That is the builder loop. Not just code. Not just ideas. Actual feedback.

This connects directly to why The Sandbox was started in Saigon: not to create another generic networking room, but to create a better environment for useful technical and product conversations.

Communities are becoming technical infrastructure

Good communities are not just social spaces. For developers, they function like infrastructure.

They help people find:

• better questions
• sharper feedback
• collaborators
• hiring signal
• local context
• technical references
• examples of what is actually being tried

This is one reason generic networking often feels weak. A room full of job titles does not help much if nobody gets to the actual work.

The better version is smaller and more specific. A developer explains a migration. A data person describes why an AI project failed because the data layer was not ready. A product engineer shares where a no-code prototype stopped being enough. Someone else says, "We hit the same problem."

That is technical infrastructure. It compresses learning.

The local ecosystem already has several layers of this. Women Techmakers HCMC has been building community around women and people in technology since 2022, with highlights across Build with AI, DevFest, Google I/O Extended HCMC, career development, and developer events. GDG HCMC adds another Google developer community layer, with public activity around Build with AI, developer community, and agent-related topics.

There is also a hands-on builder like Build Stuffs, which lists HCMC events such as Weekend Build with Codex and CAR (Codex Auto Runner), plus co-working for tech and growth builders. Product & Beyond adds a complementary product-community layer, bringing together people across design, engineering, product management, marketing, operations, legal, and other functions involved in building products.

The opportunity for HCMC is not just more events. It is better memory from those events.

What did people build? What did they learn? What tools did they stop trusting? What patterns repeated across conversations?

That is the kind of community knowledge worth writing down.

No-code and low-code are moving into serious workflows

No-code used to be easy to dismiss as a prototype layer.

That is becoming less accurate.

The more interesting pattern is the overlap between no-code, automation, AI agents, and enterprise data. The HCMC AI + NoCode Meetup, hosted by HCMC Data Meetup, focused on AI integrations with no-code tools, live demos, AI agents on enterprise data warehouses, architecture decisions, tooling trade-offs, and governance challenges.

That mix is worth paying attention to.

The question is not "Will no-code replace developers?"

The better question is: where does the fast prototype end, and where does engineering responsibility begin?

For HCMC builders, this creates a practical middle ground:

• use no-code or low-code to test workflows faster
• use automation tools to connect operational systems
• use AI to reduce repetitive work
• bring software engineering discipline when the workflow becomes important

The interesting builders are not religious about tools. They are asking which tool gets the right version of the problem into the world fastest, without creating future operational debt.

Remote work is part of the technical stack

For developers working from HCMC, the stack is not only language, framework, database, and deployment platform.

It is also:

• backup internet
• quiet call spots
• async documentation
• time-zone discipline
• security habits
• payment workflows
• written decision records
• places where deep work is actually possible

This is especially true for developers working with global teams or international clients. A good remote setup is not a lifestyle preference. It is production support for your own work.

If your internet dies before a client call, your stack failed.

If decisions live only in a chat thread nobody can find, your operating system failed.

If your work is solid but nobody understands the tradeoff you made, your communication layer failed.

That is why HCMC developer content should not only review cafes or coworking spaces. It should evaluate the actual work infrastructure behind technical output. The existing deep-work cafe guide is a starting point. The next version should look harder at what developers actually need: stable WiFi, quiet calls, outlets, ergonomics, and focus.

HCMC needs more visible builder memory

The HCMC tech community does not need more vague claims that the ecosystem is growing. It needs better shared memory.

Not only:

"There is a meetup."

But:

"Here is what people are building."

"Here are the technical problems that keep showing up."

"Here are the tools developers are testing."

"Here are the questions worth discussing next."

Across public events and community conversations, these are the categories worth tracking:

• AI coding agents and workflow automation
• internal tools for operations, HR, finance, and sales
• data dashboards and AI-on-data-warehouse experiments
• no-code and low-code prototypes moving into real software
• developer productivity tools and agent orchestration
• startup MVPs from solo developers and small teams
• remote-work infrastructure and async technical workflows
• community-led learning through Build with AI, AI Tinkerers, TECH Meetup, GDG, Women Techmakers, Build Stuffs, Product & Beyond, and similar groups

This list is not complete. That is the point.

The next version should include more direct input from developers in the city.

What are you building in HCMC right now?

If you are building something technical in HCMC or Vietnam, we want to hear about it.

You do not need to be venture-backed. You do not need a launch announcement. You do not need a polished founder story.

Useful signals are enough:

• What problem are you solving?
• What stack or tools are you using?
• What surprised you technically?
• What did you try that did not work?
• What kind of collaborator, feedback, or user would help?

The goal is not to turn every project into promotion.

The goal is to make the technical work happening around the city easier to see, easier to learn from, and easier to connect around.

Because the most interesting tech signal in HCMC is not always on stage.

Often, it is already being built quietly.