Intermediate .NET/C# developer- WORK

Location: Beirut, Beirut Governorate, Lebanon

Department: Aspire Software Lebanon, Research & Development

Workplace: hybrid

Employment Type: full

Description

Aspire Software is looking for a Senior .NET/C# developer to join our team in Lebanon.

Here is a little window into our company: Aspire Software operates and manages wholly owned software companies, providing mission-critical solutions across multiple verticals. By implementing industry best practices, Aspire delivers a time sensitive integration process, and the operation of a decentralized model has allowed it to become a hub for creating rapid growth by reinvesting in its portfolio.

About the Role:

This is a very small team, and that shapes everything about the role. You'll have real autonomy and immediate impact — and there's no one to hide behind: you will own what you ship, in a system that government departments depend on every day. For the right person that's the most interesting thing about the job. If it sounds like too much, it probably is — and that's fine. This is not a ticket-taking role. You'll evaluate the platform, form strong opinions, and drive improvements to how it's built and how it feels to use.

What you'd be working on

The newest parts of the platform are an AI-driven workflow engine that uses LLMs to turn unstructured correspondence into structured data, and a set of recent .NET services built on current versions of the framework. Alongside them run several Spring Boot services on Java 21 handling authentication, search, document conversion and transport — so some working knowledge of Java is needed.

The core of the product is a mature ASP.NET/C# codebase — MVC, Razor, jQuery, Kendo UI, SQL Server and Oracle — with an older server-rendered administration area and a legacy reporting stack that we intend to replace. Modernizing these incrementally, without disrupting the organizations that depend on them, is a significant part of this role and one of the more

interesting engineering problems here.

We're also looking at how this platform evolves toward cloud delivery, and there'll be room to shape that.

We're telling you this plainly because we'd rather you arrive knowing what the work actually is. If the idea of steadily improving a system that matters appeals to you more than starting from a blank page, this will suit you.

We operate AI-first. Daily, hands-on use of AI-assisted tools (Claude Code, Cursor, GitHub Copilot) is a core requirement — not to generate code blindly, but to design, implement and critically review production-quality work alongside your own technical judgment.

What you'll do

• Build and improve features and services in .NET/C#.
• Modernize legacy components incrementally — identify outdated patterns and propose concrete refactoring, with a realistic sense of what's worth changing and what isn't.
• Evaluate user workflows and interfaces, and reduce friction where the product doesn't serve users well.
• Write and maintain automated tests for what you ship. We have a substantial Playwright end-toend suite covering the web application and the service APIs; unit-test coverage in the .NET code is where the gap is, and closing it is part of the job.
• Contribute to the LLM workflow engine: understand how it uses LLMs, find its limits, and improve prompts, workflows and data-processing logic for better accuracy and reliability.
• Integrate APIs, messaging and third-party services.
• Take initiative — step into problems before they're assigned and drive them to done.
• Share context early and keep the team in the loop.

Requirements

• Solid, real-world experience shipping applications in .NET/C#; comfortable reading and improving large existing codebases.
• Hands-on experience with LLM-based systems — prompt engineering, evaluating and improving model output, and building or maintaining LLM-driven workflows in production.
• Comfort in a server-rendered stack — Razor, jQuery, Kendo — and the patience to improve it step by step rather than rewrite it.
• Enough working knowledge of Java to understand and contribute to Spring Boot services.
• Good grasp of API design, backend services and relational databases.
• The habit of testing your own work — comfortable with end-to-end tests, and willing to write the
• first unit tests for modules that have no coverage today.
• Practical software-design sense, and the judgment to know when to apply it.
• Strong communication and collaboration — a must-have. You work well side by side with others and you're approachable.
• Fluent English, written and spoken — a must-have.
• Mandatory: daily, hands-on use of AI-assisted dev tools to produce, review and ship production code.
• A bias toward improving systems rather than accepting them as-is, and comfort working with limited direction.

How we work - Definition of done

A change isn't done until it's tested. Every feature, fix or refactor ships with the automated tests that prove it works and guard against regressions. In a small team with no separate QA function, developers own the quality of what they deliver.

Nice to have

• Experience taking an on-premise product toward cloud or SaaS delivery — containerization, multi-tenancy, CI/CD pipelines, or cloud deployment (Azure preferred).
• Background in enterprise or government software — compliance, auditability, accessibility.
• Front-end modernization experience, migrating legacy server-rendered UIs.
• Playwright experience.