Colleagues reviewing work together

Company

Good engineers, treated like adults.

We are a small team in Málaga building software, AI, cloud and security systems for organisations that depend on them. If that sounds like your kind of work, read on.

What the work is like

What you would actually be doing.

Talk to us

Real systems, real users

Software that people depend on during their working day, not internal demos.

Whole problems

You see a piece of work from the first conversation to running in production.

Range

Applications, integrations, cloud and security work across several sectors.

Time to do it properly

We spend real effort on specification and tests, because we are the ones who maintain it.

Direct client contact

You talk to the people who use what you build. It changes what you build.

EU-based, Málaga

Our office is on Calle Alejandro Dumas, and the working day is 08:00 to 17:00 CET.

How we hire

Four conversations, no trick questions.

  1. You write to us

    A short note and something you have built. A CV is fine but it is rarely the interesting part.

  2. A conversation

    Thirty minutes about what you have worked on and what you want to work on next. Both directions.

  3. Something technical

    A discussion about real problems, or a small piece of work if you would rather show than tell. We do not set puzzles you would never meet in the job.

  4. A straight answer

    Yes or no, with a reason, and quickly. Being left waiting is the most common complaint about hiring and the easiest to avoid.

Questions

Before you write.

Are there open roles right now?

We do not always advertise. We are a small team and we hire when we meet someone good, so an introduction is worth sending even when nothing is listed.

Do you take junior people?

Sometimes, when we have the capacity to teach properly. Taking someone on and leaving them unsupported helps nobody, so the honest answer depends on what the team is carrying at the time.

Remote or in the office?

We are based in Málaga and value being in a room together for the parts that need it. Tell us what you are looking for and we will be straight about whether it fits.

What should I send?

Something you built and a paragraph on what was hard about it. That tells us far more than a list of technologies.

Get in touch

Introduce yourself.

What happens after you send this

  1. A person reads it Every introduction is read by someone on the team, not filtered by software.
  2. A reply either way Yes or no, with a reason. Being left waiting is the easiest thing to avoid.
  3. Kept on file if you would like Tell us and we will come back to you when something fits.

We use what you send to reply to you, nothing else. Nothing is shared outside the team.

Tu experiencia en este sitio mejorará si permites el uso de cookies Política de cookies