Senior Backend / Platform Engineer

Easy2Employ, LLC; Pakistan; On-site; PKR 2,000,000 - 4,000,000; Full time

Job summary

Easy2Employ, LLC is looking for a senior backend engineer to own a Python AWS stack, manage high-volume ingestion, and operate a multitenant canonical results store. You will also take over a production codebase from an external partner and make it yours.

Responsibilities include building and running data pipelines, integrating with enterprise systems, and ensuring observability and resilience. Collaborative, ownership-driven mindset is essential, with some evening hours overlapping US Central

Qualifications

• 6+ years of backend engineering with Python on AWS.
• Designed and run high-volume data pipelines with real failure modes.
• Experience with bi-directional enterprise integrations and audited API exchanges.
• Ownership of unfamiliar production codebases without rewrites.
• Able to overlap evening hours (IST/PKT) with US Central mornings.

Responsibilities

• Own production codebase and maintain production systems.
• Design and operate high-volume data pipelines with failure handling.
• Implement and manage enterprise integrations with auditability.
• Maintain idempotent, backpressure-aware data processing.
• Ensure observability with structured logs, metrics, and tracing.

Skills

Backend engineering

Python on AWS

Data pipelines

Multi-tenancy

Observability

Ownership mindset

Tools

AWS services

S3

SQS/SNS

Step Functions

ECS/Fargate

Lambda

RDS Postgres

PostgreSQL

CloudWatch

Job description

You own the platform's spine: high-volume ingestion, processing orchestration, the canonical results store, and bi-directional integrations with enterprise systems — multitenant, entitled, auditable — while live daily service never breaks. You will also take over a production codebase from an outgoing development partner and make it yours.

Core Experience — Must Have

• – 6+ years backend engineering with Python on AWS, operating production systems you built.
• – Has designed and run high-volume data pipelines with real failure modes — and been paged for them.
• – Has integrated bi-directionally with third-party enterprise systems (sync jobs, webhooks, audited API exchanges).
• – Has inherited an unfamiliar production codebase and taken ownership without a rewrite.
• – Able to overlap a few evening hours (IST/PKT) with US Central mornings most weeks.

TECHNICAL DEPTH WE EXPECT

• – AWS services — S3 (multipart, presigned, lifecycle), SQS/SNS, Step Functions or equivalent orchestration, ECS/Fargate, Lambda, RDS Postgres, CloudWatch; working IAM literacy.
• – PostgreSQL — schema design, indexing strategy, partitioning, query-plan analysis, zero-downtime migrations.
• – Pipeline semantics — idempotency keys and dedup; retry/backoff with dead-letter queues; poison-message handling; backpressure; exactly-once effects on at-least-once infrastructure.
• – Large-binary handling — chunked and resumable uploads, integrity checksums, prioritized transfer ordering, compression trade-offs on constrained links.
• – APIs & integration — contract-first OpenAPI, versioning, webhook design (signing, retries, replay protection), third-party sync jobs with a full audit trail of what was sent, when, and what came back.
• – Multi-tenancy — pooled-schema isolation (row-level security or app-layer), per-tenant partitioning, entitlement checks in the hot path.
• – Storage economics — lifecycle tiering, compression, per-unit cost tracking — storage that compounds daily must stay profitable.
• – Observability — structured logging, metrics, tracing; reads production data before guessing.

How We’ll Assess You

• – A pipeline design exercise: high-volume binary ingestion with injected failures — we probe idempotency, recovery, and cost.
• – Code reading on an unfamiliar service: explain what it does, find the defect.
• – An integration-contract design against a slow, flaky, rate-limited third-party API.

NICE TO HAVE

Media or imagery pipelines

• PostGIS
• ERP-class enterprise integrations
• Kafka/Kinesis
• Terraform.