Arsal

OnlineNoida, India IST

Product Engineer at SquadStack.ai. I build voice AI across the stack, and I care about the people on the other end of the line.

LVL 3Next level Jan 2027

01 / Quests

What I work on

Mostly at SquadStack.ai, where I build voice AI end to end. Broad strokes here; ask me about the rest.

Voice AI

AI agents that hold real conversations, on the phone and on the web.

  • Agents that listen, reply and know when to stop talking
  • Voices that sound human, in more than one language
  • Tools to build, test and understand agents
  • Giving agents knowledge and memory

People usually reply within about a fifth of a second. An agent has to think inside that gap.

Backend systems

The parts nobody sees: services, data, and what happens when a lot of it arrives at once.

  • APIs and services
  • Data models, caching and background jobs
  • Real-time audio and events
  • Monitoring that spots trouble first

The best backend work is invisible. That’s rather the point.

Frontend systems

Interfaces that feel fast and obvious, on the web and on phones.

  • Web apps and dashboards
  • Mobile apps
  • Design systems and shared components
  • Turning slow screens into fast ones

Where I started, as an intern. I still notice every janky scroll.

Product design

Working out what to build, and for whom, before writing the code.

  • User research and testing
  • Flows, wireframes and prototypes
  • Design docs that settle debates early

I was a designer before I was an engineer. It never wore off.

02 / Skill tree

What I build with

The tools I work with, area by area. The filled ones are what I reach for every day.

Voice AI
  • LLM agents
  • WebRTC
Backend
  • Python
  • Django
  • REST APIs
  • PostgreSQL
  • Redis
Frontend
  • TypeScript
  • React
  • Next.js
  • React Native
  • Tailwind
  • Vite
Platform
  • AWS
  • Firebase
  • Sentry
Design
  • Figma
  • UX research
AI-native
  • Claude Code
  • Conductor
  • Wispr Flow

Daily driver Used it, liked itUnspent skill points: 0

Passive skill: Noticing the moment software feels slow, confusing or rude. Then fixing it.

Logos belong to their owners, and are here only to name the tools.

Continue?

I’m happy to talk about voice AI, interfaces, or any good design problem. Or coffee. Or who’d win, Batman or Spider-Man.