codegang0077@gmail.com

Careers

A senior engineering team.Occasionally, one more.

We have no verified open positions today, so this page does not list any. Open applications are read by the founders, and the disciplines we hire into are below.

The team around a standing desk, mid-review of a pull request

500+

Projects delivered

most under NDA

20

Systems live

in production now

100+

Clients served

BR · AU · IN · US · EU

No verified figure to publish

Open roles

none posted today

Open roles

None posted right now. We do not keep evergreen listings open to collect résumés. When a seat exists it appears here with a scope and a salary band.

Disciplines

What we hire intowhen we hire at all

An open application against one of these is worth sending even with nothing posted.

Backend / AI engineering

Python and FastAPI, retrieval pipelines, model gateways, and the data modelling underneath them.

  • Python
  • FastAPI
  • PostgreSQL
  • pgvector
  • AWS

Full-stack product engineering

Next.js and TypeScript across multi-tenant platforms, with real ownership of the surface you build.

  • TypeScript
  • Next.js
  • React
  • Node.js
  • Tailwind

Mobile engineering

Flutter and native Android, offline-first sync, and store release engineering.

  • Flutter
  • Dart
  • Kotlin
  • Firebase

DevOps / platform

AWS architecture, containerisation, CI/CD, and the observability that makes an on-call rota humane.

  • AWS
  • Docker
  • Terraform
  • GitHub Actions

How we work

Small enoughthat your work is visible

Six things that are true of working here, including the ones that will not suit everybody.

Two engineers pairing over the retrieval layer during review

You own a system: Not a ticket queue. You take a system from scope to production and stay on it afterwards.

You talk to clients: There is no account layer between you and the person using what you built.

Your work is visible: Nothing you ship disappears into a monorepo nobody reads. It is in front of a client within weeks.

Review is written: Reasoning goes in the pull request, so decisions are inspectable months later.

Documentation is the job: Runbooks and handover docs are in the estimate, not squeezed in on a Friday.

Timezones overlap deliberately: We work across Brazil, Australia, India, the USA and Europe, and agree the overlap rather than pretending it is free.

Hiring process

Four steps,and the exercise is paid

Email

Send code we can read: a repository, a package, anything you actually built.

Conversation

Forty-five minutes with an engineer about what you built and why you chose it.

Paid exercise

A small, scoped piece of real work. Paid at our normal rate, and yours to keep.

Decision

A yes or a no with reasons, within a week. No silent pipelines.

The studio

Photographs pendingrather than stock photography

Studio, at work
Pairing: retrieval layer
Whiteboard: clinical schema
Ship day

Apply

Send something you built and why you built it that way

A repository beats a résumé. One paragraph on a decision you would now make differently beats a cover letter.