Aman K.
Senior .NET Full Stack Developer | ASP.NET Core, SaaS, AI Integration
๐ณ+ ๐๐ฒ๐ฎ๐ฟ๐ ๐ถ๐ป .๐ก๐๐ง ๐ณ๐๐น๐น ๐๐๐ฎ๐ฐ๐ธ ๐ฑ๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐บ๐ฒ๐ป๐, ๐ฏ+ ๐๐ฒ๐ฎ๐ฟ๐ ๐น๐ฒ๐ฎ๐ฑ๐ถ๐ป๐ด ๐๐ฒ๐ฎ๐บ๐ ๐ผ๐ณ ๐ฐ-๐ด ๐ฑ๐ฒ๐๐ฒ๐น๐ผ๐ฝ๐ฒ๐ฟ๐. ๐ ๐๐น๐๐ถ-๐๐ฒ๐ป๐ฎ๐ป๐ ๐ฆ๐ฎ๐ฎ๐ฆ ๐ฝ๐น๐ฎ๐๐ณ๐ผ๐ฟ๐บ๐, ๐น๐ฒ๐ด๐ฎ๐ฐ๐ ๐บ๐ผ๐ฑ๐ฒ๐ฟ๐ป๐ถ๐๐ฎ๐๐ถ๐ผ๐ป, ๐ฎ๐ป๐ฑ ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐๐ถ๐ผ๐ป ๐๐ ๐ถ๐ป๐๐ถ๐ฑ๐ฒ ๐ฒ๐ ๐ถ๐๐๐ถ๐ป๐ด ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐๐. ๐ง๐ผ๐ฝ ๐ฅ๐ฎ๐๐ฒ๐ฑ, ๐ญ๐ฌ๐ฌ% ๐๐ผ๐ฏ ๐ฆ๐๐ฐ๐ฐ๐ฒ๐๐, ๐๐น๐ฎ๐๐ฑ๐ฒ ๐ฃ๐น๐ฎ๐๐ณ๐ผ๐ฟ๐บ ๐ญ๐ฌ๐ญ ๐ฐ๐ฒ๐ฟ๐๐ถ๐ณ๐ถ๐ฒ๐ฑ. Your software should be able to say yes to "can we add one more thing?" That's what I build for. Most of my work comes down to making systems that can change without breaking. Building a multi-tenant SaaS platform properly from the start. Making a codebase that's become hard to modify modular again. Adding features to a mature system without disturbing what already works. Or putting AI into a product that already exists, without turning the rest of it into an experiment. My main backend stack is .NET and C#, with Node.js alongside it. Frontend is Angular, React or Next.js, on Azure or AWS. I've also picked up Python and Go when a client's microservices needed it, because "that's not my stack" isn't a useful answer to someone with a problem. Your requirements will change, and you shouldn't have to pay twice for that. This is why I care about SOLID, design patterns and modularity, not because they look good on architecture diagrams. On an enterprise AI product, keeping model providers behind a clear abstraction meant switching between Claude and OpenAI stayed localised instead of spreading provider-specific code through the application. On a multi-tenant insurance platform, Clean Architecture kept the domain and application layers independent of the database underneath them. If your system is past the easy CRUD stage, that's where I'm most useful. Multi-tenant architecture, complex business workflows, third-party integrations, background processing, authentication and RBAC, or an application that needs to evolve rather than be rewritten. With AI, the hard part isn't the model, it's everything around it. I've built RAG systems, document processing and structured extraction inside SaaS products that already existed. I use these tools daily in development too, which is how I know where they get dangerous. So I work in testable phases and watch authorisation, tenant isolation, data integrity and concurrency closely, because that's where code compiles perfectly and is still completely wrong. You'll also get honest answers. If an approach is unnecessarily complicated or risky, I'll tell you and explain why. Useful feedback now beats a comfortable answer followed by a production issue three weeks later. If you're building a SaaS product, adding AI to an existing one, or modernising something that's become hard to change, send me a message and tell me what you're working on. Stack I work in regularly: C#, .NET Framework, ASP.NET, ASP.NET MVC, ASP.NET Core, .NET Core, Entity Framework, Node.js, NestJS, Angular, React, Next.js, TypeScript, JavaScript, SQL, SQL Server, PostgreSQL, MongoDB, Microsoft Azure, Azure Service Bus, AWS, Docker, CI/CD, Azure DevOps, Keycloak, Okta, Stripe, RabbitMQ, WebSockets, SignalR, Claude API, OpenAI, RAG, LangChain, Supabase, multi-tenant SaaS, microservices, Clean Architecture, CQRS, REST APIs. Claude Platform 101 certified.