Home / Services
Available for contract · six to twelve months · remote
Senior UX and UI designer, for the products where the domain is the hard part.
Over ten years inside large organisations: insurance, telecom, public administration, fleet software, virtual events. Forty risk datasets an analyst cannot read at once. A network contract measured in seconds per month. A public service organised by department for a person who only has a problem.
I take six to twelve month engagements, embedded in your team rather than orbiting it. Part time or full time, fully remote, EU citizen, contracting through my own company. If you are filling a role, everything you need to decide is in the next block.
This page is the specification. Two role titles I answer to, what a contract with me looks like, and the methods and tools underneath.
UX and UI design is deciding what a product puts in front of somebody, in what order, and what it leaves out, then designing how that looks and behaves. Product ownership is deciding what gets built next and what does not, and being answerable when it ships. Most senior roles in enterprise teams are a mix of the two, which is why both are here.
What to put me forward for
One title I have held for over ten years. One I have done without the title.
Both are real, and I would rather be straight about which is which than have it come out on a screening call. The design role is where the evidence is heaviest. The product role is where the last three years actually went.
The difference between senior and mid
Problem, evidence, call, outcome. In that order, every time.
Anybody can draw the layout. What you are hiring at this level is the decision about what goes on it, and the ability to say afterwards what it was for, what was known at the time, and what happened. Four engagements, four industries. Switch between them.
Where I fit
Large organisations, complex domains, distributed teams.
Not a preference, a track record. Every engagement below happened inside a company with more than one department that had to agree, an engineering organisation that was not in the room, and a domain that took weeks to understand before anything could be drawn.
Five nines, reinsurance layers, procedural public services, fleet telematics. I am used to being the person who has to learn the business before being useful, and I do not mistake having learned it for the user having learned it.
Public administration meant three services in parallel, four stakeholder groups and fourteen months. Ericsson meant a design system negotiated with a central team in Sweden. Getting agreement is part of the job, not an obstacle to it.
Backend, DevOps and QA have all put their names to how I work with them. I hand over specification, not inspiration, and I stay reachable through the build, because that is when the decisions that matter actually get made.
A normal week
What I am actually doing on a Tuesday.
Standups, refinement, planning, retros. Agile since 2017, in teams that ran it properly and teams that said they did. Design that arrives at sprint planning has already lost the argument.
No reveal, no big presentation. The team sees the version I do not like yet, because that is the version worth talking about and the only one anyone can still change cheaply.
Available for the questions that come up mid-build, reviewing what got made against what was specified, and changing the spec when the constraint turns out to be real.
Stakeholders get the reasoning and the evidence, not the mood board. A decision that cannot survive being explained to the person paying for it is not a decision yet.
The full list
Twenty-seven methods, and the discipline to not run most of them.
Listed because you may be matching against a specification that names one of them. Worth saying plainly though: a method is chosen after the question is agreed. Running a card sort before knowing what you need to find out is how research budgets get spent on answers nobody needed.
Before you put me forward
The things a recruiter needs answered first.
How do you contract, and can you work here?
Through Luis Landi Unipessoal Lda, my own Portuguese company. Direct with the client or through your agency, whichever your process needs.
I am an EU citizen, so there is no visa, permit or sponsorship to arrange anywhere in the EU, and no right-to-work question to escalate before you can put me forward.
Part time really, or is that a formality?
Really. Part time through to full time, agreed before the contract starts rather than renegotiated in month three. If I am at capacity I will tell you on the first call instead of stretching across your role and somebody else's.
Fully remote, or do you travel?
Fully remote, European working hours, and I have worked remotely with distributed teams since 2021. Travel for a kickoff or a workshop is fine and usually worth it, but the engagement does not depend on it.
Languages?
English, Italian and Spanish. Over ten years of work has been in English, including four years in Ireland, so an English-speaking team is the normal case and not an accommodation.
References?
A product owner, a backend engineer, a DevOps engineer, a lead designer and a recruiter have all written about working with me, and they are on the About page in full. Deliberately not only designers.
When could you start?
Get in touch and I will give you a real date. I would rather tell you on a call than print one here and let it quietly go stale, which is what every availability line on every freelancer site eventually does.
Looking for a small piece of work rather than a contract?
A one-off landing page, a small business that needs its calls answered and its jobs booked, a website for a trade. That is not this page, and pretending otherwise wastes your time. ParrotB is the product I built for exactly that, and it is a better answer than my hourly rate.