Bench+
← Back to talent
I

BENCH+ PROFILE

Ismoil

Backend Engineer
Node.js and TypeScript backend development for fintech, payments, lending, marketplace, and document workflow systems

Backend-focused engineer with strong fit for TypeScript, Node.js, NestJS, microservices, integrations, and transactional API systems in fintech-adjacent environments.

BEST-FIT USE CASE

Backend implementation role for payment, lending, marketplace, or document-workflow platforms requiring TypeScript services, API contracts, asynchronous messaging, third-party integrations, cloud deployment support, and production maintenance.

Not the primary fit: Less aligned with roles centered on frontend ownership, platform-only operations, AI engineering, product management, or formal technical leadership as the main responsibility.

EVIDENCE HIGHLIGHTS

What supports the assessment

01

Implemented backend services for a local payment-system workflow using Node.js, NestJS, TypeScript, microservices, integrations, AWS, and occasional frontend support.

02

Developed backend functionality for a lending platform with TypeScript, Node.js, NestJS, event-driven flows, CQRS-style patterns, gRPC, SFTP, and cloud monitoring.

03

Built backend services for fiat and cryptocurrency financial workflows, including exchange operations, asynchronous processing, GraphQL, gRPC, and database-backed services.

04

Developed marketplace backend functionality including multi-level authentication, search filtering, payment-gateway integration, REST APIs, and cloud storage.

05

Implemented backend logic for auction-style workflows involving bidding, user point calculation, deadlines, notifications, and secure payment processing.

06

Developed backend architecture for document editing, e-signing, sharing, storage, event-driven components, and cloud storage.

WORKING STYLE

How they show up

  • Works mainly on backend tasks while covering frontend tasks when the team needs broader delivery support.
  • Collaborates through task updates, team communication, and delivery alignment in distributed project workflows.
  • Became more autonomous on a complex project after adapting to the codebase and delivery process.
  • Improved code quality, unit testing, communication, and transparency over time on a complex backend project.