Now · Engineering journey

Building at the edge of AI‑native product engineering.

The newest work comes first. Enterprise experience and earlier foundations provide the context beneath it.

NOWProduct architectureAgentic workflowsProduction systemsMarch 2026 — Present
01 / CurrentMarch 2026 — Present

Independent Product Engineering

Products are where the ideas become real systems.

The focus shifted towards understanding how modern AI systems can become useful, deployable software products.

Product architecture, LLMs, agentic workflows, orchestration and production engineering now move as one discipline.

02 / AI-native systemsActive exploration

Research in practice

A connected field of engineering questions.

The work connects intelligence, orchestration and production discipline—not as trends, but as parts of one product system.

03 / EnterpriseOctober 2021 — March 2026

Enterprise Engineering

Barclays

Explore chapter

Large-scale systems shaped by resilient integration, identity journeys, event-driven processing and customer interaction platforms.

Select a project to inspect the engineering record.
03.1Mastercard VocalinkEvent processing / Fraud workflowsProject detail

Problem

Fraud-detection events need dependable processing even when downstream work fails or must be retried.

Architecture

Event-driven integration using Apache Kafka, explicit retry handling and Dead Letter Queue paths.

Interesting engineering

Worked extensively on resilient event processing, retry mechanisms and failure isolation within Mastercard Vocalink integrations.

Lessons

Failure paths, replay behaviour and operational visibility are part of the workflow—not secondary infrastructure concerns.

Future documentation

Verified sequence diagrams and deeper implementation context will be added as documentation is completed.

Technologies

  • Java
  • Spring Boot
  • Kafka
  • Event Driven Architecture
  • Dead Letter Queue

Interview topics

  • Kafka delivery semantics
  • Idempotency
  • Retry strategy
  • DLQ operations
  • Failure recovery
03.2Identification & VerificationIdentity / Multi-channel journeysProject detail

Problem

Authentication and verification journeys must remain coherent across multiple enterprise channels.

Architecture

Enterprise identity and verification capabilities exposed through secured service and API boundaries.

Interesting engineering

Worked on systems supporting authentication and login journeys across multiple channels.

Lessons

Identity workflows require explicit trust boundaries, predictable responses and careful treatment of failure states.

Future documentation

Channel-specific flows and verified architecture detail will be added when documentation is ready.

Technologies

  • Identity
  • Authentication
  • Enterprise APIs
  • Security

Interview topics

  • Authentication flows
  • API security
  • Channel consistency
  • Trust boundaries
03.3Amazon ConnectVoice systems / AIProject detail

Status / Exact service implementation name pending confirmation.

Problem

Customer interaction through voice systems requires reliable routing and recognition within a controlled service journey.

Architecture

An Amazon Connect based customer-interaction and voice-recognition system.

Interesting engineering

Worked on the system while the exact internal service terminology remains pending confirmation.

Lessons

Voice interfaces need observable transitions and clear fallback behaviour because the interface itself is transient.

Future documentation

Project terminology will be expanded as documentation is completed.

Technologies

  • Amazon Connect
  • Voice Systems
  • AI

Interview topics

  • Voice workflows
  • Interaction routing
  • Recognition boundaries
  • Fallback design
03.4BIDVPlatform record / Documentation in progressProject detail

Problem

Verified problem context is still being documented.

Architecture

Architecture detail is intentionally withheld until it can be documented accurately.

Interesting engineering

Documentation in progress.

Lessons

No claims are published before the supporting project context is verified.

Future documentation

This record is structured for future problem, architecture and engineering detail.

Technologies

Documentation in progress.

Interview topics

  • To be documented
04 / Earlier contextBefore October 2021

Foundations

Learning how production software holds together.

The focus was on software engineering fundamentals, backend development, Java, enterprise development practices and understanding production software.

The work continues

Strong fundamentals.
AI-native workflows.

Looking for opportunities to build modern software products with teams that care about how systems behave in the real world.

Available within 15 days