Techno Bot is a Discord bot focused on word and voice-based party games. It currently serves 40,000+ servers and 3 million players, giving communities a shared space for trivia, word ladders, and voice-activated challenges.

Why it matters

Starting the project at age 12 forced me to learn software engineering and community management in public. Scaling the bot taught me how to:

• Communicate roadmap changes to thousands of server owners.
• Plan monetization and premium features without breaking trust.
• Keep moderation, logging, and uptime stable while usage spikes.

Stack

• Languages & Frameworks: Node.js, TypeScript, Vue, Nuxt, NestJS, Express.js
• Data: MongoDB
• APIs: REST
• Infra: Docker Compose + PM2 for process management

Impact

• Built a multi-tenant, event-driven command system that handles millions of invocations per day.
• Shipped a live dashboard so server admins can customize commands and track engagement.
• Evolved the architecture from a single process bot to a containerized, horizontally scalable service.

Techno Bot remains my longest-running product and continues to be the playground where I experiment with new game mechanics, observability tooling, and developer experience workflows.

I worked as a full-stack developer in a fast-paced startup environment at Sellibra, turning Figma concepts into production features within days.

What I built

• Responsive control panels in Next.js + Tailwind that mirrored Figma specs and shipped within each sprint.
• Chrome Extensions hundreds of Amazon sellers rely on to analyze products and competitors directly inside Amazon.
• GraphQL + NestJS integrations so the extension and dashboard stayed in sync with Sellibra’s APIs.

How it helped

• Enabled product to iterate on seller insights without blocking on backend changes.
• Reduced maintenance overhead by refactoring legacy UI flows into composable components.
• Kept the team aligned through sprint rituals (planning, stand-ups, retros) across Jira, Confluence, and Slack.

This suite became the fastest feedback loop Sellibra had: ideas surfaced in design, prototypes landed in production extensions days later.