- How are .NET developers vetted?
- Four gates: (1) 60-minute technical screen on modern .NET (C# 12, .NET 8/9, async/await internals, EF Core, dependency injection) plus one legacy topic (.NET Framework interop, WCF or ASMX migration, SQL Server internals); (2) live coding round on a real API design or data-access problem; (3) system-design round on a distributed enterprise system (auth, transactions, event flow, background jobs); (4) two reference calls with engineering managers from the last 24 months. Under 8% clear all four.
- Do you offer contract-to-hire?
- Yes. Three-month embedded contract, then a fixed 20%-of-annualized-base conversion fee if the engineer accepts a full-time offer inside 12 months. No conversion fee after month twelve. Engineers are never restricted from taking direct offers — the fee reflects sourcing and vetting cost.
- What's the rate structure?
- Senior .NET developers: $135–$180/hr. Staff-level with financial-services or FIX-protocol background: $170–$220/hr. Monthly retainers at 10–15% discount for 6+ month commitments. All-in — no recruiting fee, no benefits markup, no on-site per-diem for NYC office days.
- Are engineers actually onshore?
- Yes. Every engineer is US-based, in Eastern or Central time, and W-2 with NextGen or a long-term US contractor with signed NDA and IP assignment. .NET talent in particular skews toward NYC, NJ, Charlotte, Chicago, and Boston — cities where enterprise financial services has historically hired heavily. No offshore subcontracting, no rotating pools. Written into the engagement contract.
- What seniority level should we expect?
- The typical placed engineer has 10–15 years of .NET experience — usually a mix of legacy Framework (4.6.x, WCF, WebForms/MVC) and modern .NET 6/7/8/9. Common prior contexts: bulge-bracket banks, insurance carriers, exchange and clearinghouse platforms, and regulated healthcare payers. Deep judgment on migrations, transactional correctness, and Windows-shop operational realities — not just C# syntax.