Data
Platform Core
Reliability
Python
Azure
ML/AI
Pipelines
Ontology
SQL
Claude
GPT
{ }
=>

Join TACo

Platform Engineer

July 2026

OverviewResponsibilitiesAbout youFirst 90 daysBenefits

The role

We're looking for a deeply technical Platform Engineer to own the backend and infrastructure heart of HYDRA — the systems everything else runs on. This is the most load-bearing engineering role at TACo. You'll own the data platform, the services, and the deployment infrastructure that turn millions of operational data points into a fast, reliable, multi-tenant product, and you'll lead the single most important delivery of our year: migrating every customer onto our next-generation platform.

At TACo, we're building HYDRA, our AI-powered operational intelligence platform serving customers operating complex physical environments across Africa. This role owns the platform foundations HYDRA stands on: the data layer, the core services, authentication, scale and reliability, and the CI/CD and cloud infrastructure that ships it all.

This is not a role for someone who wants tickets handed to them. You'll be the technical authority on backend platform and infrastructure, working directly with the CTO to make the architectural calls that determine whether HYDRA is fast, stable, and scalable — or not.

Above all, you work AI-first. We are a heavily AI-leveraged engineering team — Claude Code, Cursor, Codex and Copilot are core to how we build, not curiosities. We expect an experienced engineer using these tools to reach completion several times faster than the same engineer without them. You bring the judgement, architecture, and verification; AI carries much of the build.

You'll be part of a lean, high-agency startup team where your work directly determines whether customers get a platform they can rely on.

Current Tech Stack

Backend: C# .NET, Razor MVC, Azure Functions, Entity Framework — migrating C# .NET Core 3.1 → .NET 8 and Azure Functions v3 → v4
Data: SQL, NoSQL; a new read-optimised data layer is being introduced as the queryable substrate
Cloud: Azure — Functions, Key Vault, Entra ID (Azure AD); AKS / Container Apps / App Service — you'll make the platform compute call in your first month
Auth: Migrating off IdentityServer4 (end-of-life) to a modern SSO + passwordless stack
Frontend (context only, not owned by this role): Vue.js today, moving to React; Mapbox
Languages: C#, Python, JavaScript
AI tooling in the build pipeline: Claude Code, Cursor, Codex, Copilot — actively used across plan, build, and ship

You'll have real influence to evolve this stack — and you'll inherit some deliberate architectural decisions already made.

What you'll do

01

Platform & Data Architecture

✓

Own HYDRA's backend platform: the core services, the data layer, and the contracts everything else depends on

✓

Build and harden the new read-optimised data foundation — the substrate that makes real-time operational queries fast at scale

✓

Design and optimise data pipelines ingesting from diverse sources: telemetry, WhatsApp, field agents, documents, and third-party systems

✓

Fix and prevent the failure modes that take platforms down — connection-pool exhaustion, query amplification, cache concurrency, unbounded load

✓

Build the rules engine and event infrastructure that alerts and automations ride on

02

DevOps, Infrastructure & Reliability

✓

Own the CI/CD pipeline, infrastructure-as-code, and deployment path for all backend services on Azure

✓

Own observability — metrics, logging, alerting, dashboards — so we detect ingestion lag, disconnects, and failures before customers do

✓

Carry primary incident response for the platform — we keep incidents rare by design, but when it breaks, you're the one who knows why

✓

Set and hold the reliability, performance, and scale targets as customer and data volume grow

✓

Manage secrets, service-to-service identity (Entra ID / managed identity), and the security posture of the platform

✓

Write and own the runbooks that make the platform operable by the whole team (and our AI agents), not just by you

03

The Platform Migration (your headline deliverable)

✓

Own the migration of all 100+ existing customers onto our next-generation platform — the single most important delivery of the period, targeted within your first 90 days

✓

Build and validate the shadow-run, the migration scripts, the rollback plan, and the cutover

✓

Deliver the auth overhaul: migrate off end-of-life IdentityServer4 to modern SSO + passwordless, coupled with the .NET 8 and Azure Functions v4 runtime upgrade

04

AI-Leveraged Delivery & Technical Leadership

✓

Build AI-first: use Claude Code, Cursor, Codex and Copilot as core tooling to deliver at multiples of conventional pace, while keeping full ownership of architecture, judgement, and verification

✓

Help extend our AI leverage from the build stage into testing, review, and operations

✓

Set technical standards for backend, data, infrastructure, and DevOps across the team

✓

Partner with the CTO on architecture and with the frontend and AI engineers on the contracts between their work and the platform

About you

Critical skills (must-have)

✓

A degree in Computer Science or Engineering (or equivalent depth) — for this role we place real weight on strong technical foundations, and give preference to formally qualified candidates. We test for depth, not paper — but the foundations must be there

✓

Substantial experience building and operating backend platforms and data systems in production — enough depth to own a platform end-to-end, with clear ownership of scale and reliability

✓

A doer, first and foremost — still hands-on and shipping code every day. We want a builder at the centre of the platform, not someone who has moved into managing builders. You lead through the work

✓

Current with modern tooling and AI-native workflows — you keep up with how engineering is changing and you build the way the best teams build today, not the way they built five years ago

✓

Deep C# / .NET expertise and the backend depth to own a platform end-to-end — services, data layer, performance

✓

Strong DevOps / platform-ops: CI/CD, infrastructure-as-code, cloud deployment, observability, incident response — you build it and you run it

✓

Serious SQL and data-layer performance skill — query optimisation, connection management, caching, the ability to diagnose and fix a platform buckling under load

✓

Demonstrably AI-first in how you build — you use Claude Code / Cursor / Codex / Copilot (or equivalents) as a core part of your workflow and can show how they multiply your output

✓

Migration experience — you've moved real customers/data onto new architecture without losing either

✓

Autonomous, high-agency operator who thrives with ambiguity and a ‘figure it out’ mandate

✓

Excellent technical communicator who can absorb, transfer, and document deep context — you'll own a platform others depend on, so keeping it legible matters from week one

Important skills

✓

Azure in depth: Functions, Key Vault, Entra ID, and a container/compute platform (AKS, Container Apps, or App Service)

✓

Distributed-systems patterns: caching, queues, event-driven architecture, idempotency

✓

Auth systems: OAuth/OIDC, SSO, passwordless; experience migrating an auth provider

✓

Multi-tenant SaaS architecture and tenant-isolation enforcement at the data layer

✓

Runtime/framework upgrades on live systems (e.g. .NET major-version migrations)

Nice to have

✓

Experience building or consuming projection / CQRS-style read models

✓

Rules engines and event-processing infrastructure

✓

Industrial IoT, property tech, or infrastructure data at scale

✓

African tech ecosystem experience

✓

A track record of introducing AI tooling into a team's engineering practice

Dealbreakers

This role is not a fit if:

✓

You're primarily a frontend or applications developer without deep platform/data/infra ownership

✓

You've never owned deployment, reliability, or operations (this is a build-and-run role)

✓

You treat AI coding tools as a novelty rather than core to how you work — our estimates and timelines assume heavy AI leverage

✓

You need detailed specs and hand-holding, or you're uncomfortable with ambiguity and rapid iteration

Your first 90 days

1

Month 1: Get Deep, Own, Stabilise

✓

Get deep on HYDRA's architecture fast — the data model, the services, the deployment path, the known failure modes, and the in-flight platform work — working closely with the CTO

✓

Take ownership of the platform: services, data layer, CI/CD, cloud infrastructure, observability

✓

Get deep on the new platform architecture and the migration plan already in motion

✓

Ship an early reliability win — close out the known scale/performance issues so the platform is solid going into the migration

2

Month 2–3: Deliver the Migration

✓

Own the shadow-run, validation, scripts, rollback plan, and execution of the migration — all customers onto the new platform, zero data loss, targeted within your first 90 days

✓

Deliver the auth overhaul (off IdentityServer4 to SSO + passwordless) and the .NET 8 / Functions v4 runtime upgrade

✓

Stand up the observability, alerting, and runbooks the platform needs for launch-grade operation

✓

Establish the CI/CD and infra-as-code standards the whole team builds against

✓

Document the platform so it's owned by the team, not trapped in one head — resilient, maintainable, and extensible by the wider team

3

Success by Day 90

✓

All customers migrated onto the new platform with no data loss — the migration landed

✓

The platform is fast, observable, and reliable at v1-target load, with the known incident classes designed out

✓

Auth and runtime upgrades shipped

✓

CI/CD, infrastructure-as-code, monitoring, and runbooks are in place and owned across the team

✓

You are the technical authority on the HYDRA platform — and the context is documented, not fragile

Self assessment

If most of these feel like a confident yes, you'll likely thrive here.

Have you owned a production backend platform end-to-end — services, data, deployment, and operations?

Have you migrated real customers or data onto a new architecture without losing either?

Have you diagnosed and fixed a platform failing under load, down at the query and connection level?

Do you own DevOps as part of your work — CI/CD, IaC, observability, incident response?

Do you build AI-first, using tools like Claude Code or Cursor as core to your pace?

Are you comfortable being the technical authority for the platform?

Can you absorb deep context fast and start owning it within weeks?

Can you work autonomously in a lean startup with high agency?

What we offer

Technical Authority — Own the core platform. Your architectural decisions determine whether HYDRA is fast and reliable.

The Headline Deliverable — Lead the platform migration: the most important engineering delivery of our year.

Hard Problems — Scale, multi-tenancy, projections, migrations, reliability under real-world load.

AI-First Engineering — Work on a team that genuinely builds with AI at the core and is pushing that leverage further into testing and ops.

Real-World Impact — Power operational and sustainability decisions across Africa's complex physical environments.

Startup Velocity — Ownership, autonomy, and pace, at a funded startup at an inflection point.

Team & Culture — A lean, high-agency team collaborating in person at our Fourways office, 4x per week.

About TACo

The Awareness Company (TACo) is a South African AI startup building HYDRA: AI for the physical world. We're creating the operational intelligence platform that helps organisations running complex physical environments make better decisions through live data, smart analytics, and automated insights.

We serve B2B customers across Africa — from property portfolios to mining, rail, and critical infrastructure — helping them optimise operations, improve sustainability performance, and unlock financial value from their physical assets. From energy and water management to security and workforce optimisation, HYDRA turns operational data into strategic advantage.

While most AI companies focus on digital-first use cases, we're tackling the harder problem: bringing intelligence to the physical world of buildings, infrastructure, and industrial operations. We combine IoT integration, data engineering, and AI/ML to create a platform that works in the real world, not just in the cloud.

Why now? We're scaling our technical foundation to serve enterprise customers across the continent — and moving every customer onto our next-generation platform this year. You'll own that. Your technical decisions have outsized impact.

Apply now to own the platform at the heart of HYDRA.

Open position

Platform Engineer

Position

Platform Engineer (Backend · DevOps · AI-Leveraged)

Employment Type

Full-time, long-term contract (renewable annually)

Reporting

Reports to the CTO; sets the technical direction for the platform lane

Start

As soon as possible