Bahar Hosseini

Today I revised some important backend and .NET interview topics. Thought to share the questions for anyone preparing for developer or architect roles. Here are the questions I practiced: What is the use of Startup.cs and Program.cs in .NET? What is middleware in .NET Core? What is the difference between Authentication and Authorization? How to authenticate Web API? What are HTTP verbs in Web API? How to make Web API accept only JSON? What is Dependency Injection and why we use it? How to remove duplicate rows in SQL table? Why TRUNCATE is faster than DELETE? What is ACID in SQL? How to improve performance of a stored procedure? What is the MVC life cycle in ASP.NET? If you are preparing for interviews, practicing these questions will help build confidence. Keep learning, keep sharing. #dotnet #sql #angular #backenddeveloper #interviewprep #webapi #aspnetcore

416

8 Comments

Tehnologies i found highly demanding in NZ/AUS market: - AWS/Azure (No GCP sorry) - Linux / Windows (knowing one of them from heart is must) - VMWare - Salesforce - Mulesoft - Jira - Terraform/Ansible - Splunk/Dynatrace - Microsoft SQL Server #aws #azure #microsoft #linux #windows #terraform #mulesoft #jira #terraform #splunk #dynatrace #ansible #sqlserver

9

1 Comment

🔥 ASP.NET Core Interview Q&A – Performance & Scaling Senior interviews are about real systems, not syntax 👇 Q1. How do you improve API performance? ✅ Caching, async/await, compression, minimal middleware. Q2. Difference between In-Memory & Distributed Cache? ✅ In-memory is local, distributed supports scaling. Q3. What is Response Caching? ✅ Caches responses to reduce server load. Q4. How does async/await improve scalability? ✅ Frees threads during I/O operations. Q5. How do you monitor performance in production? ✅ Application Insights, metrics, structured logs. 👉 These answers separate Senior vs Average devs. #aspnetcore #performance #scalability #dotnetinterview

41

🚀 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 .𝗡𝗘𝗧 𝗕𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗧𝗮𝘀𝗸𝘀 𝗨𝘀𝗶𝗻𝗴 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲 Building background processes in .NET? 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲 is your go-to framework for managing background jobs 𝗿𝗲𝗹𝗶𝗮𝗯𝗹𝘆, 𝘀𝗰𝗮𝗹𝗮𝗯𝗹𝘆, 𝗮𝗻𝗱 𝘄𝗶𝘁𝗵 𝘇𝗲𝗿𝗼 𝗵𝗮𝘀𝘀𝗹𝗲. 🔧 𝗪𝗵𝘆 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲? Hangfire lets you run background tasks without writing custom threading code or managing your own workers. It handles: • ✅ Job queuing • 🔁 Retries • 💥 Error handling • 💾 Persistence • 📊 Real-time monitoring 🧱 𝗧𝘆𝗽𝗲𝘀 𝗼𝗳 𝗝𝗼𝗯𝘀 𝗶𝗻 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲: 1️⃣ 𝗙𝗶𝗿𝗲-𝗮𝗻𝗱-𝗙𝗼𝗿𝗴𝗲𝘁 – Run immediately in the background 2️⃣ 𝗗𝗲𝗹𝗮𝘆𝗲𝗱 𝗝𝗼𝗯 – Scheduled to run after a delay 3️⃣ 𝗥𝗲𝗰𝘂𝗿𝗿𝗶𝗻𝗴 𝗝𝗼𝗯 – Based on CRON schedules 4️⃣ 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗮𝘁𝗶𝗼𝗻 𝗝𝗼𝗯 – Runs after another job completes 5️⃣ 𝗕𝗮𝘁𝗰𝗵 & 𝗕𝗮𝘁𝗰𝗵 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗮𝘁𝗶𝗼𝗻 – Grouped or dependent jobs 📦 𝗖𝗼𝗿𝗲 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀: • 🖥️ 𝗗𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 – Real-time job monitoring • 🛢️ 𝗦𝘁𝗼𝗿𝗮𝗴𝗲 – SQL Server, Redis, PostgreSQL • 🔁 𝗥𝗲𝘁𝗿𝗶𝗲𝘀 – Built-in error handling • ⚙️ 𝗙𝗶𝗹𝘁𝗲𝗿𝘀 – Custom job behaviors • 📡 𝗦𝗰𝗮𝗹𝗮𝗯𝗶𝗹𝗶𝘁𝘆 – Works across multiple servers 📌 𝗪𝗵𝗲𝗻 𝘁𝗼 𝗨𝘀𝗲 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲? Use it when you need: • A full-featured 🖥️ monitoring dashboard • 💾 Persistence across app restarts • 🕒 Recurring jobs (CRON-style) • 🔁 Automatic retries + error logs • 🔗 Chained or dependent jobs • 🚀 Production-ready background workers ⚖️ 𝗔𝗹𝘁𝗲𝗿𝗻𝗮𝘁𝗶𝘃𝗲𝘀 𝘁𝗼 𝗛𝗮𝗻𝗴𝗳𝗶𝗿𝗲: 🔸 𝗤𝘂𝗮𝗿𝘁𝘇.𝗡𝗘𝗧 – Powerful scheduler, CRON-friendly 🔸 𝗖𝗔𝗣 – Event-based background processing 🔸 𝗠𝗮𝘀𝘀𝗧𝗿𝗮𝗻𝘀𝗶𝘁 + 𝗥𝗮𝗯𝗯𝗶𝘁𝗠𝗤 – Distributed message queues 🔸 𝗔𝘇𝘂𝗿𝗲 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 – Serverless background jobs 🔸 𝗪𝗼𝗿𝗸𝗲𝗿 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 – Lightweight OS-level background tasks 📖 𝗥𝗲𝗮𝗱 𝘁𝗵𝗲 𝗮𝗿𝘁𝗶𝗰𝗹𝗲 👉 https://lnkd.in/dwb_vSb4 💻 𝗦𝗼𝘂𝗿𝗰𝗲 𝗖𝗼𝗱𝗲 👉 https://lnkd.in/dRnWurjt 💬 𝗪𝗵𝗮𝘁’𝘀 𝘆𝗼𝘂𝗿 𝗳𝗮𝘃𝗼𝗿𝗶𝘁𝗲 𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗷𝗼𝗯 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸 𝗶𝗻 .𝗡𝗘𝗧? 𝗟𝗲𝘁’𝘀 𝗱𝗶𝘀𝗰𝘂𝘀𝘀 👇 👉 Follow me (Kanaiya Katarmal) and hit the 🔔 on my profile so you don’t miss upcoming .NET tips and deep dives. 𝗧𝗵𝗮𝗻𝗸𝘀 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 𝗹𝗲𝘁’𝘀 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗲 𝗴𝗿𝗼𝘄𝗶𝗻𝗴 𝗮𝗻𝗱 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 .𝗡𝗘𝗧 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿! 👉 𝗦𝘂𝗯𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗼 𝗺𝘆 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿: https://lnkd.in/dp7tz_3V #𝗱𝗼𝘁𝗻𝗲𝘁 #𝗰𝘀𝗵𝗮𝗿𝗽 #𝗮𝘀𝗽𝗻𝗲𝘁𝗰𝗼𝗿𝗲 #𝗵𝗮𝗻𝗴𝗳𝗶𝗿𝗲 #𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱𝗷𝗼𝗯𝘀 #𝗴𝗶𝘁𝗵𝘂𝗯 #𝗺𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 #𝗾𝘂𝗮𝗿𝘁𝘇𝗻𝗲𝘁 #𝗰𝗮𝗽 #𝗺𝗮𝘀𝘀𝘁𝗿𝗮𝗻𝘀𝗶𝘁

318

55 Comments

🚀 Every .NET Developer Should Understand These Two Core Concepts: CTS & CLS Most developers focus on writing C# or ASP.NET Core code. But the real power of the .NET platform comes from its ability to support multiple programming languages seamlessly. That’s where CTS and CLS play an important role. 💡 What is CTS (Common Type System)? CTS defines all the data types supported in the .NET framework. It ensures that all .NET languages use the same data types and type definitions, making them compatible with each other. Examples of CTS types: ✔ int ✔ string ✔ bool ✔ class ✔ interface ✔ object This allows different languages like C#, VB.NET, and F# to share and use the same types. 💡 What is CLS (Common Language Specification)? CLS is a set of rules that .NET languages must follow to ensure compatibility with other .NET languages. It guarantees language interoperability, meaning components written in one language can work with another. In simple terms: CTS defines the types. CLS defines the rules to use those types across languages. ⚡ Real-Time Example In one project, we integrated a C# service with an existing VB.NET module. Because both languages follow CTS and CLS standards, they could communicate and share data without compatibility issues. 📌 Save this post if you're learning .NET Core fundamentals 🔁 Share it with someone preparing for .NET interviews 💬 Comment “.NET” if you want a complete roadmap to master .NET Core. 🚀 Follow Saurav Singh for practical insights on AI, React JS, .NET Core & SQL — real learning, no hype. #DotNet #DotNetCore #SoftwareEngineering #BackendDevelopment #FullStackDeveloper #Coding #Developers #TechLearning #AspNetCore

50

🚨 Sri Lankan Software Engineers: Let’s Talk About the Salary Gaslighting. I recently came across a recruiter post mocking a candidate with 4–5 years of experience for expecting a higher-than-average salary. The tone? “You're early-career.” “You're replaceable.” “Why ask for more when others work for less?” This mindset? It’s toxic. And more importantly, factually wrong. Here’s what the real market data shows: 🔹 SSE earn between 180K–300K LKR/month, with many touching 400K+ in strong companies or via remote roles. 🔹 ATL/TL/STL around 260K–850K+. 🔹 Architect level sits in the 580K–1.5m+ range. 🔹 Many engineers working with foreign clients or earning in Euros/USD often double these numbers. Even Sources like: Glassdoor, Payscale, https://lnkd.in/gc6hj3V6 and industry discussions show these data. So when someone says: “You should stay within market average.” “You’re not worth that much.” “Why are you pricing yourself out?” Think twice, do you really want to position yourself like that? Let’s be clear: ✅ Years don’t define value. Impact does. ✅ If you can lead, architect, own delivery, and communicate effectively, you're no longer an “early career.” ✅ The "market average" is just that, average. You’re allowed to aim higher. 💡 If you're an engineer: Don’t let these recruiter narratives make you feel guilty for asking your worth. Build skills. Brand yourself. Communicate your value. Know how to negotiate. You don’t need to wait 10 years to earn what you deserve. The global market is open, step into it. 💡 And to the underpaying companies & recruiters: Stop pretending this is about “realism.” It’s about keeping top talent cheap, and blaming the talent when they ask for more. PS: If you're sharp, driven, and constantly improving, you should be asking more. PSS: I no longer work in Sri Lanka, but before I moved here, after my first job, I always got above-market average salaries from my employers. This message is for cheap companies and recruiters who think they control the market and the talent. I can name a whole bunch of engineers who earn as much as, or more than, I did in Sri Lanka. Let’s raise the bar, not settle for the one set by the lowest bidder. #srilanka #software_engineers #pay_transparency #tech_careers #market_value #remote_work #know_your_worth #truth_matters #career_realities #engineering_growth #stop_underpaying #srilankatech

258

20 Comments

𝗡𝗦𝘄𝗮𝗴 𝗠𝗮𝗱𝗲 𝗦𝗶𝗺𝗽𝗹𝗲 🚀 APIs are like restaurants. 🍴 Your menu = Endpoints Your dishes = Data/Services Your customers = Other apps But how do customers know what to order? 👉 That’s where 𝗡𝗦𝘄𝗮𝗴 steps in. What is NSwag? * A tool for .NET & ASP.NET Core APIs * Creates documentation automatically * Gives you an interactive UI to test APIs * Generates client code (C#, TypeScript) so others can call your API easily Think of it as a Swiss army knife 🔪 for API developers. Books API Example 📚 Endpoints: * `GET /books` → Get all books * `GET /books/{id}` → Get book by ID * `POST /books` → Add a new book With NSwag, you get: ✔️ Swagger UI to test requests ✔️ Ready-made C# client methods like: var books = await todoClient.GetAsync(); await todoClient.CreateAsync(new Book { Title = "New Book" }); No manual HTTP coding needed. 🚀 Advantages: * Auto-generates OpenAPI/Swagger spec * Serves Swagger UI & Redoc * Produces client code (C#, TS) * Easy to customize & document Note: Use `[ProducesResponseType]` and XML comments so your API docs are always clear and accurate. 👉 Have you used NSwag before, or are you still writing HTTP requests manually? #DotNet #ASPNetCore #NSwag #WebAPI #Swagger #OpenAPI #CSharp #Developers

13

🚀 .NET / .NET Core Developer Roadmap 2025 Whether you're just getting started with .NET or aiming to level up your enterprise app development skills—this roadmap has you covered! 💡 🔹 Beginner ✔ C# Fundamentals, OOP ✔ Async/Await, LINQ ✔ Visual Studio, Git 🔹 Intermediate ✔ ASP.NET Core Web API & MVC ✔ RESTful APIs with Swagger ✔ Entity Framework Core ✔ Middleware, Filters, Dependency Injection 🔹 Advanced ✔ Clean Architecture & SOLID ✔ Caching, Logging (Serilog), Background Jobs (Hangfire) ✔ Authentication, JWT, Identity ✔ Microservices, Docker, Azure 🔹 Bonus ✔ CQRS, MediatR, SignalR, gRPC ✔ DevOps, CI/CD, API Gateways (YARP/Ocelot) ✔ Benchmarking with BenchmarkDotNet ✅ Whether you're a student, junior dev, or a seasoned professional, following a structured roadmap can accelerate your growth and make you job-market ready. #DotNet #DotNetCore #Roadmap #SoftwareDevelopment #BackendDeveloper #CSharp #Microservices #Azure #WebAPI #DevCommunity #LearningPath #LinkedInTech

34

2 Comments

👋 Understand the heart of every .NET Core app: Program.cs ❤️ Looking at Program.cs, you might think: ❓ Why is everything getting “registered”? ❓ What does AddScoped, AddControllers, or UseRouting even mean? ❓ What happens if I don’t write these lines? ❓ Who calls this file? Is this like main() in C++ or Java? 🧠 What is Program.cs? This file is the starting point of your entire application. In simple terms: 📦 It registers all the tools, services, and configurations that your app will need. ⚙️ It sets up the request pipeline, which controls how every HTTP request is handled. 🧵 It wires up the backend logic with frontend (Razor/Blazor) or API routes. In traditional languages like C/C++ or Java, we had main(). In ASP.NET Core, Program.cs is our main() ✅ ✅ What do we write here? 🔧 We register services (things our app needs to work): builder.Services.AddControllersWithViews(); // For MVC pattern builder.Services.AddDbContext<AppDbContext>(); // To connect database builder.Services.AddScoped<IUserService, UserService>(); // Custom services builder.Services.AddSwaggerGen(); // Swagger docs These lines mean: ➡ “Hey ASP.NET, I want to use MVC / connect database / use Swagger.” ➡ You must register before you can use them, or the app won’t know they exist. 🛣️ We build the HTTP request pipeline: app.UseStaticFiles(); // To serve images, CSS, JS app.UseRouting(); // Enables URL routing app.UseAuthentication(); // Checks if user is logged in app.UseAuthorization(); // Checks what user can access app.MapControllers(); // Maps controller endpoints This part says: “When a user sends a request, handle it like this → then → then → and finally reach a controller.” 🤔 Common Questions — Answered! Q: What does "AddScoped" mean? 🔸 It registers a service (like UserService) with a specific lifetime. 🔸 Scoped means: a new instance is created per request. Q: Why do I need to register services manually? 🔹 Because ASP.NET Core follows Dependency Injection (DI) 🔹 DI allows your code to ask for dependencies instead of creating them manually — keeping things clean, testable, and modular. Q: What if I don’t register a service or middleware? ❌ Your app will either crash, throw an error, or not behave as expected. Q: What’s the difference between Services and Middleware? ✅ Services (via builder.Services) = things you need in your logic (e.g., database, custom services) ✅ Middleware (via app.UseX) = steps for processing every request (e.g., routing, auth) 💡 Final Takeaway If something isn't working in your app — ask yourself: 🔍 “Did I register it in Program.cs?”

31

1 Comment

🚀 .NET Developer Interview Scenarios - Part 2 🚀 Preparing for a .NET Developer interview? Check out Part 2 of our series with scenario-based questions for Intermediate and Junior-level roles. Get ready for real-world challenges on debugging, database connections, and performance optimization. #DotNetDevelopers #CodingInterviews #JuniorDev #IntermediateDev #DotNetCore #TechJobs #SoftwareDevelopment #DeveloperLife #InterviewPrep #TechTalent #ProgrammingChallenges

160

6 Comments

Stop Applying for .NET Jobs. Start Being Found. 🎯 Are you tired of the "spray and pray" approach to job applications? For .NET developers, the real career trap isn't a lack of skills—it's a lack of visibility 🔍. You could be a top-tier .NET architect, but if you're only visible to your immediate network, you're missing out on the best opportunities. Many high-quality roles are filled through targeted platforms before they even hit the public job boards. So, how do you break out and get noticed by the right companies? The answer is to engage in specialized, niche communities where your specific expertise is valued. This is why platforms built by and for .NET developers are so powerful. I want to highlight StackedNet.com—a job portal dedicated exclusively to the .NET ecosystem. Here’s what makes it a game-changer: · 🎯 Niche Focus: It’s built specifically for .NET developers, C# specialists, and related tech stacks. This means the roles are curated and relevant. · 📈 Actionable Market Insights: They don't just list jobs; they analyze hiring trends. For example, their research reveals the top 5 skills gaps in the .NET job market, like Cloud Deployment (Azure/AWS) and Architecture Patterns, giving you a clear roadmap to stand out. · 💡 Community & Content: Get ahead with content that matters, from mastering the "unsexy fundamentals" to navigating senior-level architecture interviews. If you're serious about advancing your .NET career, it's time to get on the right radar. 👉 Explore 300+ curated .NET roles and increase your visibility: StackedNet.com Question for the community: What's your #1 strategy for staying visible and relevant in the fast-evolving .NET landscape? Share your tips in the comments below! 👇 #DotNet #CSharp #SoftwareDevelopment #TechCareers #CareerGrowth #JobSearch #NETCore #Azure

61

7 Comments

🚀 𝗖𝗼𝗿𝗮𝘃𝗲𝗹. Simple Background Jobs and Scheduling in .NET If you’ve ever needed scheduling, background jobs, or caching in a .NET app, you know it can get heavy quickly. That’s where 𝗖𝗼𝗿𝗮𝘃𝗲𝗹 shines. It’s a lightweight library designed to handle common application needs with almost zero configuration. 🧩 𝗪𝗵𝗮𝘁 𝗖𝗼𝗿𝗮𝘃𝗲𝗹 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝘀 ▪ Task scheduling ▪ In-memory queuing ▪ Caching ▪ Mailing with Razor templates ▪ And more All without the usual boilerplate. ⏰ 𝗖𝗹𝗲𝗮𝗻 𝗧𝗮𝘀𝗸 𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗶𝗻𝗴 You can define schedules directly in 𝗣𝗿𝗼𝗴𝗿𝗮𝗺.𝗰𝘀 or implement 𝗜𝗜𝗻𝘃𝗼𝗰𝗮𝗯𝗹𝗲 to encapsulate job logic inside a clean, reusable class. One particularly useful feature is 𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗲𝗪𝗶𝘁𝗵𝗣𝗮𝗿𝗮𝗺𝘀. It allows you to pass different parameters to the same invocable, which keeps your scheduling logic flexible without duplicating code. 📦 𝗤𝘂𝗲𝘂𝗶𝗻𝗴 𝗠𝗮𝗱𝗲 𝗘𝗮𝘀𝘆 Coravel’s queue runs in memory with zero configuration. Perfect for lightweight background processing without external dependencies. ✉️ 𝗦𝗶𝗺𝗽𝗹𝗲 𝗠𝗮𝗶𝗹𝗶𝗻𝗴 𝗔𝗣𝗜 It also provides a clean mailing API with Razor template support. No need to wire up complex infrastructure for basic email scenarios. 🔑 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆 Coravel is intuitive, minimal, and practical. If you want scheduling and background processing without bringing in a heavyweight framework, it’s worth exploring. ♻️ If you find this useful, repost and spread the knowledge. 🔔 Follow Hiteshkumar for more practical .NET insights.

39

3 Comments

Deploy .NET Web API to public hosting for FREE 🌍 I’ll show you how to deploy your .NET Web API directly from Visual Studio — all the way to public hosting for FREE, with a connected MSSQL database 💾 You’ll learn how to: ✅ Publish your .NET Web API straight from Visual Studio ✅ Set up and connect your SQL Server database ✅ Host your backend online — no paid plans or complex CI/CD needed ✅ Make your API fully accessible on the internet 🌍 If you’ve ever wanted to share your .NET project live or test it in a real hosting environment, this guide walks you through every step.

19