Terra Technologies Let’s talk

Who we are

A narrow role, described honestly.

We are small, we hire rarely, and the job is unusual enough that it suits very few people. Here is the honest version. [Draft copy]

The shape of the work

You would scope the work and then deliver it. There is no bench to hand to and no junior tier to absorb the parts nobody wants, which means the range is wide: architecture on Monday, a control mapping on Tuesday, pairing with a client engineer on Wednesday.

A large part of the delivery is AI-assisted, and the skill that matters is not prompting. It is specification, review and knowing when the output is subtly wrong. [Draft copy]

Who it suits

  • People with real enterprise programme exposure who are tired of the pyramid.
  • People who write well. A great deal of the deliverable is a document somebody has to be able to act on.
  • People comfortable saying "I do not know" in front of a client, and then finding out.
  • People who would rather own four things end to end than one thing at scale.

Who it does not suit

  • Anyone who wants a defined lane. There is not one.
  • Anyone who wants to specialise narrowly. The engagements are too varied.
  • Anyone who needs a large team around them. Some weeks it is you and a client.
  • Anyone who wants a title trajectory. We are too small to offer one honestly.

[Draft copy] — confirm the firm is comfortable publishing all four.

The associate network

Most of the people we work with are not employees. They are seniors we have delivered with before, engaged against a defined scope rather than to fill a seat, who keep their own practice the rest of the time.

If that is the arrangement you want, it is worth a conversation even when nothing is advertised. [Draft copy]

How to apply

There is no form. Write to us at consulting@terra-tech.io with something you have built, written or fixed, and what you thought was hard about it.

[Client to supply] — confirm the careers contact address and whether open roles are listed here or handled through the network.

Tell us what you are being asked to prove.

No open roles listed does not mean no conversation. If the work sounds like yours, write.

Start a conversation