# Senior Python Software Engineer at CodeIT
Source: https://true-hire-ten.vercel.app/jobs/senior-python-software-engineer-codeit-ws4fxmi5 · Company profile: https://true-hire-ten.vercel.app/companies/codeit · Apply on the employer's site: https://codeit.peopleforce.io/careers/v/250910-senior-python-software-engineer?utm_source=freehire.me
**In short:** Senior backend engineer building Python/FastAPI services for an AI assistant over document-heavy project data: RAG search with citations, LLM/agent orchestration, a model gateway (caching, rate limits, cost budgets), and PostgreSQL/permissions integration on AWS, to production-grade standards with tests, tracing and IaC.

## Job details
- Location: Ukraine and Europe
- Seniority tag: Senior
- Category: Software Engineering
- Countries: Ukraine
- Posted: 2026-11-12 (7 days ago, fresh)
- Skills named: ai, analytics, api, api-gateway, aws, azure, cdk, ci-cd, cloud, ecs, eks, fastapi, gcp, infrastructure-as-code, lambda, langfuse, langgraph, langsmith, llamaindex, llm, mcp, nodejs, observability, openid, postgresql, python, rds, react, semantic-kernel, sharepoint, sql, sso, terraform, test-automation, typescript
## Requirements

- 5+ years of backend engineering in Python (FastAPI or similar), with services running in production
- 1+ year building LLM applications in production: tool calling, structured outputs, context management, streaming
- Agent and orchestration frameworks or patterns (e.g. LangGraph, LlamaIndex, Semantic Kernel, Bedrock Agents, MCP), and judgement on when not to use one
- Has integrated RAG into an application: hybrid search, reranking, citations, handling unanswerable questions
- PostgreSQL including performance tuning; asynchronous processing, queues, caching
- Major cloud in production: AWS preferred (Bedrock, Lambda/ECS/EKS, API Gateway, RDS); equivalent Azure or GCP accepted
- Automated testing, CI/CD, containers, infrastructure as code (Terraform or CDK), observability
- Proven production LLM application with real users, with measured answer quality, latency (p50/p95) and cost per question

## Nice to have

- LLM evaluation and observability tools (e.g. Langfuse, LangSmith, Ragas); prompt caching, model routing, batch APIs
- Text-to-SQL over a governed semantic layer, or analytics features on structured data
- SSO/OIDC, row- and document-level permissions, audit logging, prompt-injection defences
- Node.js, TypeScript/React for the optional user-facing scope
- Construction or engineering documents, project-controls systems (Primavera, Ecosys, SharePoint, Aconex), or another document-heavy field such as legal or e-discovery
- Running one system on several clouds or inside clients' own cloud accounts

## About the role
**Responsibilities**

- Build Python services and APIs that expose document search, navigation and context retrieval to the AI assistant and agents, e.g. as tools or MCP servers.
- Implement LLM and agent workflows: tool calling, multi-step orchestration, routing each question to document search, summaries or SQL over structured project data, streamed answers with citations.
- Build the model gateway: model tiers, batch inference, caching, rate limits, retries, per-request token and cost budgets.
- Integrate with the platform's existing application and PostgreSQL data layer, including user identity and document-level permissions enforced before results are returned.
- Make it production-grade: automated tests including LLM-output evaluation in CI, tracing of latency and cost per question, security, infrastructure as code.
- Agree interfaces, latency budgets and quality targets with the data/AI engineers; review code; keep documentation and runbooks current.

**Optional scope, to be confirmed with the client: **user-facing features such as the chat and answer view with citations and source preview, and admin screens for ingestion runs and quality dashboards (TypeScript/React or similar).

**Must-have**

- 5+ years of backend engineering in Python (FastAPI or similar), with services running in production.
- 1+ year building LLM applications in production: tool calling, structured outputs, context management, streaming.
- Agent and orchestration frameworks or patterns (e.g. LangGraph, LlamaIndex, Semantic Kernel, Bedrock Agents, MCP), and judgement on when not to use one.
- Has integrated RAG into an application: hybrid search, reranking, citations, handling questions the documents cannot answer.
- PostgreSQL including performance tuning; asynchronous processing, queues, caching.
- A major cloud in production: AWS preferred (Bedrock, Lambda/ECS/EKS, API Gateway, RDS); equivalent Azure or GCP experience accepted.
- Automated testing, CI/CD, containers, infrastructure as code (Terraform or CDK), observability.

**Nice-to-have**

- LLM evaluation and observability tools (e.g. Langfuse, LangSmith, Ragas); prompt caching, model routing, batch APIs.
- Text-to-SQL over a governed semantic layer, or analytics features on structured data.
- SSO/OIDC, row- and document-level permissions, audit logging, prompt-injection defences.
- Node.js, TypeScript/React, for the optional user-facing scope.
- Construction or engineering documents, project-controls systems (Primavera, Ecosys, SharePoint, Aconex), or another document-heavy field such as legal or e-discovery.
- Running one system on several clouds or inside clients' own cloud accounts.

**Proven experience**
What the CV and the interview should show, with concrete numbers:

- An LLM application in production with real users: what it did, users or requests per day, how answer quality was measured.
- Latency and cost achieved (p50/p95 response time, cost per question) and what was changed to reach them.
- An agent or tool-calling workflow they designed: the tools, handling of failures and wrong tool choices, testing.
- A retrieval integration: corpus size, how citations were produced, how permissions were enforced.
© TrueHire. Listing data from freehire; applications go to the employer's own page.