Skip to main content

Platform Automation Engineer

Provisioning & Deployment Architecture

Context

Our GTM Operating System runs on controlled infrastructure.

We now require a deterministic provisioning and deployment system to replicate installations efficiently across client environments.

This role follows core platform stabilisation.

The Role

We are seeking a Platform Automation Engineer to design and implement a repeatable environment provisioning system for Mac-based and server-based deployments.

The objective is simple:

  • Reduce installation time
  • Eliminate configuration drift
  • Ensure deterministic replication

What You Will Do

  • Design and implement an automated installation workflow
  • Build a CLI-based provisioning tool
  • Automate environment configuration (.env generation and validation)
  • Validate API connectivity across integrated services
  • Package services using Docker
  • Implement post-install health checks
  • Design update and patch workflows
  • Document deployment architecture

What We Are Looking For

Required

  • Strong Python
  • Shell scripting
  • Docker
  • macOS/Linux systems knowledge
  • Environment configuration management
  • Networking fundamentals

Advantageous

  • Experience building CLI tools (Typer, Click, etc.)
  • Experience designing installers
  • CI/CD setup
  • Deployment automation tooling

What This Role Is Not

  • Not enterprise Kubernetes management
  • Not cloud-native hyperscale architecture
  • Not corporate DevOps bureaucracy

This is focused infrastructure replication.

Engagement

We are open to:

  • Contract engagement
  • Permanent hire
  • Structured project-based work

If you are motivated by system clarity and deterministic deployment rather than complexity layering, we would like to speak with you.

Excellence Defined

Deterministic Provisioning

Excellence means:

  • Installation scripts that run cleanly the first time
  • Reproducible environment setup
  • Explicit configuration validation
  • Structured failure reporting

You remove human guesswork.

Environment Validation

Excellence means:

  • Connectivity testing across external services
  • Health-check workflows
  • Clear pass/fail indicators
  • Update-safe configuration management

You prevent silent misconfiguration.

Deployment Automation

Excellence means:

  • Structured CLI tools
  • Clean separation between bootstrap and configuration
  • Versioned install logic
  • Predictable update mechanisms

You treat deployment as code.

Documentation & Clarity

Excellence means:

  • Clear installation instructions
  • Defined configuration schema
  • Explicit system prerequisites
  • Documented rollback paths

You assume that someone else must maintain what you build.

Cross-Role Expectations

Regardless of role, excellence includes:

  • Writing code that is readable six months later
  • Preferring simplicity over cleverness
  • Communicating trade-offs clearly
  • Respecting defined architecture
  • Avoiding unnecessary technology layering

We value engineers who understand that:

Infrastructure must be commercially grounded.

What Excellence Does Not Look Like

  • Introducing microservices without need
  • Suggesting Kubernetes for small-scale infrastructure
  • Adding tools that do not reduce labour
  • Overcomplicating simple workflows
  • Hiding complexity behind abstraction

We optimise for clarity, not spectacle.

Why This Matters

The sX GTM Operating System is designed to replace fragmented digital marketing stacks.

That requires:

  • Precision
  • Discipline
  • Structured thinking
  • Commercial awareness

We are building infrastructure that influences pipeline and revenue.

That demands engineering maturity.

Platform Automation Engineer

(Commences After Core Stabilisation)

Days 1–30: Deployment Analysis

You will:

  • Audit current manual installation process
  • Identify repetition and fragility
  • Map dependency tree
  • Define provisioning stages
  • Design CLI structure

By Day 30:

  • Installation architecture documented
  • Provisioning tool design defined
  • Configuration schema agreed

Days 31–60: Provisioning Tool Implementation

You will:

  • Build bootstrap script
  • Build CLI-based configuration tool
  • Automate .env generation
  • Implement API connectivity validation
  • Integrate health-check logic

By Day 60:

  • Clean repeatable installation process
  • Deterministic validation output
  • Reduced setup time

Days 61–90: Replication & Update System

You will:

  • Finalise update mechanism
  • Version deployment logic
  • Document rollback procedures
  • Create clean installation documentation
  • Test deployment in controlled environments

By Day 90:

  • Installation time reduced dramatically
  • Environment drift eliminated
  • System replication reliable

What 90 Days Does Not Look Like

  • Massive architectural rewrite
  • Microservices migration
  • Kubernetes deployment
  • Overengineered DevOps pipeline
  • Feature explosion

It looks like:

  • Structured codification
  • Controlled integration
  • Reduced manual dependency
  • Improved commercial reliability

Why This Matters

The goal is not software for its own sake.

The goal is infrastructure that:

  • Reduces labour
  • Preserves clarity
  • Improves commercial optionality
  • Supports measured growth

The first 90 days establish discipline.

From there, scale becomes a choice — not a necessity.

Initial conversations only. Send CV and brief introduction to: This email address is being protected from spambots. You need JavaScript enabled to view it.”

No applicant tracking system required at this stage, no agencies.