Depth when you need it. Outcomes before technology lists.

Context

The product needed to translate changing vehicle data and real route constraints into a dependable operations experience.

My contribution

• Built route and trip logic for one-way and round-trip operational scenarios.
• Connected Google Maps, SSE, Redis, and AWS Lambda for movement and alert updates.
• Delivered features across the Node.js backend, React interface, MySQL, and Prisma data layer.

Context

Customers needed an agent that could fit their existing websites and business systems instead of becoming another isolated tool.

My contribution

• Built embeddable widgets, agent setup flows, training sources, and connected automations.
• Supported React, Next.js, Vue, Angular, and vanilla integration paths.
• Published @irisidea/kalrav-ai to make repeat adoption faster and more consistent.

Context

The challenge was to make identity, document access, collaboration, and AI responses feel like one product rather than separate utilities.

My contribution

• Owned frontend architecture and connected workflow behavior across the product.
• Integrated Microsoft Entra ID, OneDrive, and Microsoft Graph API flows.
• Built SSE-based response loops for a more responsive AI experience.

Context

The platform needed dependable authentication, content workflows, and reporting tools across web and companion mobile experiences.

My contribution

• Implemented Firebase authentication, MFA, and JWT-based API access across the platform.
• Built Node.js, Express.js, GraphQL, and Strapi services for education workflows.
• Delivered teacher dashboard features, scheduled PDF reports, React interfaces, and Flutter companion app work.

Context

The work centered on turning product requirements into usable interfaces while keeping access control and third-party integrations consistent.

My contribution

• Built responsive product interfaces with reusable component structure and consistent design patterns.
• Layered OAuth and JWT authentication into connected API workflows.
• Improved cross-device reliability through access-control checks and consistency testing.

Context

The product needed reusable UI modules and practical debugging support while feature requirements evolved with product and QA feedback.

My contribution

• Built reusable React components adopted across multiple team modules.
• Implemented REST-connected collaboration features for Agile workflow use cases.
• Supported system-level debugging and manual QA alongside feature delivery.

Context

Chat alone was too limiting for workflows that needed forms, tables, confirmation cards, and safe writes to connected systems.

My contribution

• Streamed AG-UI components with server-held state for responsive agent workflows.
• Generated task-specific forms, tables, and confirmation cards from live context.
• Added human-in-the-loop approval before writes reached connected systems.