Engineering Team Lead - Cloud-Native Web Services

Our company Asiga (www.asiga.com) is an internationally recognised developer of 3D printing software and hardware. We are seeking an energetic technical lead run a small engineering team building and operating Asiga's cloud based services. These include automated 3D job setup and fleet management (www.asiga.com/funnel), automated AI assisted dental appliance design (www.asiga.com/genira), and cloud based patient data management systems. The role is full-time and based at our Alexandria headquarters in Sydney.

This is a hands-on lead role. You’ll still write code and review it, and you’ll also be the person responsible for how the team works: what it’s building, whether it’s shipping, and whether the people on it are growing. If you want to stop coding entirely, this isn’t the right role. If you want to code and never think about people or priorities, it isn’t either.

The stack is Go on AWS, with PostgreSQL, a mix of containers and serverless, Terraform for infrastructure, and Buildkite for CI/CD.

What you’ll be doing

• Leading the team. Regular 1:1s, honest feedback, growth conversations, and hiring when we grow. You’ll be the first person your team escalates to.

• Owning delivery. Turning roadmap intent into scoped, sequenced work. Saying what’s realistic, and flagging early when it isn’t.

• Staying technical. Design reviews, code reviews, and enough of your own delivery work that you understand the codebase you’re making decisions about.

• Running what you build. Your team owns its services in production — deployments, alerts, incidents and the follow-up work that stops them recurring.

• Working across the business. Product, support and other engineering teams. Translating in both directions.

What we’re looking for

Leading a small team

You’ve led a small team before — as an engineering manager, or as a tech lead with real people responsibility. You’ve run 1:1s, given feedback that was hard to give, and helped someone get better at their job.

Go, APIs and data

• You’ve shipped and maintained production Go services — not just written Go.

• You’ve designed HTTP APIs and evolved them over time: versioning, deprecation, and changing things without breaking existing clients.

• PostgreSQL beyond CRUD. Schema design, migrations, indexing, reading a query plan, and a working understanding of transactions and isolation levels.

• Redis (or Valkey, or Memcached) used in anger — caching, distributed locks, rate limiting.

AWS, serverless and event-driven systems

• Lambda, SQS, EventBridge, S3, DynamoDB, CloudWatch and IAM, with something real you’ve built on them.

• Async and long-running job design: retries, backoff, idempotency, and what happens when a job runs twice.

Containers and delivery

• Docker: you write your own images, and you know how to make them smaller with multi-stage builds.

• Kubernetes at a working level: deploy via charts, read logs, and diagnose a failing pod or a stuck rollout without needing a platform engineer.

• Terraform at a working level: make a scoped change to your own service’s infrastructure, read the plan, and understand it before you apply it.

• CI/CD as a normal part of your week. We use Buildkite; any equivalent is fine.

Testing and observability

• A considered approach to testing — unit level through to tests that exercise real dependencies — and a view on where the line sits.

• Structured logging, metrics and tracing. Familiarity with OpenTelemetry.

• You’ve debugged a real production incident and can walk us through how you narrowed it down.

Nice to have

None of these are required. Any of them are useful.

• Frontend. React and TypeScript — enough to make the customer portal change that goes with your API change.

• IoT and connected devices. AWS IoT Core, MQTT.

• Deeper infrastructure. Authoring Terraform modules, EKS administration, ArgoCD or other GitOps tooling, networking and VPN.

• 3D or geometry. Mesh formats such as STL, slicing pipelines, WebGL — or a C/C++ background, which is what our geometry libraries are written in.

• Cost awareness. Reading an AWS bill, S3 lifecycle policies and egress, right-sizing compute.

• Security. OWASP fundamentals, secrets management, WAF.

How to apply

Send us a CV and a short cover letter. Tell us about a system you led the build of, and one decision you’d make differently now.

Only applicants with permanent working rights in Australia need apply.