Senior .NET/Blazor Engineer for Ongoing Support

@augurstech

A Warm Hello! We are readily available to start working on this project! I have read your job posting and glad to mention that we specializes in supporting and hardening complex .NET applications in production environments. We have senior engineers with extensive experience across Blazor, ASP.NET Core, PostgreSQL, cloud-hosted SaaS platforms, payment integrations, video processing pipelines, and third-party API ecosystems. We would welcome the opportunity to discuss PostZam's architecture and show how our senior engineers can help strengthen the platform as you scale publicly. Best regards, Ana

@Microlent

What stood out to me in your description is that you're not looking for feature development—you are looking for someone who can diagnose, prove, and harden a production system. Our team has extensive experience with .NET, Blazor, PostgreSQL, API integrations, SaaS platforms, and AI-powered applications. We regularly work with complex third-party integrations where reliability, observability, retry strategies, and failure isolation are just as important as the business logic itself. The API resilience challenges you described—token refresh flows, quota management, rate limiting, webhook handling, retry/backoff strategies, AI service instability, and graceful degradation are exactly the areas where production systems either become reliable or become support nightmares. One example involved a SaaS workflow platform where intermittent failures initially appeared to be application bugs. Root-cause analysis revealed a combination of third-party API throttling and retry collisions creating duplicate processing events.. I am comfortable participating in the paid trial task and reviewing an existing production issue with your findings. I appreciate teams that prioritize evidence, reproducibility, and measurable outcomes over assumptions. Hourly Rate: $15/hr Looking forward to discussing the architecture and trial task. Best regards, Rajesh Microlent Systems

@ZohaibRoy

⭐⭐⭐⭐⭐ Senior .NET/Blazor Engineer for Advanced API Integration ❇️ Hi My Friend, I hope you're doing well. I've reviewed your project requirements and see you're looking for a Senior .NET/Blazor Engineer with API integration skills. Look no further; Zohaib is here to help you! My team has successfully completed 50+ similar projects in this area. I will tackle your project by diagnosing production bugs and ensuring robust API integration while maintaining system resilience. ➡️ Why Me? I can efficiently handle your Senior .NET/Blazor Engineer role as I have over 7 years of experience in .NET and Blazor, focusing on API integration and debugging. My skills include diagnosing issues from logs, ensuring smooth API operations, and maintaining high-quality code. Additionally, I have a strong grip on PostgreSQL, PWA lifecycles, and Git fluency. ➡️ Let's have a quick chat to discuss your project in detail and let me show you examples of my previous work. I look forward to connecting with you! ➡️ Skills & Experience: ✅ .NET Development ✅ Blazor (Server/WebAssembly) ✅ API Integration ✅ Production Debugging ✅ PostgreSQL ✅ PWA Implementation ✅ Git Version Control ✅ Resilience Engineering ✅ Transactional Email Setup ✅ Front-end Behavior Handling ✅ OAuth and Token Management ✅ Error Handling Waiting for your response! Best Regards, Zohaib

@shaktistanwar

As a Senior Software Architect & Full‑Stack Developer with 15+ years of experience, I specialize in transforming ideas into robust, scalable products. My expertise in .NET, .NET Core, and Blazor aligns closely with your project needs, backed by a proven record of diagnosing and resolving production issues while delivering clean, maintainable code. I’ve led large‑scale projects from secure API development for insurance firms to high‑performance web apps for financial institutions. This background enables me to address root causes proactively rather than applying temporary fixes — a critical trait for ongoing support. My experience spans deep API integrations (OAuth lifecycles, rate limits, failure isolation) and AI APIs like Google Gemini multimodal, including handling challenges such as capacity errors and model migrations. Additionally, I bring strong knowledge of PWAs, REST API resilience patterns (retry/backoff, circuit breakers), and Git workflows with proper conflict resolution. My availability during Eastern hours ensures smooth collaboration across time zones. Together, we can build a resilient, future‑ready solution that meets your technical and business goals. I look forward to partnering with you to turn your vision into reality.

@diektech

Hi, This is Elias from Miami. I checked the details and understand you're not looking for feature development as much as someone who can diagnose, verify, and resolve production issues in a live SaaS environment. The focus on evidence-based debugging, root-cause analysis, and validating fixes before closing issues aligns with how I typically approach support work. The real challenge in systems like PostZam is rarely the visible bug. It's usually the interaction between distributed services, third-party APIs, async processing, browser behavior, and deployment state. Patching symptoms often creates a second issue a few weeks later, which is why I prefer reproducing problems from logs, payloads, and user flows before touching code. I've worked on production SaaS platforms involving .NET, API integrations, payment processing, background jobs, PostgreSQL, and cloud-hosted multi-service architectures where reliability mattered more than feature velocity. I have a few questions to get a better understanding: Q1 – Are application logs currently centralized (Serilog, Seq, ELK, etc.), or spread across individual servers? Q2 – Is the paid trial task isolated to a single repository, or does it involve coordination across multiple services? Q3 – What level of weekly hour commitment are you expecting once the trial period is complete? I'd be happy to discuss the details and suggest the best approach for implementation. Looking forward to hearing from you.

@techplusintl

Hi there, ★★★ .NET / Blazor Expert ★★★ 5+ Years of Experience ★★★ I can diagnose and resolve production bugs with thorough testing and evidence. This will include: - Diagnosing Blazor front-end and backend issues. - Reviewing code commits for correctness and best practices. - Building resilience around external APIs to prevent user impact. - Verifying fixes with logs and artifacts. I will approach this by analyzing logs, reproducing issues, and implementing fixes while ensuring proper documentation and testing. Ready to start once you provide access to the system and any specific bugs to address. Thanks!

@seefattechnologi

Certainly--------------I believe I will satisfied you by completing this task with high Quality and Accuracy I am highly proficient to work on this project . I am an CREATIVE/Multitalented .NET/AZURE/BLAZOR/Full stack developer having rich experience with all the latest technologies with so many successful Tasks. I have some queries to give you accurate time . Please ping me to get started and provide you great results. Thanks!!!

@tangramua

Dear ,   We carefully studied the description of your project and we can confirm that we understand your needs and are also interested in your project. Our team has the necessary resources to start your project as soon as possible and complete it in a very short time.   We are 25 years in this business and our technical specialists have strong experience in Python, .NET, C# Programming, Debugging, Node.js, PostgreSQL, Git, .NET Core, .NET 5.0/6, Blazor and other technologies relevant to your project.   Please, review our profile https://www.freelancer.com/u/tangramua where you can find detailed information about our company, our portfolio, and the client's recent reviews.   Please contact us via Freelancer Chat to discuss your project in details.    Best regards, Sales department Tangram Canada Inc.     

@skalogir

Hi, I understand PostZam needs a senior .NET/Blazor engineer for ongoing production support, deep social/AI API integration hardening, OAuth/token lifecycle issues, retry/backoff, circuit breakers, PWA behavior, PostgreSQL debugging, and evidence-based root-cause fixes. I have experience with production .NET/Blazor systems, multi-platform API integrations, OAuth refresh flows, webhook/status handling, Gemini/OpenAI-style AI APIs, PostgreSQL, PWA lifecycle issues, Git review, and resilient external-service architecture. I can start with the paid trial task, reproduce the bug, fix the root cause, prove it with logs/payloads/screen evidence and commit hash, then continue supporting production with clear overlap to U.S. Eastern hours. Q1: Is PostZam running Blazor Server, WebAssembly, or a hybrid model? Q2: Which integration is currently causing the most production failures? Q3: What weekly hour range do you expect for ongoing support? Best regards.

@mubeenm5026

With over 7 years of experience in the .NET ecosystem, including strong Blazor proficiency, I am well-equipped to handle the ongoing production support and bug resolution needs of PostZam. The combination of these skills has allowed me to develop a deep understanding of the Blazor framework while maintaining a versatile approach in handling backend technologies such as Node.js and Python. In my time as a developer, I have honed my abilities in diagnosing and fixing production bugs extensively. My approach entails precisely identifying the root cause through thorough log analysis and payload examination before diving into the fix. Crucially, I always ensure that the resolution is validated end-to-end with concrete evidence such as logs, payloads, screen recordings, and commit hashes. As an international software development company, Web Crest values transparent communication, agile project management, and security-focused development - all integral facets for ensuring a smooth workflow like you've envisioned for this role. From my perspective, "done" signifies passing rigorous tests on your specific machines with complete commit hashes; a mindset that resonates well with your approach. I'm geared up for the challenge at hand and ready to prove myself in the one paid trial task you require to initiate the project. Let's get started!

@topcreator100

Hello, I’ve read your production-critical Blazor and .NET stack and I’m confident I can own root cause diagnosis for PostZam. I’ll start by instrumenting end-to-end traces, correlating logs, payload snapshots, and commit history to reproduce issues before deploying fixes. From there I will harden external calls with robust retry patterns, circuit breakers, and precise model fallbacks, while keeping PWAs, REST endpoints, and PostgreSQL interactions under tight control. My background includes working with Node.js services alongside .NET 5.0/6 and Git workflows to ensure clean merges, clear diffs, and verifiable evidence for every change. Best regards, Freelancer

@PINESCRIPTERR

Hi, Thank you for the detailed brief. We've reviewed the requirements and have a clear understanding of the objective: providing ongoing senior-level production support for PostZam, diagnosing and fixing real bugs across the full Blazor and .NET 10 stack, reviewing commits from the existing team, and hardening API integrations so upstream failures never reach paying customers. We particularly appreciate the evidence-based standard. In our view, the most important part of this engagement is the diagnosis discipline, since a fix that cannot be proven with logs, payloads, and a commit hash is not a fix at all, and that philosophy is exactly how we approach production issues. Based on the information provided, we can cover full-stack bug diagnosis and resolution across Blazor frontend and backend services, PWA behavior and service worker issues, third-party API resilience with retry and backoff patterns, commit and merge review with proper git hygiene, transactional email trigger verification, and PostgreSQL query analysis, all documented with artifacts before closing any issue. Kind regards, Houssame

@sakib51

Hello, I’m a .NET engineer with 7+ years of experience building and debugging production systems using Blazor (Server/WASM), WebAPI, and media-heavy backend workflows. I’ve worked on WebAPI systems integrated with crypto and stock market data feeds, focusing on reliability, latency handling, and resilient third-party API integration (rate limits, retries, partial failures, and timeouts). I also have experience with video playback integration and media workflows, including handling client-side playback issues, streaming edge cases, and app integration scenarios. I’m familiar with FFmpeg-based processing pipelines with conversion, HLS or smooth streaming media playback etc. Core strengths: Production debugging using logs, payloads, and reproduction-first approach WebAPI design with retry/backoff, idempotency, and failure isolation External API integration under unstable conditions (AI/third-party services included) Media processing pipelines (FFmpeg workflows, async job systems) Git hygiene and merge conflict resolution in team environments I work in systems where: external APIs fail unpredictably (AI / social / data providers) failures must be isolated per service “done” means verifiable with logs and commit evidence

@quan9824

Hi, I’m interested in supporting PostZam as a senior .NET/Blazor engineer focused on production debugging, bug resolution, code review, and system hardening. I have strong experience with .NET, Blazor, PostgreSQL, REST API integrations, production troubleshooting, Git workflows, and deployment environments. My approach is root-cause focused: reproduce the issue, inspect logs/payloads, isolate the failure path, fix the underlying problem, and provide evidence through commit hashes, screenshots/logs, and test results. A relevant example: I previously investigated a production automation issue that looked like a frontend state bug, but the root cause was an async backend retry path creating inconsistent status records. I traced logs and payloads, reproduced the failure, fixed the state transition logic, added safer error handling, and verified the fix with before/after test evidence. I’m comfortable with a paid trial task and your definition of “done”: the fix must pass on your environment with commit hash and proof attached. I can overlap with U.S. Eastern hours and provide direct, evidence-based updates.

@SJMDEVELOPER

Hi, I've spent 14+ years building and supporting enterprise SaaS platforms using .NET, Blazor, ASP.NET, PostgreSQL, and complex third-party integrations. What stands out in your requirement isn't just Blazor—it's production reliability. I've worked on systems involving payment gateways, AI services, logistics platforms, and business-critical APIs where root-cause analysis, resilience, and fault isolation were essential. A recent issue that appeared to be an API failure was ultimately traced to a background-processing race condition. By reproducing it, analyzing logs and payloads, and validating the fix end-to-end, we resolved the problem permanently rather than patching symptoms. I'm comfortable working within U.S. Eastern business hours and can start immediately. Let's connect for the technical walkthrough and paid trial task. Manoj Kumar .NET | Blazor | PostgreSQL | API Integrations | SaaS Platforms

@yuliussmayoru

OVER 10 YEARS OF EXPERIENCE IN IT, HIGH QUALITY DELIVERY Hello! The part that stands out here is your standard for “done”, because production Blazor support really does require root cause, proof, logs, commit hashes, and working behavior on the client machine, not just a quick patch that looks fine locally. I can help with ongoing production debugging across Blazor, .NET services, PostgreSQL, PWA behavior, DigitalOcean deployment, transactional email, payments, FFmpeg processing, and social platform API integrations. My approach is to reproduce the issue first, inspect logs and payloads, identify the actual failure path, make the smallest reliable fix, then prove it with test results, screenshots or screen recording, and the exact commit hash. I have handled difficult production bugs involving async API failures, stale frontend state, broken event flows, background job timing, third party timeout handling, and environment config mismatches. For external APIs like Gemini, YouTube, Meta, TikTok, LinkedIn, and X, I would harden retry, backoff, fallback, timeout, and user safe error handling so upstream failures do not leak into the product experience. I am comfortable with a paid trial task and ongoing overlap with U.S. Eastern hours. Warm regards, Yulius Mayoru

@mykhaylob4

✋ Hi there. I can provide ongoing production support for your .NET and Blazor SaaS, focusing on root cause analysis, bug resolution, code review, and platform stability rather than temporary fixes. ✔️ I have solid experience working with .NET, Blazor, PostgreSQL, REST APIs, PWAs, third party integrations, and production troubleshooting. In a recent project, I investigated an intermittent issue that appeared to be an API timeout problem but was actually caused by a race condition between background jobs and cached state, which I reproduced, traced through logs, fixed, and validated with test evidence. ✔️ For your project, I will approach every issue through logs, payload analysis, reproduction, debugging, validation, and documented proof. I am comfortable reviewing commits, resolving merge conflicts properly, improving API resilience, diagnosing PWA behavior, and hardening integrations with external services. ✔️ I will provide clear technical updates backed by evidence, test results, and commit references. I am also comfortable with paid trial tasks and working closely with existing developers to improve reliability across the platform. Let’s chat to discuss your project in more detail. Best regards, Mykhaylo

@mobimubasir

Hello there, I can help with production-level .NET/Blazor debugging, API integration hardening, OAuth/token lifecycle issues, retry/backoff, circuit breakers, and root-cause fixes backed by logs, payloads, commits, and test evidence. I’ve worked with complex backend/API workflows and would approach your trial task by reproducing the issue first, tracing it through logs and external API behavior, then delivering a clean fix with a clear root-cause explanation and verification steps.

@SachinBhatt

Have 20+ years of experience developing large scale .NET applications including ASP.NET, API and Blazor.