Full-Stack Engineer (AI / .NET)

About the role

Our client is an innovative organization dedicated to modernizing administrative infrastructure and optimizing operational efficiency. We are seeking a Lead Systems Automation Analyst to spearhead the evolution of enterprise platforms, bridging the gap between established legacy architectures and cutting-edge artificial intelligence solutions.

Responsibilities

• Architecting and rebuilding key enterprise portals, completely transforming legacy applications into highly responsive, AI-augmented user interfaces.
• Harnessing internal large language model (LLM) frameworks, specifically customized instances of Claude, to prototype, build, and deploy custom workflow tools tailored for specialized decision making support.
• Designing and engineering scalable backend services and secure web APIs utilizing .NET Core, C#, and modern RESTful integration patterns.
• Collaborating with operational business units and technical teams to gather requirements, extract workflow logic, and author comprehensive system blueprints.
• Evaluating and embedding emerging AI technologies, including Copilot and Azure OpenAI APIs, to drive intelligent workflow automation and enhance business intelligence.
• Maintaining and supporting existing legacy systems, including localized troubleshooting and tactical data migrations within a PowerBuilder environment during active modernization phases.
• Mentoring engineering peers, performing code reviews, and championing best practice software development lifecycles (SDLC).

Requirements

• Practical familiarity with prompt engineering, LLM API integrations, or building user-facing applications powered by tools like Claude or OpenAI.
• A strong passion for modern web interfaces, with a proven ability to take a dated legacy UI and redesign it into a fluid, user-centric application using JavaScript, TypeScript, HTML5, and CSS.
• Full-stack software development experience featuring deep mastery of .NET Core, ASP.NET Core, C#, and relational database management using SQL Server and T-SQL.
• A clear history of sitting with non-technical business users to gather requirements and translate operational problems into structured technical specifications.
• Exposure to AI-assisted development tools, Azure/cloud ecosystems, PowerBuilder environments, or prior experience operating within judicial, legal, or public sector frameworks.

Qualifications

Commensurate with experience.

Skills

• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core
• .NET Core