Lead .NET Engineer

Location:Onsite, full timeat ourBuyerlink office right on the Inner Harbour of Victoria, BC

Working hours:Standardfull-timebusiness hours, with an early overlap window with our Armenia team

About the role

Weoperatea 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.

This is the platform ownership role. You will set the technical direction for the marketplace platform, make the architecture calls, and be the person accountable for its health. Two engineers cover it, you in North America and a senior engineer in Armenia. That is a deliberate design: aneleven houroffset means the marketplace has senior engineering attention through the working day on both sides of the world, which matters for a system our customers use around the clock. What gets built, in what order, and what moves overnight is yours to decide.

This is not a role where you take tickets off a queue. You will be one of a small number of people who understand these systems deeply, and you will be expected to act like it.

How the role is structured

You will report to our VP of Engineering and work daily with engineering, product, and business colleagues across the United States, Latin America, Armenia, and Ukraine. Our US stakeholders will cometo you directly, and translating what they need into technical work is a real part of the job.

You will lead the senior .NET engineer in Armenia on this platform. You set their technical direction, decide what they pick up, and review what comes back. To be precise about the boundary, this is technical leadership rather than people management. Their employment relationship sits with our Armenia organization, so hiring, performance, and compensation are not yours. Everything about how the platform gets built is.

The practical shape of it is a handoff twice a day. What you leave behind at the end of yoursdetermineshow their day goes, and the reverse. Leads who write things down and give context in advance get real leverage out of the offset. Leads who keep the important context in their heads do not.

One thing to be clear about: as the platform owner in this hemisphere, production issues that surface outside the Armenia working day come to you.

What you will do

• Own the design, development, testing, and release of features across customer-facing .NET applications and the services behind them.
• Take production issues fromfirstreport toresolvedroot cause, including the ones that surface during your hours and need a decision now rather than after a meeting.
• 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 schemaworkon systems under real load.
• Direct the work of the senior engineer in Armenia: set priorities, scope what they take on overnight, review what comes back, and give them enough context to make good calls without you.
• Build a handoff practice thatactually works, so overnight coverage produces progress rather than a queue of questions.
• Review code and raise the standard of what ships.
• Translate business requirements from product and marketing partners into technicaldesigns, andpush back when therequirementand 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 twelvemonthswe expect to movesubstantially towardagentic 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 els