Lentra · Career Experience

A professional journey in product engineering

Hello, HR Team Welcome to my journey.

Explore my growth at Lentra, the challenges I've worked through, and the engineering contributions that have shaped my professional journey.

Lentra career presentation Crafted by Samarth Kolge
Samarth Kolge CAREER STORY / LENTRA
Portfolio
CAREER JOURNEY / 2025—2026

From business analysis to product engineering.

My journey at Lentra has taken me from understanding business requirements and digital lending workflows to building, improving, and supporting complex product journeys. I bring together analytical thinking, hands-on development, problem-solving, and a strong sense of ownership to help turn business needs into working product experiences.

Pune, India Lentra Product Engineering
Explore My Work View Career Timeline

Focused on delivery, collaboration, and continuous improvement.

2025 Started at Lentra
2026 Rapid Progression into Product Engineering
E2E Journey development and delivery
THE EVOLUTION

A journey of growing ownership.

Every new responsibility has been an opportunity to understand the product more deeply, solve more complex problems, and take greater ownership of the outcome.

JUN 2025 Started at Lentra

Tech Business Analyst Trainee

Lentra · Business Analysis

I started by learning how business requirements translate into digital lending workflows. My focus was understanding product behaviour, working with form configurations, and helping deliver business requirements through the platform.

  • Worked with lending journeys covering multiple business products and customer onboarding scenarios.
  • Contributed to widget-level responsibilities involving Demographics, Sourcing, Lead, and RM Recommendation.
  • Developed an understanding of requirements analysis, field validations, business rules, form behaviour, and workflow dependencies.
  • Collaborated with cross-functional stakeholders to understand functional expectations and resolve implementation issues.
Foundation built: Understanding the business problem before implementing the technical solution.
2025–2026 Broader product exposure

From requirements to implementation

Product workflows · Quality · Delivery

As my product understanding grew, I increasingly connected business expectations with the implementation details needed to make a journey reliable, usable, and ready for production.

  • Contributed to platform and Design Studio work, including reviews of lending journeys before production deployment.
  • Investigated functional and UI issues, implemented fixes, and helped improve journey behaviour.
  • Identified and tracked high-risk issues that could affect production readiness, helping the team prioritize resolution.
  • Worked with teammates to validate changes, understand edge cases, and improve implementation quality.
Key development: Moving beyond understanding what a feature should do to examining how reliably it works in practice.
01 JUL 2026 Role progression

Associate Product Engineer

Lentra · Product Engineering

On 1 July 2026, I transitioned into an Associate Product Engineer role. My work expanded toward implementation, backend development responsibilities, journey-level problem-solving, and delivery ownership.

  • Took on development responsibilities across multiple digital banking journeys and product workstreams.
  • Worked on enhancements, defect resolution, workflow behaviour, and complex implementation requirements.
  • Collaborated with engineering leads and teammates to address escalations and improve the reliability of product journeys.
  • Began taking greater responsibility for translating requirements into working implementations and supporting the resulting delivery.
Role progression: Bringing business context and technical execution together to deliver complete product functionality.
2026 Expanded responsibilities

End-to-End Journey Ownership

Development · Integrations · Delivery

With broader engineering exposure, I took responsibility for complete journey components and received lead-developer responsibilities for selected workstreams. The focus shifted from isolated tasks to understanding how individual components work together.

  • Worked across multi-step banking journeys involving sourcing, KYC, demographics, API status, and supporting data components.
  • Investigated complex interactions between lending systems, connectors, downstream services, and document-management data.
  • Gathered and clarified requirements, optimized existing functionality, supported demonstrations, and addressed implementation issues.
  • Independently delivered a Sales Roles journey end-to-end within one week, including complex implementation changes.
  • Shared technical knowledge and supported newer team members as they learned the product and its development workflow.
What this represents: Increased responsibility for implementation, coordination, problem-solving, and delivery across interconnected product components.
ENGINEERING IMPACT / ANALYTICS

Impact, made visible.

A snapshot of client contribution and the engineering work behind delivery: implementation, iterative improvements, production support, and journey ownership.

11 client contribution profiles Build · Improve · Support · Own

Client contribution

Supplied contribution levels · scale from 0% to 100%

INDB87%
HDFC75%
BANDHAN30%
CBOI35%
Federal70%
HDBFS45%
RCBC90%
PNB100%
CTBC100%
Security Bank35%
TVS10%

Percentages are the contribution estimates supplied for this portfolio. They are not a company-wide allocation and are not intended to add up to 100%.

Engineering delivery profile

Work delivered across four responsibility areas

Development & implementationJourney builds and implementation work10+journeys
Enhancements & optimizationImprovements to existing journeys and features100+enhancements
Production support & bug fixingIssue investigation, fixes and production support2K+bugs handled
End-to-end ownershipResponsibility across complete journeys4journeys
How to read this: each metric keeps its original unit. These are separate counts, not percentages of one shared total, so the dashboard avoids implying a misleading distribution.
WHAT I BRING TO THE TEAM

Beyond completing individual tasks.

My work combines product understanding, implementation, integration analysis, issue resolution, and collaboration to help deliver dependable product functionality.

01 / ANALYSIS

Business-to-Technical Translation

Breaking down business requirements into implementation tasks, field behaviour, validations, workflow conditions, and functional acceptance expectations.

Requirements Validation Workflows
02 / DEVELOPMENT

Journey & Widget Engineering

Developing and enhancing journey components, implementing field logic, managing conditional behaviour, resolving bugs, and improving the consistency of user flows.

JavaScript UI Logic Form Behaviour
03 / INTEGRATION

API & Data Flow Analysis

Understanding the flow of requests and responses between lending systems, connectors, downstream services, and data-management components to troubleshoot integration issues.

API Integration JSON Postman
04 / QUALITY

Production Readiness

Reviewing journey behaviour, identifying high-risk issues, implementing fixes, and helping teams prepare changes for deployment and production support.

Bug Fixes Issue Tracking Deployment Support
05 / DELIVERY

End-to-End Responsibility

Owning assigned journey components from requirement understanding and implementation through validation, refinement, and delivery coordination.

Implementation Testing Demonstrations
06 / COLLABORATION

Teamwork & Knowledge Sharing

Working with engineers, business stakeholders, and team leads to clarify requirements, resolve blockers, coordinate fixes, and help newer team members understand implementation workflows.

Collaboration Knowledge Sharing Problem-Solving
SELECTED WORK

Turning complex requirements into working journeys.

A closer look at the engineering challenges, implementation responsibilities, and delivery experiences that have shaped my work at Lentra.

Complex Data Integration

Lending journey · PNB workstream
In progress

Worked on a complex journey involving interconnected services, structured requests and responses, and the display of document-management data in the lending application's user interface. The work required understanding the complete data flow rather than treating each component as an isolated implementation task.

My contributions

  • Analyzed the interaction between the loan origination system, integration components, and downstream services.
  • Investigated request and response structures to understand how data moves through the connected systems.
  • Worked on mapping and displaying returned document-management data within the appropriate journey components.
  • Contributed to requirement clarification, journey optimization, and preparation for stakeholder demonstrations.
API Integration JSON Data Mapping Troubleshooting
Core challenge: Understanding cross-system dependencies.
SYSTEM DATA FLOW HIGH-LEVEL VIEW
Lending Application Initiates the request
Integration Layer Routes and processes data
Downstream Services Return the required information
Response Mapping & Display Data presented within the journey

Simplified illustration of the integration pattern. This is not a production architecture diagram or an exact representation of internal services.

Multi-Widget Banking Journey

Philippines banking workstream
Development & support

Worked on a multi-widget banking journey involving more than seven components, with responsibilities spanning development, enhancements, bug fixes, and production support.

Engineering contributions

  • Developed and enhanced interconnected journey components.
  • Investigated defects and implemented fixes to maintain expected workflow behaviour.
  • Supported production issues and time-sensitive troubleshooting.
  • Contributed to ongoing journey improvements and planned enhancements.
Multi-Widget Development Bug Fixes Production Support
Focus: Reliability across connected components.

Sales Roles Journey

CTBC workstream
Delivered

Independently delivered the Sales Roles journey end-to-end within one week. The assignment involved a complex new facet implementation that required additional code development.

What I handled

  • Understood the required journey behaviour and implementation scope.
  • Implemented the journey and the required facet-related changes.
  • Worked through technical complexity and completed the assigned journey within the one-week timeframe.
Independent Delivery Implementation Problem-Solving
Key takeaway: Ownership from implementation to delivery.

Self-Serve & Assisted Journeys

Federal workstream
Self-Serve delivered

Built and deployed the Self-Serve journey from scratch and contributed to the Assisted journey through bug fixes and additional functionality.

Technical contributions

  • Developed the Self-Serve journey from the initial implementation through deployment.
  • Contributed to enhancements and defect resolution in the Assisted journey.
  • Coordinated with the team to implement a complex design that required additional work beyond the directly available studio configuration options.
End-to-End Development UI Implementation Enhancements
Focus: Translating design intent into functionality.

UI & Production Readiness

HDBFS workstream
Quality improvements

Contributed to improving the user experience and identifying issues that could affect production stability and delivery quality.

What I contributed

  • Implemented UI-related improvements across the assigned experience.
  • Identified and tracked high-risk defects that could affect production.
  • Documented issues and shared findings with the team to support investigation and prioritization.
UI Quality Risk Identification Issue Tracking
Approach: Identify risk before it affects delivery.
THE VALUE I ADD

Impact through ownership and execution.

The common thread across my projects is a willingness to understand the problem, investigate the details, coordinate with the team, and work towards a dependable solution.

IMPACT / 01

Independent Delivery

Delivered the Sales Roles journey end-to-end within one week, working through a technically complex facet implementation and associated code changes.

End-to-end execution
IMPACT / 02

Technical Problem-Solving

Investigated complex integrations, response structures, UI behaviour, and journey dependencies to help turn difficult requirements into working implementations.

Analytical execution
IMPACT / 03

Production Readiness

Contributed to journey reviews, issue documentation, high-risk defect tracking, production support, and implementation fixes.

Quality-focused delivery
HOW THE WORK COMES TOGETHER

From requirement to delivery.

A practical approach to delivering dependable product functionality.

01. Understand the requirement

Clarify expected behaviour, business rules, dependencies, edge cases, and the user experience the solution must support.

Requirement Analysis Functional Understanding

02. Implement and integrate

Develop the required functionality, configure the relevant components, trace data flow, and account for interactions between connected systems.

Development Integration

03. Validate and resolve issues

Investigate defects, validate expected behaviour, address identified gaps, and communicate issues that need further attention.

Validation Troubleshooting

04. Support delivery and improvement

Help prepare changes for review or deployment, support time-sensitive issues when required, and identify opportunities for further improvement.

Delivery Support Continuous Improvement
ENGINEERING IN PRACTICE

When the design doesn't fit the available tooling.

Engineering is not only about implementing what is readily available. Sometimes it means finding a practical way to bridge the gap between a design and the capabilities of the development platform.

CHALLENGE / FEDERAL JOURNEYS

Translating a Figma design into a working product experience.

During work on the Federal journeys, the proposed design contained UI behaviour that was not directly available through the Design Studio's existing configuration options.

The challenge was to preserve the intended user experience while working within the technical constraints of the platform.

Understand the gap Reviewed the design and identified where the available platform configuration did not provide the required behaviour.
Coordinate on the solution Worked with the relevant team members to discuss the implementation approach and expected functionality.
Implement the required changes Applied additional implementation changes to achieve the required behaviour where the standard configuration was insufficient.
Focus on functional consistency Worked towards preserving the intended user experience and expected journey functionality.
WHAT I HAVE LEARNED

Growth is more than a change in title.

My development at Lentra has been shaped by increasingly complex problems, new responsibilities, collaboration, and the experience of turning requirements into working product functionality.

Stronger Product Understanding

Developed a deeper understanding of digital lending workflows, business requirements, journey dependencies, and how technical implementation supports business outcomes.

Hands-On Engineering

Expanded my involvement in JavaScript-based implementation, widget development, conditional behaviour, data mapping, issue resolution, and integration analysis.

A Production-Quality Mindset

Learned to look beyond whether a feature works in one scenario by considering dependencies, potential defects, edge cases, and the importance of reliable delivery.

Collaboration & Knowledge Sharing

Worked with engineers, business stakeholders, and team leads to clarify requirements, address technical challenges, share implementation knowledge, and support newer team members.

TRUST EARNED THROUGH WORK

Recognition through contribution.

The most meaningful milestones have been the opportunities to take on more responsibility, contribute to important deliveries, and help the team solve difficult problems.

OWNERSHIP & TRUST

Entrusted With Broader Responsibilities

Took on lead-developer responsibilities for selected journey workstreams and expanded my involvement in implementation, technical problem-solving, and delivery.

DELIVERY

End-to-End Journey Delivery

Independently delivered the Sales Roles journey within one week, including additional implementation changes needed for a complex new facet.

PRODUCT QUALITY

Contribution to Production Readiness

Contributed to journey reviews, production issue resolution, high-risk defect tracking, and implementation improvements across assigned workstreams.

TEAM CONTRIBUTION

Supporting Team Growth

Shared product and implementation knowledge with newer team members while continuing to take responsibility for my own deliverables.

These highlights describe responsibilities and contributions, rather than formal awards or an official team-lead designation.

BEYOND THE CODE

Professional growth also comes from the people around us, the teams we work with, and the experiences we share along the way.

Lentra team celebrating Traditional Day
Traditional Day
Traditional Day Celebrating culture and community.
Lentra team enjoying a cricket moment
Team Moments Shared milestones and memories.
Solo photograph at the Lentra workplace
Everyday Work
Everyday Work Learning through daily collaboration.
Professional group photograph at Lentra
INDB Client Visit Major Milestone for Lentra

Many more memories processing...

Still learning. Still building. Moving forward.

My journey at Lentra has strengthened my ability to connect business requirements with technical execution, take ownership of complex work, and contribute to meaningful product delivery. I look forward to continuing that growth through new challenges, deeper engineering skills, and collaboration with great teams.

Explore My Main Portfolio Revisit Project Work

Thank you for taking the time to explore my professional journey.