.NET Architect
Description
- 10+ years of backend development, including several years in a senior or architect-level role where you still wrote code daily.
- Strong C++ on Windows: MFC and/or ATL, Windows services, multi-threading, memory management, COM/DCOM.
- Strong C# / .NET, including .NET Framework-era technology (WCF, COM interop, Windows services).
- Deep Microsoft SQL Server expertise:
- Complex stored procedures, functions, views and triggers
- Query optimization, indexing and partitioning
- Transactions, isolation levels, concurrency and deadlock analysis
- Performance tuning on large, high-volume databases
- Proven production debugging. Youve root-caused real incidents in live systems, including with crash dumps and SQL diagnostics.
- Experience with message-based or asynchronous architectures (MSMQ, Kafka or similar).
- Experience with financial or transactional systems where correctness, consistency and auditability are critical.
- Comfort with Visual Studio, MSBuild, Git, and CI/CD (Azure DevOps/TFS, Jenkins or similar).
- Solid acquiring knowledge. You understand the acquirer side of card payments well enough to design for it:
- The four-party model (merchant, acquirer, card scheme, issuer) and the acquirer’s role and liabilities
- The transaction lifecycle: authorization, capture, clearing, settlement and merchant funding, plus reversals, refunds and offline transactions
- Interchange, scheme fees and merchant pricing models (blended vs. interchange++)
- Chargebacks, disputes and reconciliation
- Acquirer-side data required by the schemes (for example MCC, merchant name and country, acquirer BIN / ICA)
Need to know
- Payment protocols and scheme formats: ISO 8583, GICC, ZVT, EMV, girocard, Visa / Mastercard clearing formats (for example Base II, IPM), 3-D Secure.
- Hands-on experience with an acquiring or merchant-processing platform, payment facilitator (sub-merchant) models, or acquirer migrations.
- Payment security: HSM, PIN and MAC, DUKPT, ZKA, PCI DSS.
- SEPA, EBICS, camt or other banking and settlement file formats.
- SQL Server replication, SQL Agent or SQL CLR.
- Experience with 32-bit 64-bit migration of native code, or rehosting a Windows estate on AWS (EC2, FSx).
- Java 21 / Spring Boot and Kafka.
- Experience with regulated environments (BaFin, ZAIT, banking).
- German language skills, since parts of the code, database and documentation are in German. This is a strong plus.