Назад
2 дня назад

Senior/Lead .NET Engineers

Формат работы
hybrid
Тип работы
fulltime
Грейд
senior/lead
Английский
c1
Страна
Armenia
vacancy_detail.hirify_telegram_tooltipВакансия из Telegram канала -

Мэтч & Сопровод

Покажет вашу совместимость и напишет письмо

Описание вакансии

TL;DR
Senior/Lead .NET Engineer (.NET/AWS/Angular): Building backend and full-stack solutions with an accent on .NET engineering, Angular development, AWS, and collaboration across US time zone overlap. Focus on developing reliable software for multiple projects and matching backend or full-stack expertise to suitable engineering roles.

Network jan, I’m once again looking for strong Senior/Lead .NET Engineers to join us on an exciting project!
We are open to both Backend .NET Engineers and Full-Stack .NET Engineers with Angular experience.

What we’re looking for:
• Strong hands-on experience with .NET (Backend or Full-Stack)
• Experience with Angular (for Full-Stack profiles)
• Experience with AWS
• Fluent English and strong communication skills
• Availability to work with US time zone overlap

📍 Hybrid | Yerevan, Armenia

Interested or know someone who could be a great fit? Feel free to DM me directly or drop a comment below! 😊

#.Net #Angular #FullStack #BackendDevelopment #SoftwareEngineering #TechJobs
One technical interview. Multiple possibilities. 👀

That’s one of the things that can make recruitment at a service providing IT company different.
Instead of being considered for just one position, engineers may have the opportunity to explore multiple projects and roles, and find a match that works for both sides.

But how does it actually work?
Let’s break down the journey. 👇
Wrapped Anthropic's AI Fluency certification. Took it expecting basics, got more than that.
Discernment is what I kept thinking about after. AI has no idea why your system is the way it is, but it will still give you a confident answer. That context lives in your head, not in the prompt.
Diligence doesn't get nearly enough attention. The output looks polished, so the scrutiny drops. That's exactly when it shouldn't.
The more you delegate, the more discernment and diligence matter.

#Java #BackendDevelopment #AI #SoftwareEngineering
I enjoy building reliable, scalable, and clean backend systems that solve real business problems.
Over the past years working as a .NET Developer, I’ve focused on writing high-quality, maintainable code and designing systems that are secure, performant, and production-ready. My experience includes:
• Designing and developing backend services with .NET / C#
• Building scalable APIs and working with high-load systems
• Applying Clean Architecture, SOLID, and best practices
• Improving application security (authentication, data protection, secure flows)
• Working with cloud technologies and modern development workflows
Recently, I’ve been especially interested in performance optimization, system design, and building resilient distributed systems.
I always enjoy connecting with professionals, sharing knowledge, and discussing engineering challenges. If you’re working on interesting technical problems or building impactful products — feel free to connect.
#dotnet #backend #softwareengineering #csharp #systemdesign #cleanarchitecture #developers
Cut AWS costs by 5% without touching a single line of application code.

Just S3 lifecycle policies. Moving old data to cheaper storage tiers automatically, instead of everything sitting in standard storage forever.

We had years of stored objects nobody was actively reading anymore. Logs, old exports, historical data. All sitting in the most expensive tier, just because nobody set up a policy to move it.

Took maybe a day to actually implement. The savings kept adding up every month after that.

Sometimes the biggest win isn’t in the code. It’s in the infrastructure nobody’s looked at in a while.

What’s a cost or performance win you found outside of the actual codebase?

#AWS #Backend #CloudCost #NodeJS #SoftwareEngineering
Interviewed a fullstack engineer last week. Solid on APIs, comfortable with ORMs.

Asked him about the saga pattern. Blank stare, “not familiar with that one.”

After couple of other questions I asked “How would you handle transaction between microservices with different DBs.

After couple of clarificaton questions he nailed it as he was answereing the “saga” question.

He didnt know the name but he understood the problem.

The term is just a shortcut for experienced people to talk to each other fast. It’s not the actual skill.

Have you ever had a moment like that, knowing the “how” without knowing the name for it?

#Backend #SoftwareEngineering #DistributedSystems #SystemDesign
Some standup updates need their own calendar invite.

Opened the laptop. Checked slack. Read 3 messages. Made coffee. Then actually got to work.

By the time they get to what they worked on yesterday standup is already 10 minutes over and someone has muted themselves to make a second coffee.

In the meanwhile the person who did the most work says "worked on the ticket, no blockers" and moves on in 8 seconds.

Weird correlation the longer the update the less usually got done.

What's the longest standup update you've sat through?

#Standup #SoftwareEngineering #TechHumor #Backend #DevLife
Փնտրում եմ C# .NET & SQL մասնագետի

Mid-level՝ 1-2 տարվա backend փորձով,

պահանջվող հմտություններ՝

C# .NET Core/.NET Framework, ASP.NET Web API/MVC, RESTful APIs, MS SQL Server, T-SQL, CRUD operations, ORM (Entity Framework/Dapper), OOP principles, auth basics (JWT/OAuth), debugging & log analysis
Agile/Scrum a plus

Դիմելու համար կարող եք անցնել հղումով 👇

https://lnkd.in/dKzB5sab
Something I learned running services on GKE: autoscaling does not give you free reliability. It just moves the problem somewhere else.

We had a service that scaled well under load. New pods started fast when traffic went up. But each new pod opened its own fresh set of database connections. At peak traffic, we had way more open connections than the database could handle. The pods scaled fine. The database did not.

The fix was not more scaling. It was adding a connection pooler in front of the database. Now all the pods share one limited set of real connections, instead of each pod opening its own.

Lesson: Kubernetes will happily scale your app right into a wall if the thing behind it cannot scale the same way. Autoscaling only helps the one layer you put it on, not everything downstream.

#Kubernetes #GCP #Backend #NodeJs #SystemDesign
#notaigenerated
You know what’s interesting?
AI is helping teams ship features in days instead of months. Yet many of those same companies are struggling financially. Then they lay off employees, hoping it will increase revenue, but a few months later, they see no significant changes.
Why? Because cutting costs doesn’t always address the root cause, when customers don’t have enough purchasing power.
I see a similar pattern at an individual level. Many people, including myself, have started cutting unnecessary expenses and building safety cushions because of economic uncertainty.
But when millions of people do the same, consumption slows down and when it slows, businesses feel the impact.
And seem like we are in a broken loop.
I don’t know, I don’t know 🤷♀️
Maybe I’m wrong, maybe I’m right, but I haven’t noticed many companies experiencing revenue growth as a result of implementing AI🤔
But let’s focus on companies that don’t produce chips and haven’t laid off employees to show improved financial results.

Будьте осторожны

Если работодатель просит войти в их систему, используя iCloud/Google, прислать код/пароль, запустить код/ПО, не делайте этого. Это мошенники. Обязательно жмите «Пожаловаться» или пишите в поддержку. Подробнее в гайде →

Текст вакансии взят без изменений

Источник -