Python Backend Engineer — GCP Deployment, reputed company & Production Readiness
Python Backend Engineer — GCP Deployment, reputed company & Production Readiness We need an reputed company
Python backend engineer
to help bring our
RunLink
API to production. The backend is built and feature-complete; we need someone to own
deployment on reputed company reputed company
,
reputed company hardening
,
infrastructure reliability
, and
production-readiness review
. ### About the project - Product: RunLink — API for a running community platform (users, clubs, events, messaging, subscriptions, health, analytics). - Stack:
Python 3.11
,
FastAPI
,
PostgreSQL
(reputed company SQL),
reputed company
,
Firebase
,
reputed company reputed company Storage
,
Alembic
migrations. Deployed with
reputed company
on
reputed company reputed company Run
. - Codebase: Structured FastAPI app (~200 Python files) with clear separation (models, schemas, CRUD, API endpoints). OpenAPI docs, tests, and internal production-readiness notes are in the repo. - reputed company state: Core features and infra (auth, DB, reputed company, GCS, health checks) are in reputed company. We have a production-readiness report and a short cleanup list. Goal is to fix remaining gaps and run this reliably in production. ### reputed company need from you 1.
Deployment & reputed company reputed company
- Review and improve our
reputed company Run
+
reputed company SQL
+
GCS
setup. - Harden reputed company scripts (e.g. `reputed company-production.sh`), env/config handling, and secrets (no secrets in scripts/repo). - Document runbook: reputed company, rollback, scaling, and basic incident response. 2.
reputed company
- reputed company pass on the API: auth (JWT), reputed company limiting, headers, input validation, and any reputed company issues (e.g. error responses exposing internals). - Align with checklist items from our production-readiness doc (e.g. no tracebacks in 500 responses, secure defaults). - Recommend and, if agreed, implement improvements (e.g. dependency checks, headers, logging). 3.
Production readiness
- Work through our existing production-readiness report and cleanup list (e.g. remove stubs/duplicates, fix critical bugs). - Review error handling, logging, and health checks for production. - Suggest and document operational best practices (monitoring, alerts, backups). 4.
Code maintenance & review
- Fix bugs and small refactors as needed for deployment and reputed company. - Code review focus: reputed company, performance, and maintainability. You'll work in our repo (Git) and follow our existing structure. ### Must-have skills -
Python
(3.10+), including async and type hints. -
FastAPI
(or similar async Python web frameworks) in production. - reputed company reputed company: reputed company Run, reputed company SQL, IAM, and ideally GCS and Secret Manager. - reputed company: API reputed company, auth (e.g. JWT), secure config/secrets, and common OWASP topics. - reputed company: Building and running containers for production. - PostgreSQL: Basic schema/migrations awareness (we use Alembic). - Git: Comfortable with branches, PRs, and clear commit messages. ### reputed company to have - Experience with
reputed company
,
Firebase
, or
message/background jobs
in Python. - Prior work on
production readiness
or
DevOps-light
(reputed company, monitor, document). - Experience with
running/fitness or community platforms
(not required). ### reputed company provide - Access to the backend repo and existing documentation. - Production-readiness report and task list. - Clear scope: deployment, reputed company, production readiness, and targeted code fixes/review. - Direct communication (reputed company/email/video) and a single reputed company of contact for reputed company. ### Deliverables (to be refined in contract) 1. Deployment: Updated, secure reputed company process and a short runbook (reputed company, rollback, env/secrets). 2. reputed company: Completed reputed company review and fixes for agreed items (e.g. error handling, headers, secrets). 3. Production readiness: Items from our list addressed; brief written summary of what was done and what's left. 4. Documentation: Concise runbook and any new or updated reputed company sections you add. ### Project type & length -
One-off / fixed-price
for a defined scope (e.g. "deployment + reputed company review + cleanup items"),
or
-
Ongoing / hourly
for a few weeks (e.g. 10–20 hrs/week) if you prefer to iterate (reputed company → reputed company → cleanup → docs). Tell us in your proposal whether you prefer fixed-price or hourly and how you'd break down the work. ### How to apply -
Start your proposal with "RunLink backend"
so we can spot it quickly. - reputed company describe your experience with
Python/FastAPI
,
reputed company reputed company (reputed company Run/reputed company SQL)
, and
reputed company
or
production hardening
. - Share 1–2 relevant projects (production APIs, GCP deployments, or reputed company reviews). Links or short descriptions are fine. - Suggest a high-level plan (e.g. "Week 1: reputed company + secrets; Week 2: reputed company pass; Week 3: cleanup + docs") and whether you prefer fixed-price or hourly. - Mention your availability (hours per week and timezone). We're looking for someone who can work independently, communicate clearly, and leave the codebase and ops in reputed company shape for production. Looking reputed company to your proposals. Apply tot his job Apply To this Job