Plotux Careers

Backend / Platform Engineer

Data systems and cloud infrastructure: PostgreSQL, DynamoDB, AWS.

  • Open
  • Netherlands
  • Freelance, B2B
  • Remote-friendly
  • AI-DevOps friendly
How to apply

About the role

Plotux · Product engineering, remote-friendly

Plotux is a global, multilingual publishing marketplace and immersive reading platform: authors and publishers sell books; readers read, listen or do both in sync, across devices. We are multi-currency and operate in the US and EU today, each zone with its own tax, legal and data rules.

This is a combined backend and cloud infrastructure role. You will write the services and their data layer, and build, ship and run them. You will choose the right kind of storage for each job: strict relational storage where correctness is everything, and scalable key-value / document storage where volume and access patterns dominate.

  • PostgreSQL (Aurora)
  • DynamoDB
  • Meilisearch
  • OpenSearch
  • AWS

Concepts you will use every day

The ideas behind every review.

  • Infrastructure as code
  • Observability and cost awareness
  • Backpressure and failure isolation
  • Idempotency
  • Immutability and audit
  • Eventual vs strong consistency
  • Software Factory
  • Event-driven architecture
  • Asynchronous processes
  • Serverless

What you will build

Projects you’d add to your CV on your Plotux journey.
  • Marketplace data layer Relational storage for orders, the ledger and the currency catalog; key-value / document storage for products, offers, provider events and exchange-rate cache. Schemas, migrations, indexes, backups.
    • Aurora PostgreSQL
    • DynamoDB
    • AWS Backup
  • Backend API layer Typed services for catalog, offers, checkout, accounts and reading-progress sync, behind delegated authentication.
    • Node.js / TypeScript
    • REST
    • Keycloak / OIDC
  • Search system Multilingual full-text and faceted catalog search, an indexing pipeline fed by data-change events, relevance tuning.
    • Meilisearch
    • OpenSearch
    • DynamoDB Streams
    • EventBridge
  • Financial accounting system A double-entry ledger. A confirmed purchase is split between the platform, the creator, tax and payment fees, exact to the smallest currency unit, in many currencies, with refunds and reconciliation.
    • PostgreSQL
    • Stripe
    • VAT
    • FX rate providers

What you will learn

You will work closely with our solutions architect on design, reviews and production decisions.
  • Horizontal scaling of workloads Stateless services, autoscaling, partitioning, connection management, load testing.
    • ECS Fargate / EKS
    • Aurora Serverless v2
    • RDS Proxy
    • DynamoDB on-demand
  • AI-DLC and Software Factory An AI-driven development lifecycle (AI-DLC) where AI agents spec, plan, build and review under human approval, and an automated path from decision record to production.
    • Claude Code
    • MCP
    • ADRs
    • AI-driven CI/CD
  • Event-driven architectures Event buses, outbox, sagas, idempotent consumers, replay.
    • EventBridge
    • SQS / SNS with DLQs
  • Serverless Functions, workflow orchestration, event schedulers and when not to use them.
    • Lambda
    • Durable Functions
    • EventBridge Scheduler
    • API Gateway
  • Data replication Cross-region and cross-cloud, change data capture, consistency trade-offs.
    • Aurora Global Database
    • PostgreSQL logical replication
    • DynamoDB Global Tables and Streams
  • Data protection Encryption and key management, least privilege, personal-data handling, data residency per zone.
    • KMS
    • IAM
    • Secrets Manager / SSM Parameter Store
    • GDPR
  • Business continuity Backups, point-in-time recovery, restore drills, disaster recovery, RPO / RTO, runbooks.
    • AWS Backup
    • Aurora and DynamoDB PITR
    • Multi-AZ / cross-region failover
  • Multi-cloud (AWS + GCP) Workload placement, identity federation, cross-cloud networking, portable infrastructure as code.
    • AWS
    • Google Cloud
    • Workload Identity Federation
    • Terraform
  • Observability Logs, metrics, traces, service-level objectives and alerting.
    • CloudWatch
    • X-Ray
    • OpenTelemetry (ADOT)
  • Architecture practice Decision records, architecture reviews, threat modeling, cost management, comparing competing implementations.
    • ADRs
    • AWS Well-Architected
    • Cost Explorer
    • Bake-offs

What you will do

Your daily responsibilities.

Backend

  • Design and build services and APIs that stay correct under retries, duplicates and partial failure.
    • Node.js / TypeScript
  • Model a ledger where every posting balances and history is immutable.
    • PostgreSQL
    • DynamoDB
  • Model non-relational data from access patterns: keys, secondary indexes, expiry, recovery.
    • DynamoDB (GSIs, TTL, PITR)
  • Build asynchronous pipelines: events arrive, are queued and processed idempotently; failures are isolated and replayable.
    • Stripe webhook → CloudFront + Lambda → SQS → processors
    • DLQs
  • Handle money correctly: integer minor units, explicit currency, deterministic rounding.
  • Evolve database schemas on live data without downtime.
    • PostgreSQL migrations
  • Integrate external providers: payments, exchange rates, email, identity.
    • Stripe
    • FX rate APIs
    • SES
    • Keycloak / OIDC

Infrastructure

  • Describe all infrastructure as reviewed, versioned code; no manual changes.
    • Terraform
  • Build delivery pipelines and release flows across isolated environments.
    • GitHub Actions / CodePipeline
    • dev / stage / prod AWS accounts
  • Make systems observable and costs visible and attributable.
    • CloudWatch
    • EventBridge

Requirements

Minimum is what we expect on day one. Ideal is where the role grows.

Software engineering

Minimum

  • 4+ years of building and owning production backend services.
    • SQL
    • TypeScript / Node.js
  • API design, input validation, error handling, automated testing.
    • REST
  • Understanding of idempotency, at-least-once delivery, retries and backoff.

Ideal

  • Event-driven patterns.
    • Outbox
    • Saga
    • Event sourcing
  • Financial systems: double-entry accounting, invoicing, tax, refunds, reconciliation.
    • Stripe (webhooks, payment intents, fees, refunds)
    • VAT
  • Stripe API integration experience.
  • Monorepo and shared-package practices.
    • Bun / pnpm workspaces
  • Delegated authentication and authorization: OIDC, token flows, mutual TLS.
    • Keycloak
    • Device certificates

Relational data

Minimum

  • Schema design, constraints, indexing, joins, window functions.
    • PostgreSQL
  • Transactions, isolation levels, locking, reading query plans.

Ideal

  • Managed relational services: high availability, read replicas, failover, elastic capacity, upgrades.
    • Aurora PostgreSQL / RDS
    • Multi-AZ
    • Aurora Serverless
  • Connection pooling and capacity management.
    • RDS Proxy
    • PgBouncer
  • Partitioning, replication, zero-downtime schema changes.
    • PostgreSQL partitioning
    • Logical replication
  • Backup and point-in-time-recovery drills; encryption at rest and in transit.
    • PITR
    • KMS
    • TLS
  • Modeling strict invariants (balances sum to zero, immutable postings).

Non-relational data

Minimum

  • Production use of at least one non-relational store (key-value, document).
  • Access-pattern-first modeling.

Ideal

  • Wide-column / key-value design in depth: partition and index design, conditional writes, transactions, expiry, change streams, point-in-time recovery, capacity modes.
    • DynamoDB (GSIs, TTL, Streams, PITR, on-demand / provisioned, DynamoDB Local)
  • Caching and rate limiting with an in-memory store.
    • ElastiCache / Redis
  • Full-text and faceted search engines.
    • Meilisearch
    • OpenSearch / Elasticsearch

Cloud and infrastructure

Minimum

  • Core cloud knowledge.
    • S3
    • Lambda
    • SQS
    • CloudWatch
  • Containers and local multi-service environments.
    • Docker
    • docker-compose
  • Infrastructure as code, in any tool.
    • Terraform
  • Version control workflows and continuous integration.
    • Git
    • GitHub Actions
  • Linux, shell, DNS, TLS, mTLS, HTTP.

Ideal

  • Compute modelsContainer orchestration (managed or Kubernetes), serverless functions, blue/green and canary releases, image registries and lifecycle.
    • ECS Fargate
    • EKS (Karpenter)
    • Lambda
    • CodeDeploy
    • ECR
  • Serverless and messagingWorkflow orchestration, event buses and schedulers, queues and topics with dead-letter handling, managed GraphQL / real-time APIs, streaming.
    • Step Functions
    • EventBridge (+ Scheduler)
    • SQS / SNS
    • AppSync
    • Kinesis / MSK
  • Edge and securityCDN caching and origin protection, web application firewall, DDoS protection, user identity services, key management, secret stores, threat detection, audit trails.
    • CloudFront (OAC, signed URLs)
    • WAF
    • Shield
    • Cognito
    • KMS
    • Secrets Manager / SSM
    • GuardDuty
    • Security Hub
    • CloudTrail
  • IaC at scaleReusable modules, remote locked state, multi-account / multi-tenant organization setup, drift detection, policy-as-code.
    • Terraform modules
    • S3 state with native locking
    • AWS Organizations
    • tflint
    • Checkov
    • cfn-guard
  • DeliveryPipelines with short-lived federated credentials, progressive delivery, rollbacks.
    • GitHub Actions OIDC to AWS
    • CodePipeline / CodeBuild / CodeDeploy
  • ObservabilityLogs, metrics, traces, structured logging, service-level objectives.
    • CloudWatch (Logs Insights, alarms, EMF)
    • X-Ray
    • OpenTelemetry (ADOT)
  • Cost and reliabilityTagging and cost attribution, right-sizing, commitments, backup policy, disaster recovery, runbooks, architecture reviews.
    • Cost Explorer
    • Budgets
    • Savings Plans
    • AWS Backup
    • Well-Architected reviews

How to apply

Email us at job@plotux.com and include the following.

Subject line Backend Engineer – your name
  1. A brief introduction: who you are, what you have built recently, and why this role interests you (a few sentences are enough).
  2. Your CV (Markdown, PDF or a landing page).
  3. Your work: links to your GitHub, portfolio or any public work you are proud of, if available.
  4. Your compensation expectations: monthly or annual, gross, and in your preferred currency.
  5. Your location (country and time zone) and your preferred form of employment: B2B contract, freelance, business incubator, etc.
  6. Your availability: when you could start and how many hours per week you can commit.
  7. Optional: what you would like to add to your CV after this project. It helps us understand your goals.
Email job@plotux.com