IT, Data & Security Professionals

Support, infrastructure, data and security are different jobs

This family brings together people who keep the technology running and people who work with data and defence. A service desk manager leads the people who answer user problems. A systems administrator keeps servers, identity and productivity tools in order. A network engineer builds and maintains connectivity. A cloud engineer runs workloads in hosted environments. A cybersecurity analyst watches for and responds to threats. Data analysts, business intelligence developers and data engineers work with information.

Each of these has its own pool. A person who is excellent at user support may know little about network design. A data analyst may not be able to build a pipeline. Name the problem, not just the department.

If you are unsure what you need, describe the symptoms: users cannot connect, reports disagree, a scan found problems, systems are slow. We will help you turn those into a role.

Interim manager versus contract specialist

An interim service desk manager owns a team, its queue, its tools and its standards. They set priorities, handle escalations and improve how the team works. A contract specialist, such as a systems administrator, network engineer or analyst, performs defined technical work. They may do it very well and still leave the team structure untouched.

If your desk is chaotic because nobody leads it, a specialist will not help. If your environment is sound and you need an extra pair of expert hands for a migration, a specialist is ideal.

Single person IT environments need a generalist who can do a bit of everything. Larger ones need depth in one area. A brief that does not say which will produce profiles that fit neither.

Technical differences that matter

Platform matters. Experience with one productivity suite or identity system is not automatic experience with another. Hosted environments differ by provider, and a strong engineer in one will usually adapt, but the first period will show the difference.

In security, analyst work spans monitoring, investigation, policy and governance. A person who monitors alerts is not the same as someone who writes policy or prepares for an assessment. Frameworks vary by industry, and some roles require clearances or similar constraints.

In data, the difference between analysis, reporting and engineering is large. Analysts answer questions with data. Business intelligence developers build dashboards and models for ongoing use. Data engineers build the pipelines that move and clean the data. Mixing them up leads to mismatch.

Who we draw from and how we screen

We look at contract engineers who work between assignments, in house staff who moved to project work, former managed service staff and independent practitioners. Security and data people also come from consulting and from specialist teams.

Screening is hands on. We ask what they built or fixed last, how they diagnosed it, what they documented and what they would do differently. For security we ask for an example of an incident they handled and how they communicated it. For data we ask how they checked that numbers were right.

We also check clear writing and clear speaking. Technical people who cannot explain what they did create hidden risk for you.

Dependencies across the business

IT depends on the business telling it what matters. Security depends on leaders supporting unpopular controls. Data work depends on source systems producing reliable records and on business owners agreeing definitions. Without that agreement, two reports will always disagree.

Support also depends on onboarding and offboarding being communicated by human resources. Network work depends on facilities and vendors. Cloud work depends on finance accepting variable costs.

Tell us who will provide access, who decides priorities and who answers business questions. A specialist waiting for credentials or decisions is expensive idle capacity.

Briefing mistakes specific to IT

Common mistakes include asking for IT person with no scope, listing every tool you own as a requirement, and failing to mention security obligations. Another is asking a data analyst to fix data quality that needs upstream changes.

Briefs also forget documentation. If nobody has recorded how the environment works, the new person starts from scratch and may need access to find out. Say whether documentation exists.

Finally, be clear on authority. Can they change settings, buy tools, shut off access? If every action needs approval, the work will be slower and less effective, and candidates should know.

Questions to settle before you brief

Think also about hours and coverage. Some technology work happens in business hours, and some needs people on call or working outside normal times. Say which applies, because it changes the pool, and be open about whether work can be done remotely or needs a person on site.