Senior .NET Engineer

About The Role This role will support the AutoWeb business, which operates a marketplace that connects car shoppers with dealers and manufacturers. The systems behind it run on .NET, they are customer facing, and they carry live transaction volume every hour of the day. When something goes wrong, dealers notice, consumers notice, and revenue moves. That is the level of consequence this role sits at. Two engineers cover this platform, a lead engineer in North America and you in Yerevan. We built it this way on purpose. An eleven hour offset from the Americas means the marketplace has senior engineering attention through the working day on both sides of the world, which is a real advantage for a system our customers use around the clock. This posting is for the Armenia seat. During your hours you are the senior engineer on the platform. Issues that come up are yours to resolve and the decisions that come with them are yours to make. That is the substance of the role, and it is why it is a senior one. How The Role Is Structured You will report to a manager in Armenia, and the wider engineering organization runs through our VP of Engineering. Your day-to-day technical direction comes from the lead engineer for this platform, based in North America. They own the platform and set its direction; you own the systems during your hours and carry a real share of the build. You will be handed scoped work and trusted to make the calls inside it, not handed a script to follow. The practical shape of it is a handoff twice a day. What you leave behind at the end of yours determines how their day goes, and the reverse. Engineers who write things down and give context in advance do well here. Engineers who keep the important context in their heads do not. You will also work regularly with product and business colleagues in the United States and engineers in Ukraine. To be clear about scope, this is a standard working day. Coverage means you are the senior engineer on the platform during your normal hours, not that you are on call outside them. Anything that breaks overnight in Yerevan is the North America lead's to handle. [Note any on-call rotation, holiday coverage, or premium here if one applies.] Your overlap window with the Americas is at the start of your day. The rest of it is yours, which means long stretches of uninterrupted work and real autonomy over how you use them. What You Will Do Own the design, development, testing, and release of features across customer-facing .NET applications and the services behind them. Cover the platform during your hours. Take production issues from first report to resolved root cause, including the ones that need a decision before anyone in the Americas is awake. Modernize as you go. Parts of this platform predate current .NET, and moving them forward without interrupting a live marketplace is a core part of the job rather than a side project. Design and build APIs that partners, dealers, and internal systems depend on. Work on SQL Server performance and data design, including query and schema work on systems under real load. Hand off cleanly to and from the platform lead in North America, with the written context that makes continuous coverage possible. Review code and raise the standard of what ships. Translate business requirements from product and marketing partners into technical designs, and push back when the requirement and the system are pointing in different directions. Working with AI Every developer here has Claude and GitHub Copilot, and they are part of how the work gets done rather than an optional extra. What matters to us is judgment: knowing which tasks to hand to a model and which to write yourself, giving it enough context to return something usable, and reviewing what comes back as carefully as you would review any other engineer's pull request. You should be able to explain every line you merge. The more important thing to know is where this is heading. Over the next six to twelve months we expect to move substantially toward agentic development, with agents taking on larger and more autonomous portions of the build and test cycle. That will change our tooling, our workflow, and what the day-to-day job looks like. We are not asking you to have done this before, because very few people have. We are asking you to be genuinely interested in figuring it out with us, and comfortable working in an environment where the way we build is still being reshaped. If you would rather join a team with a settled toolchain, this is an honest reason to look elsewhere. If that prospect is the interesting part, we should talk. What You Bring 5 to 8 years building and supporting production .NET applications, including time as the senior person others came to. Strong C# and ASP.NET, across both modern .NET and the older framework versions that real businesses still run on. API design and development experience, including integrations that external partners depend on. Real SQL Server depth: query optimization, indexing, and schema design against systems under load. Production experience on Azure. Our platform runs there. Enough front-end familiarity (JavaScript, HTML, CSS) to work effectively on customer-facing applications. Judgment about legacy code. Knowing when to modernize, when to leave it alone, and how to tell the difference. The temperament to own a live platform on your own for part of the day: calm under a production issue, decisive without a second opinion available, and disciplined about escalating the things that genuinely warrant it. Comfort working through change. Our stack and our development practices are actively evolving, and you should find that energizing rather than unsettling. Professional English, written and spoken. Your handoffs, design discussions, and code reviews all happen in it. Nice to have Experience in automotive, marketplaces, lead generation, or another high-volume transactional domain. Migration experience, particularly legacy .NET Framework to modern .NET, or on-premises SQL Server to Azure SQL. Multi-threading and parallel processing work. Familiarity with XML and XSLT, which appear in parts of this platform. CI/CD and automated testing practice. Agile delivery in a distributed team. Why work with us? The systems here matter and the team is small enough that you will see the effect of your work directly. This is not overflow work handed down from somewhere else. You own a live customer-facing platform for half of every day. We invest ahead of the curve on tooling, we retire what no longer serves us, and we would rather ship and learn than deliberate indefinitely. Powered by JazzHR auigpsWsBK