Network Engineer

Before you apply

• We're direct about how we work. Read this section first.
• This is a small team and you will own the network. There is no tier one to escalate to. When a site goes dark, you are the person who finds out why.
• Some of this is on site. Factory floors, gates, warehouses. You will occasionally be the person tracing a cable in a place with bad lighting and worse documentation.
• We value people who know what they don't know, and say so. If you're honest about your gaps, we'll invest in closing them. If you hide weaknesses or oversell your experience, you won't last here.
• We move fast. Growth happens outside comfort zones. If this sounds harsh, we're probably not a fit. If it sounds like the work you have been waiting for, keep reading.

The role

Allerin builds AI and IoT products. Edge to cloud video intelligence, computer vision systems, and data platforms. Those products live at the end of a network, usually somebody else's, and when the network is wrong the product is blamed.

You own that network. Our own estate, the links out to client sites, and the site networks we put in. A camera that drops one frame in fifty looks like a model problem until somebody looks at the switch, and that somebody is you.

What you'll own

• Client site networks: segmentation, VLANs, addressing, and the switch that has to carry a dozen camera streams without dropping any of them.
• Getting video off site: working out what a link can actually carry, what happens at peak, and what the fallback is when the line goes down.
• The boundary: firewalls, VPNs, and rules somebody other than you can read six months later.
• Names and addresses: DNS that resolves, DHCP that behaves, and knowing what breaks when a resolver goes away.
• Monitoring that tells you first: you should know a site is degrading before the client calls. Whatever you build, you will be the one woken by it, so build it accordingly.
• Writing it down. A site nobody has documented is a site nobody else can fix.

Where this role stops

We also have a Linux System Administrator. They own the servers, the virtualisation and the services running on them. You own what connects them and what connects us to a client. There is overlap at the edges and we expect you to work it out between you rather than throw things over a wall.

What you must arrive with

We do not require a certification and we do not count years.

• You understand what actually happens when a packet does not arrive, and you can prove where it stopped rather than guess.
• Routing, switching, VLANs and subnetting well enough to design a small site, not just repeat the theory.
• Firewalls and NAT, including why a rule that looks right does not work.
• DNS and DHCP, and the confidence to say when the problem is name resolution rather than the network.
• You can read a packet capture when it comes to that.
• Enough Linux to diagnose from a server rather than only from a switch.

A GitHub account is required to apply. We are not counting stars. Scripts, configuration, a tool you wrote to stop doing something by hand, notes on a build you did. Network work leaves less public trace than software does, so a small honest repository is entirely enough.

Nice to have

• Video or CCTV networks, and the bandwidth arithmetic that goes with them
• Proxmox or any virtualisation networking you have configured rather than clicked through
• Network automation in Python or Ansible
• Wireless in an industrial setting, where the interference is real
• Certifications, and we will read them, but they will not decide anything on their own

What we offer

• Real ownership of real networks, not a ticket queue
• Sites you can design rather than inherit
• A team that would rather you fixed the cause than the symptom
• Investment in your growth if you're honest about where you need it

How we hire

Apply through the form. Seven questions, six of them required, and they are about things you have done.

If we talk, we will describe a site that is misbehaving and watch how you narrow it down. There is no single right answer and you will not be asked to recite command syntax.

A human reads every application, and answers that read as model-generated are tested in depth in that conversation, where they do not survive.