Work
Remote .NET architecture and senior development work
I am open to relevant remote work where senior .NET experience, architecture judgement, maintainability, and long-term application quality matter.
This can be a full-time role, part-time role, contract engagement, focused architecture review, or advisory collaboration — as long as the work is serious, remote-compatible, and connected to building or improving maintainable software.
Updated 2026-08-07
Currently open to
Available for remote senior .NET roles, contract architecture work, and focused advisory engagements.
Availability and working model
I am primarily interested in remote collaboration with teams that need senior .NET, architecture, maintainability, or technical leadership experience.
Availability
- Remote senior .NET, system architect, lead developer, contract, or advisory roles.
- Full-time, part-time, or focused short-term engagements depending on fit and timing.
- Best suited for Europe / CET-compatible collaboration, but open to international remote teams when the working model is practical.
- Occasional planned meetings are fine; regular on-site presence is not a good fit.
Working model
- Clear written communication, practical technical recommendations, and independent delivery.
- Comfortable working with existing teams, existing codebases, and established business systems.
- Preference for focused collaboration where meetings support progress rather than replace it.
- Useful in roles where architecture, maintainability, delivery, mentoring, and technical judgement overlap.
Why work with me
I bring long experience with business-critical .NET systems, including applications that need to keep evolving safely over many years.
- Strong background in senior .NET development, system architecture, lead developer work, and technical consultancy.
- Practical experience with maintainability, modernization, clear boundaries, testing, and long-lived business applications.
- Comfortable working with existing systems where improvement has to happen incrementally, without unnecessary rewrites.
- Used to remote collaboration, stakeholder communication, mentoring, documentation, and independent delivery.
- Focused on making technical decisions understandable, useful, and connected to real project constraints.
Selected writing for architecture-minded teams
I regularly write about practical software architecture, maintainability, testing, boundaries, and long-lived .NET systems. These articles give a more detailed picture of how I think about technical decisions.
Architecture
Articles about boundaries, dependency direction, maintainability, architectural drift, and keeping systems understandable as they evolve.
Development
Articles about tests, naming, dependency injection, validation, business rules, and practical .NET design choices.
Improving existing systems
A practical example of how I approach maintainability, boundaries, and incremental improvement in existing .NET codebases.
Good-fit roles and engagements
System architect
Architecture and design responsibility for .NET applications where boundaries, responsibility placement, maintainability, and long-term changeability matter.
Senior .NET developer
Senior implementation work in C#, .NET, application services, WPF, desktop applications, backend components, and maintainable business application code.
Lead developer
Technical leadership, code review, implementation direction, mentoring, and practical architectural guidance for teams that need experienced judgement.
Architecture review
A focused review of a .NET application, codebase, or architecture decision, ending with practical observations, risks, and next steps.
Maintainability improvement
Help identifying unclear boundaries, overly broad services, infrastructure leakage, fragile tests, and areas where normal changes have become unnecessarily expensive.
Technical mentoring
Support for developers or small teams who want to improve architectural thinking, testing habits, code quality, and confidence in technical decisions.
Types of work I am open to
- remote full-time employment
- remote part-time employment
- contract work for senior .NET development or architecture support
- focused architecture or maintainability reviews
- technical advisory work for long-lived .NET business applications
- remote collaboration with teams that value quality, clarity, and ownership
Work that is especially relevant
I am most interested in software where maintainability is not an afterthought: systems that are expected to live for years, support real business workflows, and continue changing as the organization learns.
Long-lived business applications
Applications where technical decisions have long-term consequences for daily development, operational reliability, and the ability to support changing business needs.
.NET and C# systems
C#, .NET, application services, backend components, integration code, and structured application development where clarity and consistency matter.
WPF and desktop applications
Windows desktop applications where responsiveness, usability, structure, MVVM boundaries, and long-term maintainability are important.
Architecture and boundaries
Work involving responsibility placement, dependency direction, infrastructure boundaries, testability, refactoring, and reducing avoidable coupling.
Not a good fit
To keep the contact form useful for serious inquiries, these are generally not relevant:
- SEO outreach, guest-post offers, link exchanges, or generic marketing services
- unpaid startup pitches or vague business opportunities
- low-cost outsourcing or body-shopping arrangements
- roles that require regular on-site attendance
- projects unrelated to .NET, architecture, maintainability, or serious software development
- cryptocurrency, gambling, or other speculative business proposals
What to include when contacting me
If you contact me about a role, contract, or consulting engagement, please include enough context to make the opportunity easy to evaluate.
- company or organization
- role or engagement type
- whether the work is remote, hybrid, or on-site
- expected time commitment, such as full-time, part-time, or contract
- technology stack and application type
- main architecture, maintainability, or delivery challenge
- expected timing or start date, if known
Related pages
Services
Read more about focused .NET architecture and maintainability advisory, including the .NET Architecture Review starter engagement.
Improving an existing .NET codebase
See how I approach maintainability, boundaries, and incremental improvement in existing .NET systems without unnecessary rewrites.
How I Work
Read more about my approach to architecture, maintainability, testing, usability, ownership, and collaboration.
CV
Download my CV for a more traditional overview of experience, roles, technologies, and professional background.
Selected articles for technical decision-makers
These articles give a sense of how I think about architecture, maintainability, boundaries, testing, and long-lived .NET applications.
Relevant remote role, contract, or advisory opportunity?
Send a short description of the role, engagement, application, or technical challenge, and I can assess whether it looks like a good fit.