Full Stack .NET/Azure Engineer (Event-Driven Architecture)

REQUISITION: Full Stack .NET/Azure Engineer (Event-Driven Architecture)Location: Dallas-Fort Worth, TX (Hybrid: 3 days/week Onsite)Duration: 6 Months + (High likelihood of extension)TECHNICAL SEARCH BLUEPRINT (TRUE 50/50 FULL STACK)1. The "True Full Stack " MandateWe are looking for a 50/50 split . The candidate must be as dangerous in Angular (RxJS/Signals) as they are in Backend Messaging Patterns . We do not want "Backend devs who can dabble in UI " or "Frontend devs who can write a basic API. "2. Critical "Must-Haves " for SubmissionDeep Angular (16+): Must demonstrate expertise in Reactive Programming (RxJS) and modern state management ( Signals ). They must understand how to optimize change detection for high-frequency data updates.Advanced Azure Messaging (Service Bus): Critical experience with Service Bus (Queues/Topics/ Subscriptions). They must understand message ordering, dead-lettering, and scaling listeners.Serverless Logic (Azure Functions): Deep knowledge of Azure Functions (Triggers, Bindings, and Durable Functions). They must be able to discuss handling "Cold Starts " and execution timeouts.Modern .NET Ecosystem: Professional experience with .NET 6/7/8 .Data Integrity (Azure SQL): Beyond CRUD. Must understand performance tuning and how the database handles concurrent writes from multiple Azure Functions.3. Submission "Green Flags "Event-Driven Mastery: Resumes that mention Idempotency or Saga Patterns in distributed systems.Performance Metrics: Specific examples of reducing cloud spend or increasing message throughput.AI/ML: Experience integrating Azure OpenAI or cognitive services into event-driven workflows.4. Immediate Red Flags (Auto-Reject)Synchronous-Only Thinking: Candidates who only build REST APIs and haven't worked with Asynchronous messaging .The "Black Box " Developer: Inability to explain why a Service Bus was used instead of a standard API call.Identity Mismatch: LinkedIn profiles that don't match the DFW location or the provided experience timeline