Current role · Jul 2025 – Present
- Where
- Examdee, AI VIETNAM RDS JSC
- Team
- 10–20 people
- Also
- Head of Product
- Stack
- NodeJS, ReactJS, Redis
01 · The job
I decide what gets built, and I answer for how it is built.
As Product Owner I own the vision, the roadmap and the backlog. As Tech Lead I own the architecture and the quality bar. The product serves teachers, students and guardians from one back-end, so every product decision I make lands on my own desk again as a technical one.
02 · The architecture I am responsible for
Teacher
ReactJS web
Student
gamified app
Guardian
mobile app
NodeJS API
JWT access token on every request
Redis
refresh tokens
Database
courses
Zoom
Meeting SDK
03 · What I did
Product and engineering, same person.
01
Product
Own the vision, roadmap and backlog. Write PRDs and user stories with business rules and acceptance criteria.
02
Architecture
Design the NodeJS back-end and ReactJS front-end, and make the key technical calls.
03
Delivery
Break epics into technical tasks, estimate, assign and unblock. Kanban for discovery, Scrum for delivery.
04
Quality
Review every pull request on Bitbucket for correctness, risk and maintainability. Work with the QA lead on coverage.
05
Security
Hardened authentication: JWT with a Redis-backed refresh-token flow.
06
Design
Design flows and screens with the design team on Figma / FigJam and maintain the design system.
04 · What I specified and led
Epics I wrote the PRD for and led to release.
- 01Course assignment
- 02Learning-material versioning
- 03Cross-organization content sharing
- 04Teacher self-study portal
- 05Gamified student course map
- 06Zoom Meeting SDK integration
- NodeJS
- ReactJS
- JWT
- Redis
- Jira
- Confluence
- Bitbucket
- Figma
05 · Decision log
Calls I made, and what they cost.
JWT access tokens + Redis-backed refresh tokens
Chose
Short-lived JWTs for requests, refresh tokens stored in Redis so a session can be revoked.
Gave up
Pure stateless auth. Every refresh now depends on Redis being up, and there is one more piece of infrastructure to run.
Kanban for discovery, Scrum for delivery
Chose
Ideas and specs flow on a Kanban board until they are ready; only ready work enters a sprint.
Gave up
One simple board. Two workflows mean more Jira upkeep and a handoff the team has to respect.
Review every pull request before merge
Chose
I read each PR on Bitbucket for correctness, risk and maintainability.
Gave up
Merge speed. I am a bottleneck by design, in exchange for one consistent quality bar.
Contact
Looking for a Tech Lead?
I want to own the technical direction and help a team ship products that matter.
huybn.dev97@gmail.com