Since 2022
Migrated to AWS, the employer this time, not just the cloud
- Zero-downtime migration from consulting to cloud advisory.
- Now professionally invested in other people’s architectures staying up.
- Monitoring: enabled. Meetings: auto-scaling.
Luís Marques
Technical Account Manager (TAM) @ Amazon Web Services (AWS)
Polyvalent problem-solver with 20+ years of turning “it’s broken” into “it works, don’t touch it”.
Uptime
100%*
*measured since you opened this page: and counting
Region
eu-alps-1
Martigny, Switzerland. Not a real region. Yet.
Day 1
× 1473
consecutive Day 1s at AWS since September 2022. Yes, they are all Day 1. I checked, it’s in the culture.
Open incidents
0
Everything below is resolved. Career postmortems available.
Components
Cloud advisoryOperational
Answering “it depends” with 99.99% consistency.
eCommerce expertiseOperational
Legacy support mode. Magento memories retained for compliance reasons.
LanguagesOperational
PT native · EN fluent · FR fluent · ES still being promoted from alpha to beta.
Availability zonesOperational
Three cantons served so far: Valais, Vaud and Geneva. Cross-zone latency: one train ride.
Coffee intakeElevated
By design. A Nespresso stint left permanent configuration changes.
SarcasmOperational
100% uptime since initial boot. Cannot be disabled.
WeekendsMaintenance
Scheduled maintenance windows: hiking, family, and walking a dachshund whose legs do not match the terrain. The Alps are the runbook.
Uptime history
One bar per year of professional service. Hover, tap or tab through the bars. Split bars are years that ran two engagements at once.
Support channels
Route your request according to severity and how well you know me.
Ping
ICMP is disabled for security reasons. Email works though.
Response time: a few business coffees.
Send email →You know me professionally
Cloud, eCommerce, or “quick question” that never is.
SLA: business hours, Swiss punctuality.
Open LinkedIn →You know me personally
Mountains, a dachshund, and the occasional proof I leave the terminal.
Best-effort delivery. No SLA whatsoever.
Open Instagram →Incident history
All incidents resolved. Root cause analysis: curiosity.
2018 to 2022
Failover to agency life
- New employer, same client for a while: the Nespresso engagement carried on into 2018, which is why the two incidents overlap.
- Promoted from debugging code to debugging projects, and occasionally humans.
- Led local and nearshore teams on Adobe Commerce, standard and headless.
- Deprecated: writing PHP at 2am. Mostly.
2016 to 2018
Deployed to Nespresso. What else?
- On site as an external consultant, so the engagement outlived the contract that started it.
- Rolled out storefronts to markets worldwide, cross-channel and cross-platform.
- Learned that enterprise Java and espresso pair surprisingly well.
- Side effect: coffee intake permanently reclassified as “elevated”.
2012 to 2016
Self-hosted mode: freelancing
- Ran eCommerce platforms, campaigns and analytics for European retailers.
- One-person on-call rotation. Escalation path: also me.
- Shipped a PrestaShop module to the public marketplace, because why not.
2003 to 2012
Initial deployment: Portugal
- Booted in part-time mode while studying: selling machines, fixing machines, then repairing the network the machines had upset.
- Promoted to full deployment: bespoke PHP/MySQL sites and eCommerce for clients in Portugal, Italy and Germany.
- Same badge, second hat: hybrid Windows/Linux networks, ERP rollouts, and an intranet nobody ever filed a ticket to thank me for.
- The era of fixing computers for everyone, including the neighbours. Root cause of everything that followed.
1988
Initial boot
- Cold start in Portugal, no documentation provided.
- Shipped with bugs. Still patching.