Life at Wriggy

Engineers who see the whole stack

Small enough that an engineer touches the firewall, the switch, the hypervisor and the customer conversation in the same week.

The work

Estates, not tickets

Most of what we do is visible. A branch network that stays up, a room that passes an audit, a migration that finished on the weekend it was supposed to. People here can point at things and say they built them.

  • Real estates across fourteen states, not a simulated lab
  • Exposure to competing vendors rather than one stack
  • The engineer who designs it is usually the one who builds it
  • Site work, not only remote hands on a keyboard
  • Projects with a cutover date and a handover pack
Learning

Certifications we pay for

Holding competing authorisations means the certification load is real. We carry it because the business depends on it, which means the training budget is not the first thing cut.

  • Vendor certification funded, including exam re-sits
  • Time allocated for study, not expected after hours
  • Recertification tracked so nothing quietly lapses
  • Shadowing on practices outside your own
  • Senior consultants who are expected to teach, not hoard
How we work

Small teams, named owners

Nobody disappears into a pool. Engagements have named owners and small teams, which means credit and accountability both land somewhere specific.

  • A named owner on every engagement, at every level
  • Small teams that see a project from survey to handover
  • Direct access to leadership without three layers
  • Decisions explained rather than announced
  • Mistakes reviewed for cause, not for blame
The other side

What this job actually involves

Worth saying plainly, because the wrong expectation helps nobody.

  • Field work means travel, sometimes at short notice
  • Cutovers happen at weekends and at night, by design
  • A 24×7 NOC means shift work for the people on it
  • Client sites vary from corporate offices to plant floors
  • Documentation is part of the job, not an afterthought
Joining

What we look for

Certifications help. What matters more is whether you can explain a design to someone who is not technical, and whether you finish the documentation.

  • Curiosity about how the whole estate fits together
  • Willingness to say when a design is wrong, including ours
  • Clear written communication in English and in the field
  • Ownership through to handover, not just to deployment
  • Respect for the site, the client and the people on it
Next step

Tell us what you are running today

We will tell you what we would change, and what it would cost. No obligation, and a named engineer on the call rather than an account manager.