Senior Python Full Stack Technical Lead with Flask, FastAPI, Django, GraphQL , AWS , Amazon EKS , Terraform & Salesforce Integration /CDC exp - Frisco TX -Onsite work & Mandatory In person Interview
Senior Python Full Stack Technical Lead
SIT Polyglot Python Platform Evolving Toward Event-Driven Systems
About the Role
SIT Academy is seeking a hands-on Senior Python Full Stack Technical Lead to guide the engineering of its learner-facing and operational platforms. The Academy stack is Python-first—spanning Flask, FastAPI, and Django—integrated with a Hasura GraphQL data layer, a WordPress content surface, and Salesforce (Apex) as a system of record, all deployed to AWS on Kubernetes (Amazon EKS) with Terraform.
This is a builder-leader role: you will write and review production code, set technical direction, and mentor an onshore/offshore team. The architecture is deliberately evolving—today a mix of request/response services and point integrations, and on a clear path toward target-state event-driven systems. We need a lead who can keep the current platform healthy while steering the team toward asynchronous, decoupled, event-first patterns, and who treats that migration as an opportunity rather than a chore.
The Architecture & Where It’s Heading
A central part of this role is comfort with a polyglot, multi-surface platform and the discipline to evolve it coherently. The current landscape and target direction look like this:
- Python application tier built across Flask, FastAPI, and Django — a mix of lightweight services, async APIs, and fuller web/admin applications. Part of the lead’s job is bringing consistency (shared libraries, conventions, and service boundaries) across these frameworks.
- Hasura provides a declarative GraphQL (and REST fçade) data-serving layer over PostgreSQL-compatible tables, including event triggers that can emit changes for downstream consumers.
- WordPress serves content and marketing/learner-facing surfaces; the platform integrates with it rather than treating it as a silo.
- Salesforce (Apex) acts as a key system of record; integration patterns (CDC, platform events, REST/Bulk APIs, and Apex callouts) connect it to the Python tier.
- Target state: the platform is moving from synchronous, point-to-point integrations toward an event-driven architecture — durable events, asynchronous processing, and decoupled producers/consumers (e.g., via Hasura event triggers, Salesforce platform events / CDC, and a streaming/eventing backbone). Leading that transition is core to this role.
- Everything runs on Amazon EKS, provisioned with Terraform and shipped through CI/CD.
You don’t need to have used every one of these technologies in production, but you should be able to reason across them, judge when to introduce event-driven patterns versus keep things simple, and lead engineers through the migration without destabilizing what already works.
Core Responsibilities
- Provide hands-on technical leadership—architecture, design, code, and review—while mentoring onshore and offshore engineers and driving technical decisions.
- Design, build, and maintain Python services and applications using Flask, FastAPI, and Django, with attention to consistency, testability, and shared standards across frameworks.
- Define and drive the migration toward event-driven architecture—identifying integration seams, introducing events/async processing, and decoupling tightly-coupled flows incrementally.
- Build and consume APIs over the Hasura GraphQL/REST layer, including configuring and reacting to event triggers.
- Design and maintain integrations with Salesforce (Apex, platform events, CDC, REST/Bulk APIs) and with WordPress content surfaces.
- Implement Change Data Capture (CDC) and reliable messaging patterns for real-time, decoupled data synchronization.
- Write Infrastructure as Code with Terraform and containerize/deploy services on Amazon EKS.
- Create and maintain CI/CD pipelines for automated testing, quality gates, and deployment.
- Champion observability, security, performance, and data-governance practices across the platform.
Required Technical Skills
- 10+ years of software engineering experience with strong, current proficiency in Python 3.
- Production experience with at least two of Flask, FastAPI, and Django — and the ability to work fluently across all three.
- Strong grasp of asynchronous programming in Python (async/await, task queues such as Celery/RQ, background workers).
- Demonstrated experience designing and building event-driven and message-based systems (e.g., Kafka, Pulsar, SQS/SNS, or platform events) — or a clear track record of migrating synchronous systems toward them.
- Proven track record building internet-facing web applications deployed to a public cloud (AWS preferred).
- Solid RESTful and GraphQL API design and implementation.
- Experience integrating enterprise applications with Salesforce using REST APIs, Bulk APIs, Platform Events, Change Data Capture (CDC), and Apex-based integrations.
- Strong relational database skills with PostgreSQL (SQL modeling, performance, migrations).
- Hands-on experience with Docker, Kubernetes (EKS), and Terraform.
- Solid CI/CD and Git version-control / branching and PR-review skills.
- Experience integrating with third-party SaaS and systems of record via APIs and webhooks.
- Exposure to Salesforce Apex — able to read and work with Apex (triggers, classes, callouts) and reason about Salesforce data/automation when building and debugging integrations.
Preferred Qualifications
Experience with:
- Hasura (auto-generated GraphQL/REST, event triggers, permissions) or comparable declarative API layers.
- Deeper Salesforce development — hands-on Apex development, platform events, Change Data Capture, and the broader Salesforce integration ecosystem.
- WordPress integration, headless WordPress, or the WP REST API.
- Streaming/eventing platforms (Kafka, Pulsar, Kinesis) and CDC tooling (Debezium or equivalent).
- Observability and metrics tooling (Prometheus, Grafana, Dynatrace, OpenSearch).
- Test-driven development (TDD) and code-quality tooling such as SonarQube, with peer review via GitHub PR flows.
Knowledge Of
- Microservices and API security patterns; OAuth 2.0 and JWT authentication.
- Event sourcing, CQRS, and distributed-systems / decoupling design patterns.
- Data governance, privacy, and compliance requirements.
- EdTech domain and exposure to platforms such as Moodle, Open edX, or other Learning Management Systems (LMS) and Student Information Systems (Banner)
- Â
Leadership & Communication
- Demonstrated ability to lead distributed onshore/offshore teams and mentor engineers.
- Clear, fluent written and verbal communication—able to explain trade-offs to engineers and non-technical stakeholders alike.
- Pragmatism in an evolving architecture: keeps today’s platform healthy while steering deliberately toward the event-driven target state.