Information Technology Support Specialist

Role summary

We are backfilling our outgoing IT role, but reshaping it rather than replacing it like‑for‑like. The position moves away from a pure on‑site helpdesk seat toward the systems, automation, cloud and security work that the IT function increasingly depends on.

This is a remote role (South America preferred, for time‑zone overlap with Barcelona and cost fit), engaged as an independent contractor, working Barcelona business hours.

The profile we want is a solid‑fundamentals generalist: someone who can operate confidently across several areas rather than a deep specialist in any single one. Breadth, clean fundamentals, and a demonstrated habit of keeping their skills current matter more to us than seniority. This is a mid‑level hire — we expect gaps to be filled through on‑the‑job learning, so curiosity and self‑improvement are as important as the checklist below.

Core responsibilities

1. Google Workspace management

Day‑to‑day administration of our Google Workspace tenant and its subdomains.

• License management — keep our licensing balanced against actual need: track usage, reclaim licenses from offboarded users, and flag when we're over‑ or under‑provisioned so we don't pay for seats we don't use.
• Users, aliases and groups — create and maintain user accounts, keep email aliases tidy and correct, and manage Google Groups (membership, permissions, distribution lists).
• Security investigations — support internal security work: create and run Vault Matters to investigate suspected data leaks or incidents, keep the security alerts/notifications in the Admin console properly configured and monitored, and help implement and maintain SSO (SAML/OIDC) across the platforms we use.
• Onboarding / offboarding — execute our existing onboarding and offboarding SOPs reliably, improve those SOPs where they're weak or outdated, and progressively automate the process so provisioning and de‑provisioning are fast, consistent and auditable.

2. Automation

We run a growing automation stack and want to lean into it further.

• Grow our automation coverage — build out new automations that remove manual work across the business.
• Spot the opportunities — proactively identify repetitive, manual tasks that are good candidates for automation, rather than waiting to be told.
• Keep it healthy — troubleshoot and maintain existing automations when they break or misbehave, and do so without introducing fragility.

3. Cloud / IaaS

Ownership of our small cloud footprint, primarily on DigitalOcean.

• Deploy — stand up new instances as needed.
• Troubleshoot — diagnose and resolve issues on running instances.
• Maintain — keep instances healthy: patching, update cadence, basic hardening and housekeeping.
• Run the environment — comfortably maintain a small DigitalOcean environment end to end.

4. Containers

Practical, working container skills — enough to run and support our deployments, not container‑platform engineering.

• Deploy containers — bring containerised services up and down reliably.
• Small pipelines — set up and maintain simple deploy pipelines (e.g. push to a Git repo → deploy to production).
• Read logs — inspect container logs to understand what's happening.
• Use Portainer — operate our container environment through Portainer.
• Identify issues — recognise when something is wrong and where to look, escalating the genuinely deep problems.

5. IT security

A hands‑on contributor to the company's overall security posture, not a dedicated security specialist.

• Improve our posture — help raise the baseline security of the company over time.
• Educate — be able to explain and coach colleagues on security fundamentals (passwords/MFA, phishing, least privilege, safe handling of data).
• Identify concerns — recognise security risks and gaps as they come up.
• Assist mitigation — help remediate the issues that are found, working with the rest of the team.

6. General troubleshooting

• Solve problems across contexts — a general troubleshooting mindset that can adapt to different scenarios, tools and systems, and knows how to investigate methodically rather than guessing.

7. LLM literacy

We use LLMs as everyday working tools, and we want someone fluent enough to build and get things done with them — nothing research‑grade. Using Claude as the reference point, they should be comfortable with:

• Artifacts — creating and iterating on working outputs.
• Projects — organising and reusing context.
• Skills and agents — understanding the concepts and when to use them.
• Scheduled tasks — automating recurring work through the tool.
• In short: comfortable with essentially everything a good product tutorial would teach, and able to use an LLM to actually develop something (with a basic grasp of human‑in‑the‑loop and agent workflows).

8. Documentation

• Write concise, usable documentation — clear enough for others on the team to follow. This is a light requirement: someone who is genuinely fluent with LLMs can lean on them to produce and maintain documentation, so we're flexible here.

Requirements at a glance

Mandatory

• Google Workspace administration (users, apps, OUs, aliases)
• Automation experience (n8n, Zapier, Workato, or similar)
• Cloud / IaaS experience (DigitalOcean, AWS, GCP, or Azure)
• Docker (deploying containers, simple pipelines, troubleshooting)
• IT security fundamentals
• General troubleshooting
• Practical LLM literacy (able to build with an LLM; HITL and agent basics)
• Ability to write clear documentation
• Fluent English
• Able to work Barcelona business hours

Nice to have

• Proven experience with big automations
• Spanish

Differentials

• Any depth beyond the requirements above
• Post Graduation on an IT Related Field
• HubSpot or other CRM experience
• Certifications in any of the areas above

Education

• A higher‑education degree is desirable but not required. The field genuinely does not matter — strong IT people often come from non‑technical backgrounds.