Experience

Baazargaan

Co-founder · Product & Technical

A digital B2B product in development where I work across product, technology, and delivery. My role spans problem definition and product decisions through technical coordination, quality assurance, documentation, and release readiness.

My role

My role connects product questions with the team’s technical work and delivery. I clarify problems, turn decisions into actionable requirements, and follow implementation and quality with the specialists doing the work. Progress comes through shared decisions and coordinated contributions across the team.

What I do

Product decisions

I make open-ended product questions easier for the team to discuss, decide, and implement.

  • Turn early needs and ideas into product requirements, scenarios, and actionable decisions.
  • Define and review product requirement documents and product rules.
  • Break broad problems into smaller decisions and scopes.
  • Prioritize features and make trade-offs visible.
  • Coordinate roadmaps, backlogs, and dependencies.
  • Define acceptance criteria and a clear definition of done.
  • Review delivered work against product decisions.
  • Keep current decisions as the shared source of truth across documentation.

Technical coordination

I work at the boundary between product and development, with hands-on frontend work and close coordination with technical specialists.

  • Contribute hands-on to frontend work and UI iterations.
  • Review interactions and user flows.
  • Coordinate frontend and backend work with the development team.
  • Review API and integration behavior against product expectations.
  • Trace issues across the UI, backend, and data layers.
  • Join debugging and investigate issues exposed during integration or QA.
  • Review deployment and release state with the team.
  • Translate technical constraints into clear product decisions.

Delivery, quality, and documentation

I help keep decisions, implementation feedback, and release preparation connected throughout delivery.

  • Break decisions into tasks and map dependencies.
  • Check implementation against acceptance criteria and definition of done.
  • Contribute to QA checklists and follow-up iterations.
  • Document product and technical issues so the team can resolve them together.
  • Prepare release-readiness notes and keep project context up to date.

Working across the team

My work at Baazargaan is cross-functional and collaborative. I bring product decisions, technical constraints, implementation feedback, and delivery needs into the same conversation, then keep open questions moving among the people closest to them. Each area is built with the relevant specialists on the team.

  • Backend development
  • UI and interface work
  • Product stakeholders
  • Marketing and branding contributors
  • Business stakeholders

From idea to delivery

My role can span several stages: clarify the problem, turn it into actionable work with the team, and follow the result through quality review and release preparation.

  1. 01 Problem or idea
  2. 02 Research and clarification
  3. 03 Product decision
  4. 04 Requirements, rules, and scenarios
  5. 05 Task and dependency breakdown
  6. 06 Design and technical coordination
  7. 07 Team implementation
  8. 08 QA and iteration
  9. 09 Release readiness and review
  10. 10 Documentation and next decisions

Tools I work with

Product and documentation

  • Notion

    Product decisions, tasks, documentation, and project context.

  • Figma

    Interface reviews, flow walkthroughs, and design-development communication.

Development and delivery

  • GitHub

    Code, change history, and technical coordination.

  • Vercel

    Deployment and release verification.

  • Codex

    A supporting tool for code exploration and development work.

Artifacts I produce

Product

  • Product requirement documents
  • Product rules
  • User and system scenarios
  • Decision logs
  • Roadmaps
  • Prioritized backlogs
  • Acceptance criteria

Delivery

  • Task breakdowns
  • Dependency maps
  • QA checklists
  • Release-readiness notes
  • Technical and product issue documentation

Collaboration

  • UI review notes
  • Implementation feedback
  • Cross-functional decisions
  • Project documentation

How I work

Clarity before execution

Before work starts, I help clarify the problem, who needs to decide, and what done means.

Trade-offs over perfect answers

I consider time, team capacity, and dependencies when evaluating product and technical choices.

Documentation as infrastructure

Important decisions and context belong in documentation the team can return to.

Team over individual heroics

I aim to build shared context and coordination that help the team work with greater independence.

Selected outcomes

  • Helped turn an early idea into a more structured product that the team can implement.
  • Established clearer ways to document product decisions.
  • Connected product needs with technical constraints and the team’s implementation work.
  • Contributed to multiple UI and frontend iterations.
  • Joined QA to identify mismatches between product decisions and implementation.
  • Helped structure workflows for tasks, decisions, documentation, and release readiness.
  • Moved project context from informal conversations into a shared source of truth.