Senior Engineer - Developer Experience

<p>Complexio’s Foundational AI platform automates business processes by ingesting and understanding complete enterprise data—both structured and unstructured. Through proprietary models, knowledge graphs, and orchestration layers, Complexio maps human-computer interactions and autonomously executes complex workflows at scale.</p><p>Established as a joint venture between Hafnia and Símbolo—with partners including Marfin Management, C Transport Maritime, BW Epic Kosan, and Trans Sea Transport—Complexio is redefining enterprise productivity through context-aware, privacy-first automation.</p><p></p><p>We are looking for a Senior Engineer to establish and lead our new Developer Experience team. This team’s mission is to improve engineering productivity, consistency, and satisfaction by building and maintaining the systems, processes, and tooling that underpin our Software Development Lifecycle (SDLC).</p><p>You will shape how our engineers build, test, release, and monitor software, ensuring frictionless workflows while keeping ownership of business logic, test quality, and development practices firmly with the product engineering teams.</p><p>This is a hands-on role with significant influence: you will design systems, implement tooling, measure productivity gaps, and drive adoption of better practices across the engineering organisation.</p><p><strong>Requirements</strong></p><h3>Requirements</h3><h3><strong>Responsibilities</strong></h3><ul><li><strong>CI/CD Infrastructure &amp; Tooling</strong></li><ul><li>Own and operate CI/CD systems (GitHub Actions, runners, caching, artifact storage).</li><li>Maintain stability, scalability, and cost-effectiveness of pipelines.</li><li>Build and maintain systems for our monorepo.</li><li>Ensure CI/CD observability, with metrics flowing into Datadog/Slack.<br/></li></ul><li><strong>Pipeline Instrumentation &amp; Optimisation</strong></li><ul><li>Analyse pipelines for inefficiencies (e.g., flaky tests, redundant steps, lack of caching).</li><li>Recommend and implement optimisations (parallelisation, test selection, caching strategies).</li><li>Define benchmarks and KPIs (e.g., build times, flakiness %, cost per run).</li><li>Measure and report on productivity gaps (e.g., time lost to flaky tests, slow builds, manual release steps).</li></ul></ul><p></p><ul><li><strong>Onboarding &amp; Documentation</strong></li><ul><li>Maintain up-to-date documentation on SDLC processes, CI/CD, release flows, and GitHub usage.</li><li>Provide templates, playbooks, and starter kits.</li><li>Automate repetitive onboarding processes.</li></ul></ul><p></p><ul><li><strong>GitHub &amp; SDLC Guardrails</strong></li><ul><li>Own GitHub governance (branch protections, repo standards, integrations).</li><li>Implement base SDLC guardrails (PR templates, code owners, security scans).</li><li>Ensure compliance requirements are integrated into pipelines.</li></ul></ul><p></p><ul><li><strong>Monitoring &amp; Incident Flow</strong></li><ul><li>Set up alerts for pipeline health regressions.</li><li>Provide first-level triage to distinguish infra vs. test vs. dependency issues.</li><li>Escalate to the correct engineering team and ensure test ownership is tracked.</li></ul></ul><p></p><ul><li><strong>Release Management Support</strong></li><ul><li>Build tooling for release notes, changelogs, packaging, and deployment.</li><li>Standardise release processes across services.</li><li>Enable customer-facing packaging and deployments, without owning release decisions.</li></ul></ul><p></p><ul><li><strong>Change Management &amp; Adoption</strong></li><ul><li>Identify friction in developer workflows through metrics, surveys, and incident data.</li><li>Drive adoption of DevEx improvements by partnering with engineering teams, running enablement sessions, and monitoring uptake.</li><li>Establish feedback loops to validate impact (e.g., reduced build times, improved developer satisfaction).</li></ul></ul><p></p><h3><strong>What You Won’t Do</strong></h3><ul><li>Define test strategy, coverage, or quality gates (owned by engineering teams).</li><li>Own microservice/domain documentation.</li><li>Dictate coding practices (linting rules, frameworks, languages).</li></ul><h3><strong>What We’re Looking For</strong></h3><ul><li>Proven experience with CI/CD platforms (e.g., GitHub Actions, GitLab CI, CircleCI).</li><li>Strong background in SDLC practices and developer productivity tooling.</li><li>Hands-on experience with infrastructure automation (e.g., Docker, Kubernetes, IaC with Terraform, Ansible or Pulumi).</li><li>Familiarity with observability &amp; monitoring (Datadog, Prometheus, or similar).</li><li>Experience managing or improving monorepo build systems.</li><li>Strong ability to measure developer productivity gaps and define KPIs.</li><li>Experience in driving adoption of change in engineering organisations.</li><li>Excellent communication skills and a collaborative mindset.</li></ul><h3><strong>Nice to Have</strong