Illia Kotvitskyi

I build and fix the software behind busy financial platforms.

Backend .NET engineer at EPAM. When the trading platform breaks, I find out why and make sure it doesn’t happen again.

Illia Kotvitskyi, backend .NET engineer

Looking for mid-level backend .NET roles in Sweden, or the EU with relocation, from autumn 2026.

  • Authorized to work in Sweden
  • At EPAM since Dec 2024
  • BSc Software Engineering, 2026
  • English C1

Kept a $200K contract by finding the root cause in 48 hours

  1. The problem

    A client saw wrong data between two connected systems and was moving to cancel a $200K-a-year contract.

  2. What I did

    Rebuilt what happened, step by step, from the system’s logs, and found the step that never ran.

  3. The result

    Within 48 hours I showed exactly where the data went wrong. The client stayed, the contract was kept, and the root cause went in as a permanent fix.

audit log, rebuilt
  1. SAP integrationrecords left half-applied
  2. async callbackfailed
  3. retriesfailed
  4. gave upstopped retrying
  5. compensating transactionnever ran

illia@eu:~ $ system fault, not client error. Proven in 48 h.

Shown in the order things happened, not to scale in time.

One of 12+ production problems I investigated during three months on the platform’s Stability team. Three more:

<1 sec

Fixed a login service that kept going down at peak times. Responses are stable and fast again.

~15 min

Saved per incident by a tool I built on my own initiative. Used by 5 engineers.

2 teams

Reused my design for services to retry failed messages automatically.

What I build with

the keywords you may be matching against, grouped by what they’re for

stack
Technologies, grouped by what they are for
Core / .NETWhat I write every day
  • C#
  • .NET
  • ASP.NET Core
  • EF Core
  • Dapper
  • xUnit
Architecture
  • DDD
  • CQRS
  • Event-driven
  • Microservices
  • Modular Monolith
Data & Messaging
  • PostgreSQL
  • SQL Server
  • MongoDB
  • Redis
  • RabbitMQ
  • MassTransit
Infrastructure & Reliability
  • Docker
  • IIS
  • Puppet
  • Jenkins
  • Terraform
  • Datadog
  • OpenTelemetry
  • Git
Certified
  • Azure Fundamentals (AZ-900)

Ask instead of skimming

an AI that answers only from my CV and projects, and says when it doesn’t know

ask about illiapress / to ask
example

What has he shipped in production?

Four things stand out: a 48-hour investigation that kept a $200K client contract, a fix for a login service that failed at peak load, an incident-triage tool now used by 5 engineers, and an automatic-retry messaging pattern 2 other teams reused.

Rather talk to a person? iiiako197@gmail.com

How I work

when something breaks in production

  1. Rebuild what happened

    Step by step, from the system’s logs, before guessing at a cause.

  2. Find the root cause

    Not the first symptom. The fix goes where the fault actually is.

  3. Fix it and prove it

    Reproduce the problem under real traffic, and check the fix there before it reaches production.

  4. Write it down

    A ticket, a decision record or a pattern, so the next person doesn’t have to find it again.

Projects I own end to end

built outside work, to practise how larger systems are designed

Brama Proof of concept

A helper library that catches common programming mistakes before the software is released.

All projects, with the technical details →

Get in touch

Open to mid-level backend .NET roles in Sweden, or elsewhere in the EU with relocation. Email is the fastest way to reach me.

Elsewhere
LinkedIn, or view my CV
Work rights
I’m authorized to work in Sweden. Anywhere else in the EU, I would need a work permit.
Get in touch »CV