About Paybis Paybis is a global fintech company in the crypto and payments space. Since 2014, we’ve been building products that help people and businesses buy, sell, and exchange cryptocurrency. As of 2026: 6.9M+ users across 180+ countries, $2B in transaction volume in 2025 alone (+266% YoY), and recognised as Best Crypto Payments Provider at AIBC Awards Dubai 2026. Self-funded and profitable. The Role This is not a generalist DevOps addition to an existing team. You will be the first dedicated DevOps Engineer for a new product stream — with full ownership of its infrastructure from day one. You join at the greenfield stage: the infrastructure decisions made now will define the architecture for everything that follows.
The platform processes real financial transactions in real time for millions of users globally. Infrastructure reliability here is not a supporting function — it is a core business requirement. If you thrive on building things from scratch, take security seriously by default, and want your infrastructure decisions to have visible, long-term impact — this role is for you. What You’ll Be Working On * Design and build product stream infrastructure from the ground up using the existing platform framework and standards * Implement comprehensive observability: monitoring, logging, alerting, and dashboards (Grafana, Loki, Prometheus, VictoriaMetrics, CloudWatch) * Build and optimise CI/CD pipelines using GitLab CI/CD to enable efficient and reliable software delivery * Own and maintain AWS infrastructure: EC2, ECS, Lambda, S3, API GW, SQS, SNS, EventBridge, RDS Aurora, VPC * Write, structure, and maintain Terraform configurations — remote state, module architecture, team workflows * Manage Linux servers (Debian-based and AmazonLinux): administration, security hardening, troubleshooting * Implement secret management, IAM policies, and least-privilege access controls * Participate in on-call rotation and incident response as the stream matures * Work closely with the product stream’s engineering team and the core DevOps team * Contribute to runbooks, post-mortems, and operational documentation
What We’re Looking For Must have: * 3+ years of hands-on DevOps / infrastructure engineering in a production environment * Linux administration: Debian-based OS and AmazonLinux — user management, permissions, security hardening, systemd, troubleshooting * AWS core services in production: EC2, ECS, Lambda, S3, API GW, CloudWatch — real operational experience, not just console familiarity * AWS networking: VPC design, Security Groups, NACLs, subnets, routing — can design and debug network connectivity issues * AWS messaging: SQS, SNS, EventBridge — understands event-driven patterns and queue-based architectures * AWS RDS (Amazon Aurora) — deployment, backup/restore, monitoring, basic performance tuning * Docker and Docker Compose in production — building images, multi-stage builds, compose for deployment * Terraform: writing, structuring, and applying configurations — not just reading existing code — mandatory * GitLab CI/CD: building and maintaining pipelines — stages, variables, environments, caching, artifacts * Git: branching strategies, MR workflows, comfortable in a team code review culture * Troubleshooting skills: Linux, network, application performance, database — systematic diagnostic approach * Security mindset: principle of least privilege, secret management, Security Group hygiene — default operating mode, not a specialisation * English B2+ — incident writeups, runbooks, MR descriptions, async team communication
Nice to have: * Serverless Framework or AWS CloudFormation — production serverless deployments * Monitoring stack: Grafana, Prometheus, Loki, VictoriaMetrics — set up or maintained in production * AWS Secrets Manager or SSM Parameter Store — secret rotation and secure config management * AWS WAF, Shield, or GuardDuty — deployed or managed in production * Kubernetes / EKS — even exposure-level experience * Fintech, payments, or crypto/blockchain industry experience * AWS cost optimisation: right-sizing, Reserved Instances, Savings Plans * Infrastructure performance tuning: ECS task sizing, Lambda memory/timeout, RDS Aurora clusters * AWS Config, CloudTrail, or Security Hub — compliance posture monitoring * Scripting: Python or Bash for operational automation * Experience writing runbooks, on-call documentation, or post-mortems
Tech Stack AWS (EC2, ECS, Lambda, S3, API GW, CloudWatch, SQS, SNS, EventBridge, RDS Aurora, VPC) · Terraform · GitLab CI/CD · Docker & Docker Compose · Serverless Framework · Grafana · Prometheus · Loki · VictoriaMetrics · Linux (Debian / AmazonLinux) What Success Looks Like First 30 days — Complete infrastructure tasks with guidance, gain solid understanding of the platform architecture, onboard into team processes and tooling.
First 90 days — Independently (with review) deliver infrastructure tasks and actively support the product stream’s engineering team. First infrastructure components deployed.
First 6 months — Independently (with review) own and maintain stream infrastructure, proactively improve reliability and automation, act as the primary DevOps point of contact for the stream. Interview Process * Technical interview — DevOps Engineers (1.5h): AWS architecture, Terraform IaC, GitLab CI/CD, Linux troubleshooting, security and compliance awareness * Cultural fit interview with HRD (45 min) * Final interview with CIO + Team Lead (1h)
What We Offer * Full infrastructure ownership from day one — greenfield opportunity with high long-term impact * Real fintech scale: 6.9M+ users, $2B in 2025 volume — your infrastructure runs real financial transactions * Modern stack: AWS, Terraform, Docker, GitLab CI/CD, Grafana — no legacy environments * Product company, not an agency — your infrastructure decisions stay with you * Crypto/fintech domain: technically challenging, regulation-driven, non-trivial security and reliability requirements * Remote-first, high autonomy, minimal micromanagement * Fast-growing company: 266% YoY growth in 2025, self-funded and profitable * Collaborative DevOps team — existing team as support network, not competition
