Position: Senior .Net Software Engineer
Category: .NET
English level: upper
Years of experience: 4

Designed an epic about multiple (secret file type name) file upload, which included parallel parsing of the files and big refactoring.

Designed a story about model changes notification with the SignalR technology.

Fixed the bug in the mechanism which is used to parse model objects from XML trees.

Designed a story about the integration of the new microservice (storage of big XML models) with the main application.

Created documentation article after implementation of the epic about the conversion of the Domain projects from EF to EF Core.

Executed manual user test cases during integration weeks. Reported bugs. Analyzed and fixed bugs from database logs.

Prepared and demonstrated several demos for PO and SA.
Full Stack ASP.NET Core Software Developer with 2 years of commercial experience on an enterprise project in the telecommunication domain. And 2y on USA car wash automation project.

Have experience with front-end as much as back-end. On a daily basis, I performed story and epic investigation and design, task/story review, implemented 100% code coverage by unit, and integration (service-level) tests, fixing bugs (production as well), fixing code style, coverage, code duplication issues generated by SonarQube.

The development process was by Scrum methodology and from time to time we used to take Kanban when we were assigned a  maintenance role at the UAT phase or integration weeks.

As I came to the legacy (10 years old) project in a time of big changes I implemented (with my team of course):
1) Two new microservices. The first was for the creation and saving of any operation result. The second was for saving large XML models of the domain models. Also, the cache was implemented and configured to store huge models wrapped in the WeakReference objects to avoid OutOfMemoryExceptions.

2) Visual Studio extension that brought us the possibility to create a whole new module of projects (Extensibility, Domain, Service, Test, WebApi, WebClient).

3) Conversion of all existed microservices from EF to EF Core.

4) Parallel parsing of the (secret file type name) files. Later we refused this idea because of the poor server's parallel execution capabilities. I wanted to tell about it because this was a good application of the platform internals knowledge (GC modes).

Also, personally, I like to prepare and demonstrate demo sessions to PO or SA and dev sessions after the design for a story. I'm interested in team leadership and going to grow up to the Team Lead position.
Ready to be challenged by the new domain. Won't work in a project with old technologies like .NET Framework and ASP.NET.