Direct technical integration support across critical payment flows.
Software/Product Engineer • Payments • Reliability
I turn complex customer problems into production systems.
I work with banks, fintechs, card issuers, payment gateways, and internal teams to solve integration and operational problems across payment, authentication, and high-throughput backend platforms.
A redesigned Kafka-based bulk token-enrolment workflow.
Investigation, architecture, stakeholder alignment, and delivery.
Architecture shaped by customer impact and production constraints.
From customer problem to production outcome
My work combines customer-facing technical discovery, backend engineering, and delivery. I translate integration and operational problems into technical decisions, align the people involved, and implement systems that hold up under real production pressure.
Selected work
A few examples of systems, constraints, and outcomes from my work.
SafeToken Project
Interswitch authentication service for issuing, delivering, and validating OTPs across payment and identity-verification flows.
Bulk Token Enrollment
Resolved stuck uploads and redesigned the workflow to process 10,000 token records in under one minute.
LLM Failure Analysis
Studied reasoning failure patterns in AI systems, with emphasis on robustness and systematic error propagation.
Agentic engineering workflow
I use coding agents to shorten feedback loops across discovery, implementation, testing, review, and documentation. The agent accelerates the work; I remain accountable for the technical decisions and production outcome.
Frame the outcome
Start with the user problem, success criteria, constraints, and risks.
Provide context
Ground the agent in the codebase, architecture, conventions, and operating environment.
Delegate focused work
Use bounded tasks for investigation, implementation, testing, and documentation.
Review the reasoning
Inspect assumptions, trade-offs, code changes, security, and failure behavior.
Verify independently
Run relevant checks and confirm the system behaves correctly before shipping.
Tech stack
Languages
JavaSQL
Frameworks
Spring BootSpringSpring MVCHibernate
Messaging
Apache KafkaRabbitMQgRPCREST
Databases
MySQLMSSQLMongoDBPostgreSQLRedis
Cloud & Storage
AWSAzureAWS S3AWS Redshift
DevOps & CI/CD
DockerKubernetesJenkinsBitbucketSpinnaker
Security
Spring SecurityOAuth2JWTEncryption
Big Data
Apache SparkApache HadoopApache HueAirflow
AI & Agentic
CodexAI-Assisted DevelopmentAgentic WorkflowsContext EngineeringPrompt EngineeringLLM EvaluationVector Databases
Testing
JUnitPostmanSwagger
Architecture
MicroservicesEvent-Driven
Side projects
Things I build outside of work.
Thoughts
A few ideas that shape how I think about growth, responsibility, and the pressure that comes with real work.
Thought 01
Figuring life out often looks like ownership
Sometimes the shift is simple: a deployment is running, and you stay awake because the outcome now belongs to you too.
Thought 02
AI assistance raises the bar for engineering judgment
Faster code generation makes context, verification, security, and ownership more important — not less.
Thought 03
Speaking up is usually less costly than silence
Growth often comes from saying the necessary thing, learning that the world does not end, and adjusting if needed.
Have a complex customer or systems problem?
I work with teams that need customer-facing technical judgment, strong backend engineering, and delivery that holds up in production.
Start a Conversation