Position: .Net developer/Full-stack developer
Category: .NET
English level: upper
Years of experience: 2.5

I'm a .Net Software Engineer. C#, ASP .NET Core Web API, SQL

I’ve successfully completed a great number of courses (especially in
Epam) and have experience in a few .Net projects.
I have a strong desire to work my way up in order to have a great
feeling of accomplishment. Usually my friends characterize me as a
self-assured, goal-oriented and competitive person. I am open to
face changing requirements, I like studying and exploring
something new.
In addition, I have some mentoring skills because of my experience
working as a math tutor for 1.5 year.
]1) Company: Luxoft
From May 2022 till now
MES (Manufacturing Execution System) 
- Project Team Size: 8 people;
 Tools & Technologies: .Net 6, ASP.NET, Entity Framework (Code First), MS SQL
Server, Azure
 Architectural concepts: Modular Monolith, MediaR, CQRS, Clean Architecture

-Description: 
Domain : Manufacturing
Enterprise project for Future Factory. The idea of the project is to digitize work for engineers inside the factory. Using MES people inside the factory are able to control the different working processes and flows such as control of quality,
availability and performance rates on channels and machines inside the factory, making production orders with operations and different materials, label printing and so on.

-Responsibilities
Implementation of separate modules with its business logic
Unit and integration testing
Custom Generic filtering, sorting and pagination on db side using reflection and
expression trees.
--------------------------------------------------------------

2)AAA(authentication, authorization, accounting) server
Project

-Project Team Size: 3 people;

Tools & Technologies: .Net 6, ASP.NET, Entity Framework (Code First), MS SQL
Server, GitHub
 Protocols: OAuth 2.0, Oidc
 Libraries: OpenIdDict
 Flows: Authorization Code flow with PKCE

-Description:
Authorization server with generation of self-contained access token which supports different kinds of flows for different clients (confidential and public ones). For public clients it’s used Authorization Code flow with PKCE according to OAuth2.0 standards to prevent clients tampering and ensure that data of the user can only be received by authenticated apps.
Each jwt-token contains different claims. The claims include scopes and basic user information such as email, time the token was issued, expiration time etc. Having this kind
of information, different APIs can decrypt and validate tokens by themselves. The most obvious benefit of this approach is that there is no need to store tokens and to make
additional requests to the Auth Server for token introspections.