Waseem PalliyaliR&D Product/Simulation Engineer

Product Engineering

Offline-first enterprise workflows and analytics.

Multi-tenant systems end-to-end: backend, frontend, data modeling, operational tooling.
Offline-first POS workflows used in daily operations
Accounting + inventory patterns designed for auditability
Cross-platform SDK delivery and rollout discipline
CI/CD and deployment workflows for production reliability
Email about roles
Resume → Simulation track

Capabilities

Systems Engineering

  • Multi-tenant architecture
  • Data integrity + audit trails
  • Performance + observability

Offline + Operational UX

  • Resilient flows (sync conflicts, retries)
  • Role-based workflows
  • Works when the internet doesn't

Analytics & Automation

  • Reporting pipelines
  • Data quality checks
  • Operational dashboards

Case Studies

Request walkthrough
Case Study 1

Thabooq — POS + Accounting (flagship)

Role: Role: product engineer (end-to-end architecture, delivery, and rollout).

Context: Multi-tenant POS + ERP serving retail transactions in production.

The Challenge

Problem: Problem: unreliable connectivity + audit requirements made legacy workflows brittle.

Constraints: Constraints: offline-first, auditability, multi-tenant isolation, low training overhead.

Impact & Results

"Impact: 1000+/day transactions, reduced reconciliation time, clean audit history per tenant."

Our Solution

  • Modeled workflows as state machines to make sync + retries predictable.
  • Data model with ledger-style accounting and invariants enforced at the DB + API layers.
  • Background sync with conflict resolution, metrics, and alerting.
  • Release playbooks for environment promotion, rollback, and migrations.

Artifacts

Artifacts: workflow/state charts, data model highlights, CI/CD pipelines, demo environment.

Engineering Principles

  • Start with data model and invariants (audit + correctness).
  • Design workflows as state machines (predictability).
  • Operational observability: logs/metrics, failure modes first.
  • Iterate with users: reduce friction, reduce errors.

Stack

Backend

  • Node/NestJS
  • PostgreSQL
  • Migrations + seed data

Frontend

  • React + offline-first patterns
  • Design systems tuned for operations

DevOps

  • CI/CD pipelines
  • Release playbooks
  • Environment promotion + rollback

Data

  • Reporting pipelines
  • BI tooling
  • Data quality checks