Bench+
← Back to talent
E

BENCH+ PROFILE

Evgeny

Backend Engineer
High-load distributed backend systems with Go and .NET microservices

Senior backend engineer suited to high-load microservices, transaction-heavy systems, and backend modernization involving Go, .NET, relational databases, messaging, and service-to-service architecture.

BEST-FIT USE CASE

Backend implementation or technical leadership for transaction-processing platforms, distributed microservices, legacy-service migration, and backend components for AI-enabled applications where the role includes architecture, hands-on implementation, and team guidance.

Not the primary fit: Pure frontend, mobile-only, product management, QA-only, security-operations-only, or research-oriented model-engineering roles.

EVIDENCE HIGHLIGHTS

What supports the assessment

01

Owned or led backend architecture and implementation for transaction-processing microservices using Go and .NET in a fintech domain.

02

Implemented high-throughput workflows for transaction streams, discrepancy detection, reconciliation, chargeback routing, and payout-related processing.

03

Led backend development across multiple projects, including microservices strategy, legacy migration to newer .NET versions, and secure authorization workflows.

04

Built backend systems for travel-related search, payment, and transactional messaging with message-broker processing under high traffic.

05

Engineered academic information and process-automation systems with database infrastructure and backend performance work at institutional scale.

06

Built independent full-cycle applications combining backend services, mobile frontend work, local document processing, and AI-assisted data features.

07

Technical interview discussion covered REST versus gRPC versus messaging, monolith decomposition, consistency strategies, observability, indexing, dependency injection, and security topics.

WORKING STYLE

How they show up

  • Uses Scrum-style delivery with two-week sprints, task tracking, time logging, and clarification of requirements when needed.
  • Recognizes the developer role in implementing business decisions while raising technical or value-related questions without blocking delivery.
  • Considers architecture decisions through business horizon, budget, service-level expectations, team onboarding, infrastructure constraints, integrations, compliance, and long-term support.
  • Describes task planning as implementation design, estimation, peer validation, baseline planning, iterative adjustment, and progress control.
  • Has experience with code review and mentoring in senior engineering teams.