Sr. Backend Engineer (.NET Core)

About Data Society Group
At Data Society Group, we provide the highest quality, leading-edge, industry-tailored data and AI training and solutions for Fortune 1,000 companies and federal, state, and local governmental organizations. We partner with our clients to educate, equip, and empower their workforces with the skills they need to achieve their goals and expand their impact. Our portfolio of brands and services sits at the intersection of people, data, and AI and consists of:

• CDO Magazine, the trusted voice of global data and AI leadership
• The Data Lodge, a pioneer in data literacy and cultural transformation
• Data Society, delivering applied AI education and custom-built solutions
• InspiredMinds!, a convening force behind the world’s most inclusive AI community

We are working to empower the workforces of the future; if you’re as passionate about transforming workplaces with the power of Data & AI as we are, we’d love to hear from you!

About the Role
The onshore Senior Back-End Engineer leads .NET Core microservices architecture and backend build quality for the platform, directing a pod of offshore back-end engineers while remaining hands-on in service design, API contract ownership, and CI/CD pipeline governance. In this role, you will serve as the technical authority on all backend decisions, from Azure SQL cache schema design through write-path logic, Azure Service Bus patterns, and security compliance. You will work closely with the onshore Solution Architect, Integration Lead, and Sr. Front-End Engineer to ensure the backend layer is production-ready and validated every sprint.

This role is work-from-home (remote) though must be able to commute to client offices in Falls Church, VA as needed (estimated every 2 weeks). This is a full-time W2 employment position with benefits. Please note that this role is tied to a client contract and is structured as an initial 9-month position. Opportunities for extension or long-term placement are highly likely based on client renewal and project performance.

Responsibilities
As the Senior Back-End Engineer, you will set architectural standards, oversee service layer quality, and guide offshore engineering efforts. Your core responsibilities include:

• Architecture & Leadership: Lead .NET Core microservices architecture, defining service boundaries, API contract standards, and write-path design patterns across all functional areas. Direct and oversee a pod of offshore back-end engineers by assigning work, conducting code reviews, and ensuring production-ready output.
• Database & API Layer Design: Design and own the Azure SQL transactional cache schema. Design and implement REST API endpoints exposed through Azure API Management (APIM), consumed by the React frontend.
• Integration & Business Logic: Implement write-path logic that routes commit actions (budget approvals, PO releases, change orders) through Azure Service Bus to OIC flows and back to the ERP. Enforce business logic, data validation, and error handling standards within the service layer.
• Pipeline Compliance & Security: Own CI/CD pipeline compliance for backend code, ensuring all commits pass Veracode SAST + SCA security scanning before merging.
• Demos & Client Handoff: Lead bi-weekly sprint demos for backend workstreams, ensuring all service layer work is demo-ready on schedule. Resolve and triage backend defects during SIT, UAT, and post-launch hypercare within agreed SLA windows. Conduct knowledge transfer to the client team ahead of the support handoff.

Required Skills & Experience

• 6–8 years of back-end development experience, with at least 4 years focused in .NET Core / C#.
• Demonstrable experience leading or directing offshore back-end engineering teams.
• Strong experience designing and building REST APIs exposed through an API gateway (Azure APIM preferred).
• Proficiency with Azure SQL, schema design, query optimization, and working with a delta-refreshed transactional cache pattern.
• Experience with Azure Service Bus or similar async messaging infrastructure, including retry logic, dead-letter handling, and error queues.
• Solid understanding of microservices architecture and separation of concern