MediaFast

About the Role

We’re looking for a backend-focused software engineer who treats quality as part of engineering, not as a separate function.

This is not a QA-only or SDET role. You will write production backend code, design APIs, and take ownership of testing, reliability, and correctness across the systems you build.

Our platform is data-heavy and API-driven, so correctness, observability, and thoughtful testing matter as much as feature delivery.

What You’ll Do

• Build and maintain backend services and APIs
• Design and implement meaningful tests (unit, integration, contract)
• Validate data integrity and API contracts before production
• Integrate tests into CI/CD pipelines
• Monitor production behavior and test outcomes
• Collaborate with engineers, product, and data teams to ship reliable systems
• Use AI tools responsibly to accelerate work (not replace understanding)

What We’re Looking For

• Strong backend engineering experience
• Comfortable owning both code and tests
• Solid understanding of REST APIs and data flows
• Experience with CI/CD and cloud environments
• Ability to reason about failure modes, edge cases, and trade-offs
• Clear communicator who can explain technical decisions

• Senior Platform & Infrastructure Engineer
• This role is a software-first approach to systems. You aren't just managing servers; you are building the platform that runs the company. It requires a blend of high-level architectural thinking and deep-tier systems automation.
  
   
• The Core Identity
• Software-First Infra: You treat infrastructure like a product, using software engineering principles (code reviews, testing, CI/CD) to manage the cloud.
• Developer Enablement: You build self-service tooling so product engineers can deploy and scale their own services safely.
• Architectural Guard: You own the long-term reliability and performance strategy, ensuring the system scales as the business grows.
  
   
• The Technical Stack
• Category
• Core Technologies
• Cloud Platform
• AWS or GCP (Identity, IAM, VPCs, Managed Services)
• Orchestration
• Kubernetes (Deep internals: CRDs, Operators, Networking, ingress)
• Languages
• Go or Python (for automation); TypeScript/Node (for tooling/CDK)
• IaC
• Terraform (Primary) or Pulumi
• Data & Storage
• PostgreSQL (Performance tuning, replication, schema evolution)
• Observability
• Prometheus, Grafana, Datadog (Tracing, SLIs, Alerting)
• CI/CD
• GitHub Actions, ArgoCD, or CircleCI
  
   
• What This Is vs. Is Not
• ✅ IS: Designing a Kubernetes operator to automate database migrations.
• ❌ NOT: Manually clicking in the AWS Console to resize a disk.
  
   
• ✅ IS: Improving developer velocity by building a "one-command" staging environment.
• ❌ NOT: Being the "gatekeeper" who must approve every deployment ticket.
  
   
• The Ideal Candidate Profile
• 5+ Years in Software or Systems Engineering with a focus on cloud-native platforms.
• Operator Mindset: You've run high-traffic systems and know how they break at 3 AM (and how to design them so they don't).
• Tool Builder: You prefer writing a Go service to automate a task rather than writing a documentation page on how to do it manually.
• Would you like me to help you map your specific experience with these tools (K8s, Terraform, Postgres) into a cohesive interview narrative?