Skip to content
[YOUR NAME]

Open to technical leadership roles

IT Manager · Software Architect · Technical Lead

[YOUR NAME]

I connect business strategy with well-designed systems and teams that deliver.

I combine IT management, software architecture and hands-on development to turn business goals into reliable, maintainable platforms that are ready to scale.

Placeholder profile photo of Arnau Llull
Placeholder photo

Highlights

years in technology and software
20
teams or projects led
10+
primary sector or industry
Tourism / IoT
working languages
CA · ES · EN

01Expertise

Three levels of work, one goal: systems that serve the business.

My profile is hybrid by design. I move between strategic decisions, technical design and implementation, which shortens the distance between what gets decided and what gets built.

  • IT Strategy & Leadership

    Aligning technology with business priorities and creating the conditions for teams to deliver autonomously.

    • Technology roadmaps aligned with objectives
    • Prioritisation and technical portfolio management
    • Coordination with business, product and vendors
    • Team development and engineering culture
    • Risk, budget and technical debt management
  • Software Architecture & Engineering

    Designing systems with clear boundaries, documented decisions and explicit trade-offs between cost, performance and maintainability.

    • Modular and service-oriented architecture design
    • API design and integration contracts
    • Data modelling and multi-tenant systems
    • Security, observability and reliability by design
    • Architecture decision records (ADRs)
  • Full-Stack Development & Delivery

    Writing code where it adds value and taking work all the way to production with quality, automation and fast feedback.

    • Frontend and backend development
    • CI/CD pipelines and deployment automation
    • Testing strategies and code review
    • Incremental delivery and scope management
    • Engineering standards and technical documentation

02Case studies

Representative work

Three concepts that illustrate the kind of problems I work on. Each case outlines the context, the technical approach and the outcomes that should be validated with real data.

Sample content pending owner validation. It does not represent real results.

  1. 01Illustrative concept

    Multi-tenant IoT monitoring platform

    Real-time telemetry ingestion, dashboards and per-customer customisation on a single platform.

    Technologies

    • MQTT
    • PostgreSQL
    • Node.js
    • TypeScript
    • React
    • Docker

    Context

    Several customers need to monitor field devices with their own visualisation, alerting and integration requirements, without multiplying maintenance costs.

    Approach

    • Telemetry ingestion over MQTT with message validation and normalisation
    • Multi-tenant data model in PostgreSQL with per-customer isolation
    • Configurable dashboards and alert rules per tenant
    • Integration layer with third-party systems via APIs and webhooks

    Outcomes to validate

    • [Time to onboard a new customer]
    • [Volume of messages processed]
    • [Observed availability or latency]
  2. 02Illustrative concept

    Cloud-ready software architecture

    Modular services, well-defined APIs and an operational foundation designed to evolve safely.

    Technologies

    • REST
    • OpenAPI
    • Docker
    • Kubernetes
    • OpenTelemetry
    • Terraform

    Context

    A system growing in features and users needs a structure that allows it to evolve in parts, deploy with confidence and diagnose problems quickly.

    Approach

    • Decomposition into modules and services with clear responsibilities
    • Versioned API design with documented contracts
    • Authentication, authorisation and secrets management as baseline requirements
    • Observability through structured logs, metrics and traces

    Outcomes to validate

    • [Deployment frequency]
    • [Mean time to diagnose incidents]
    • [Impact on infrastructure costs]
  3. 03Illustrative concept

    Technical delivery & platform modernisation

    Engineering standards, CI/CD and pragmatic technology choices to improve delivery without stopping the business.

    Technologies

    • GitHub Actions
    • Automated testing
    • Docker
    • SonarQube
    • Linux

    Context

    An existing platform has accumulated technical debt and manual processes that slow down delivery and increase the risk of every change.

    Approach

    • Defining coding, review and documentation standards
    • CI/CD pipelines with automated tests and reproducible deployments
    • Incremental modernisation prioritised by risk and value
    • Collaboration practices across teams and with the business

    Outcomes to validate

    • [Reduction in lead time]
    • [Change failure rate]
    • [Team satisfaction or autonomy]

03Technology

Tools I work with

An editable selection grouped by area. I choose technology based on the problem, the team and the long-term cost of maintaining it.

Web engineering

  • TypeScript
  • JavaScript
  • React
  • Next.js
  • HTML & CSS
  • Tailwind CSS

Backend systems

  • Node.js
  • Python
  • REST APIs
  • GraphQL
  • MQTT
  • Messaging & queues

Databases

  • PostgreSQL
  • MySQL
  • Redis
  • Time-series data
  • Data modelling

Cloud

  • AWS
  • Azure
  • Vercel
  • Serverless architecture
  • Networking & DNS

DevOps

  • Docker
  • Kubernetes
  • GitHub Actions
  • Terraform
  • Observability
  • Linux

Security

  • OAuth 2.0 / OIDC
  • OWASP Top 10
  • Secrets management
  • Access control
  • Encryption

Editable list: adjust it to your actual experience.

04Professional approach

How I approach every project

A simple, repeatable process that reduces risk and keeps the focus on the outcome rather than the tool.

  1. 01

    Understand the business problem

    Before proposing solutions, I clarify goals, constraints, users and success criteria with the people involved.

  2. 02

    Design the architecture

    I define boundaries, data and integrations, and document key decisions together with their alternatives and trade-offs.

  3. 03

    Build incrementally

    I deliver in small, verifiable steps to get early feedback and adjust course with real information.

  4. 04

    Validate quality and security

    I automate tests, reviews and security checks so that quality does not depend on individual effort.

  5. 05

    Deliver maintainable solutions

    I leave systems documented, observable and understandable so the team can operate and evolve them.

05About

Background

I'm [YOUR NAME], an IT professional with experience in [MAIN AREAS]. Throughout my career I have worked across technology management, systems architecture and software development.

I am drawn to problems where technology has a direct impact on the business, and to teams where technical decisions are made with sound judgement and explained clearly.

[Add a paragraph here about your motivation, leadership style or the kind of role you are looking for.]

Editable text: replace the bracketed placeholders.

Experience

  • [CURRENT ROLE]

    [COMPANY]

    [Short description of responsibilities and scope.]

    [YEAR] — Present

  • [PREVIOUS ROLE]

    [COMPANY]

    [Short description of responsibilities and scope.]

    [YEAR] — [YEAR]

Education

  • [DEGREE]

    [UNIVERSITY OR INSTITUTION]

    [YEAR]

Certifications

  • [CERTIFICATION]

    [ISSUING BODY]

    [YEAR]

06Contact

Shall we talk about your next technical challenge?

I'm open to conversations about IT Manager, Technical Lead, Software Architect or Engineering Lead roles. Email is the most direct way to reach me.

Send an email
Résumé
Download PDF
Location
[YOUR CITY, COUNTRY]