Backend Solution Architect
Details
About job
Our client runs a large distributed platform that brings all project-related data into one place and surfaces the key information to enterprise clients. Teams collaborate on complex, multi-phase engagements, and clients get detailed analysis, visibility, and control during high-value transactions such as acquisitions or divestments.
The platform is built on a microservices architecture with a modern .NET stack, supports role-based access across multiple user types, and generates the final report that closes out each project.
You will own the technical solution end to end — from translating vague business requirements into architecture, through defining trade-offs, to making sure the team delivers on time and to standard.
Your Responsibilities
- System architecture: define application, security, infrastructure, and deployment architecture for solutions across the platform
- Business-to-technical bridging: talk to the business, translate ambiguous requirements into technical PBIs, negotiate trade-offs, and set direction
- Delivery ownership: review and approve all technical deliverables and timelines together with the PM, and manage technical risk
- Hands-on engineering: write production code at high velocity, run code reviews, and enforce standards and test coverage
- Technical leadership: mentor the team through every stage of the SDLC and introduce design patterns with a clear rationale
- Feasibility & impact: own POCs, impact analysis, and assessment of breaking versus non-breaking changes
- Client communication: act as the central technical contact for client representatives and resolve cross-team dependencies
Skills required
- 13+ years of experience in software development, with a strong solutioning focus
- Expert-level C# and .NET Core — ASP.NET Web API, Entity Framework Core, Dependency Injection, Unit of Work and Repository patterns
- Azure in production: App Service, Service Bus, Functions, SQL Database, Azure DevOps
- Strong SQL and relational database experience (MS SQL / Azure SQL, MySQL, SSRS)
- Testing discipline: xUnit or nUnit, unit and integration testing, Postman, Fiddler, profiling and static analysis tools
- Nice to have: microservices, Docker, Kubernetes, Redis, MediatR, OAuth / JWT, OWASP, CI/CD, basics of React and TypeScript
- Excellent English — you will explain technical concepts to technical and non-technical stakeholders alike
- Consultant mindset: ownership, urgency, and the willingness to argue for the right solution
What can you expect?
- Real architectural authority — you define the direction, not just implement someone else's
- Direct contact with the client's business side, not a layer of proxies between you and the decision
- A platform with genuine technical ambition: microservices, high quality bar, no legacy shortcuts
- Long-term engagement with a stable, senior team
- Occasional travel across the EU and UK for planning sessions and workshops
Start date
- Start: ASAP
- Workload: Full-time
- Setup: 90% remote — attendance at planning sessions and workshops roughly 4× per year, up to one week each (free travel around the EU and UK required)
- Working hours: 11:00–19:00 CET, core hours 14:00–19:00 CET
Reward
Get rewarded.
No lengthy forms — just a name and a contact. We handle the rest. Reward paid once they pass their three-month probation.

Process
Four steps, no take-home assignments.
5 minutes
Apply
CV or LinkedIn, no cover letter. We reply within 48 hours — to everyone, including the no's.
ASK
— which stack
— how many people
— from when
— what you're solving
45 minutes
Tech call
With an engineer, not a recruiter. Architecture, tradeoffs, your real projects. No "describe a situation where you had to…".
ASK
— which stack
— how many people
— from when
— what you're solving
90 minutes
Pair na reálném kódu
An existing repo, a real bug or a small feature. We care how you think and debug — not whiteboard algorithms.
ASK
— which stack
— how many people
— from when
— what you're solving
Within 7 days
Offer
A concrete number, a concrete project, a concrete team. Decision within a week of the pair session.
ASK
— which stack
— how many people
— from when
— what you're solving



