Position: Middle .NET Developer
Category: .NET
English level: upper
Years of experience: 3

One of the most challenging projects required building reporting extension from ground up. During that project I had widest set of responsibilities in my career: discussing business requirements with client, setting up architecture in ASP.Net MVC 5 (with no commercial experience with that particular framework) on top of massive legacy codebase, estimating, supporting and relaying requirements to front-end teammate and so on. There were only two of us, but we managed to get a lot of work done.
I have participated in multiple projects of varying team sizes (small-middle), with diverse responsibilities (fixing tickets on Jira - communicating with clients and setting up project architecture), mainly in fintech sphere. One of the most common tasks I had was integration of external service into our system, like adding support for cloud storage or powerful dashboards.

I love solving complex problems using modern tools and best development practices.
I'm pretty flexible with my expectations. I would love working on a project of any scale, and I don't mind learning new things if they are required. There are only two things that would greatly influence my decision to join a project. 
First is company and team work culture, where respect and understanding between teammates is a must.
Second is meaning. I believe people are most productive when they understand *why* they are doing something. That's why communication between management\clients and team is important. If I know the project history where it is now, and which real world problem it's supposed to solve, I'm equally motivated to fix a bug or build new service. Also, if you don't understand the purpose of feature you are implementing, you most likely won't do it right.

Also, remote is a plus.