Role purpose:To design, develop, and maintain enterprise integration solutions across cloud and on-prem environments using . NET Core and Azure API Management (APIM). The role ensures reliable, secure, and efficient system integrations by building APIs, orchestrating workflows, and optimizing data exchange across enterprise applications.
Key responsibilities:1) Broker/Trading Domain Integration Experience (CFD or Crypto-specific) Proven delivery integrating broker core systems end-to-end (not just “APIs” in general): trading platform (e.g., MT5), CRM/Back Office, KYC/AML, payments/PSPs, liquidity/bridge, and market data. Experience with trading-domain concepts: orders, positions, deals, margins, swaps, leverage, symbol settings, trading sessions, hedging vs netting, and client lifecycle (lead → KYC → funding → trading → withdrawals). Comfortable aligning integrations to operational flows: onboarding, deposits/withdrawals, rebates/IB, risk controls, reporting. 2) Integration Architecture & Middleware Build-from-Zero (Enterprise-grade) Led the design and build of an integration platform/middleware (not only consuming APIs), including:API Gateway patterns (versioning, throttling, auth, rate limits) Event-driven architecture and messaging (e.g., Kafka/Rabbit MQ/Azure Service Bus) Canonical data model and mapping strategy between systems Orchestration vs choreography decisions Idempotency, retries, sagas/compensation, and failure handling Capable of defining the integration operating model: standards, patterns, documentation, governance, and SDLC for integrations. 3) Security, Compliance, and Auditability in a Regulated Environment Demonstrated capability implementing security controls appropriate for a broker:OAuth2/OIDC, mutual TLS, secrets management, token lifecycle PII protection, encryption in transit/at rest, key management Audit trails (who did what/when), immutable logs where needed Secure API design: input validation, anti-replay, least privilege Experience aligning with financial services compliance expectations: traceability, controlled access, change management, evidence-ready documentation. 4) Reliability Engineering: Observability, Performance, and Resilience Has delivered integrations that run 24/7 with measurable SLAs:Monitoring/alerting, distributed tracing, structured logging Queue backlogs, dead-letter handling, reprocessing mechanisms Performance tuning (throughput/latency), load testing approach HA/DR thinking (active-active vs active-passive), RTO/RPO awareness Strong “production ownership” mindset: incident response, runbooks, on-call readiness, postmortems. 5) . NET Leadership Depth + Delivery Management (People, Vendors, and Roadmap) What to look for Deep practical . NET integration stack leadership:. NET (Core/6/7/8), Web APIs, background workers, messaging, EF where relevant CI/CD, IaC basics, environment strategy (Dev/UAT/Prod), release governance Can manage and scale delivery:Hiring/building an integration squad, vendor management, prioritization Converting business objectives into an integration roadmap and backlog Stakeholder management across trading, compliance, operations, finance
Required qualifications & experience:• Bachelor’s degree in computer science, Computer Engineering, or related field.• Minimum of 7 years of experience in middleware development and system integration• Hands-on expertise in . NET Core and Azure API Management for API gateway, security, and lifecycle management.• Proven experience designing and securing RESTful APIs, including APIM policy configuration• Strong SQL Server/Azure SQL skills — including query optimization and stored procedure design• Familiarity with enterprise architecture principles and integration best practices.• Experience with Azure App Service, Application Insights, and Log Analytics for API hosting and monitoring.