Senior Backend Engineer

We need solid Python Backend engineer , Fast API, and Azure for this roe and other must have.

Senior Backend Engineer

Location : Austin Texas Hyrbid

Interview : Video Interview

ROLE MANDATE

Build the backend services, APIs and orchestration layer behind the Sales Command Center. The role sits between the web/iOS experiences and Dynamics 365, creating reusable services that combine CRM information with data and workflows from other enterprise platforms.

KEY RESPONSIBILITIES

* Design and develop backend services using Python and FastAPI.

* Build BFFs, domain APIs and reusable business services supporting the Sales Command Center.

* Implement secure integration with Microsoft Dynamics 365 / Dataverse.

* Build orchestration services combining CRM data, documents, customer context, sales workflows and other enterprise systems.

* Implement REST APIs, asynchronous workflows and event-driven integration patterns.

* Build Dynamics adapter / anti-corruption layers so UI and domain services do not become tightly coupled to CRM schemas.

* Implement authentication, authorization, idempotency, retries, timeouts, circuit breakers, rate limits, caching and canonical error handling.

* Develop read models and caching patterns where high-volume requests should not directly hit Dynamics.

* Use Azure API Management, Service Bus / Event Grid, Key Vault and Azure Monitor / Application Insights.

* Write unit, integration and contract tests and contribute to CI/CD quality gates.

* Troubleshoot production and integration issues across UI, APIs, backend services and Dynamics.

REQUIRED SKILLS

* Python

* FastAPI

* REST APIs and microservices

* Azure application development

* Azure API Management

* Azure Service Bus / Event Grid

* Azure Functions / App Service / containers

* SQL / NoSQL

* Redis or equivalent caching

* OAuth 2.0 / OIDC / JWT

* Observability and distributed tracing

* CI/CD and automated testing

* Dynamics 365 / Dataverse Web API

* Dynamics workflows, security roles and service limits

PREFERRED EXPERIENCE

* Headless CRM implementation experience

* BFF and API gateway architecture

* Event-driven read-model patterns

* CRM integration with document, analytics or customer-data platforms

* Financial-services technology experience