Senior .NET Backend Engineer

About us
We’re Smart Factory — a product company building software that runs real manufacturing operations. It’s a long-term, growing product, and we’ve invested heavily in doing the engineering properly.
Our backend is something we’re genuinely proud of: a clean, service-oriented architecture that’s thoroughly documented, where the design and the diagrams come before the code. It’s modern, well-structured, and built to last — a codebase you can reason about and extend with confidence, without fighting technical debt. We’re looking for one more strong backend engineer to build it with us.

Why you might love this role
Design-first, for real. We agree the design — use cases, call chains, sequence diagrams — and review it before implementation. No spaghetti, no “we’ll document it later.” If clean architecture is your thing, you’ll feel at home.
Real ownership. You won’t just take tickets. You’ll take part in design discussions, architecture decisions, and planning — with direct access to our CTO for architectural sparring.
It’s a long game. A multi-year product with a growing customer base. We’re looking for someone to grow with the team, not for a short contract.
Mobilization protection (бронювання). For the right person, we can arrange official reservation.
Remote. All communication and documentation on the team happens in English. What you’ll do
Design and build APIs and services in ASP.NET (8+) and EF Core (8+) on Azure
Produce the design first — activity & sequence diagrams — then implement against it
Take part in architecture, planning, and design reviews
Write the unit and integration tests that keep the system reliable
Work independently from well-structured documentation, and explain and justify your decisions clearly

This role will suit you if
You enjoy thinking deeply, you like owning decisions and standing behind them, and you can move independently without waiting to be told what to do. The work is genuinely analytical — for the right person, that’s the best part.

What matters to us
A few things we pay close attention to, beyond the tech:
Clear English. You can hold a fluent conversation, write clearly, and be understood with ease — all our work happens in English.
You can present your thinking. When you propose a solution, you can walk us through it and explain why. A clear, well-structured story tells us the thinking behind it is just as clear.
Consistent quality, end to end. We care how every stage is done — clean code, good communication, handling the unexpected, and delivering close to what you estimated. Not only the result, but how you get there.
What we seek
Proven experience designing and building APIs in ASP.NET (version 8.0 or higher)
Proven experience with Entity Framework Core (version 8.0 or higher)
Proven experience with Microsoft Azure
At least 8 years of professional experience with C#
At least 8 years of experience building unit and integration tests
Knowledge of service-oriented architecture (SOA) principles
Knowledge of integration patterns and principles
Knowledge of OAuth and OpenID Connect security protocols
Adheres to SOLID principles
At least 7 years of experience with Azure DevOps and Git
Understanding of UML activity diagrams and sequence diagrams
Fluent English, written and spoken — you can present and justify your work clearly (all documentation and communication is in English)
Nice to have
Azure platform services (Service Bus, Key Vault, AI Search, SQL Database) • Azure DevOps YAML pipelines with PowerShell
T-SQL (SQL Server)
Familiarity with the IDesign Method

How we hire
We’ll be honest: our process is thorough — because we’re building something we’ll live with for years, and we want the fit to be right for both sides. Here’s the whole path up front, so there are no surprises:
1. Intro call — we get to know each other (background, English, what you’re looking for)
2. Short online test (~10–15 min) — technical skills and analytical thinking
3. Technical interview with our CTO — including a walk-through of the system
4. Trial preparation — we share documentation and context; you prepare your approach and present it on a short call
5. Paid trial assignment (1–3 weeks) on real work. We can keep this part-time, so you can comfortably fit it around your current job — you get to see how we actually build, and we get to see how you work
6. Offer — welcome to the team
The trial is paid because it goes both ways: you’re getting paid to find out whether you like how we
work, too.