Federico Kotek Product Designer

Federico Kotek is a product designer in Buenos Aires, working remotely on industrial software for Autodesk.

Product designer, builder, and a wannabe design engineer. years designing B2B software (which is a long stretch to spend on screens most people never see, but I digress). Right now that is Autodesk, where I work on asset intelligence for maintenance. Before the acquisition it was MaintainX, where the person using the app is standing under a broken conveyor with one hand free and a shift ending in twenty minutes.

Before that, card issuing infrastructure at Pomelo and delivery routing at Mercado Libre. These days most of my prototypes start in code, with a coding agent working next to me (or should I say in front?). I still think that if it needs a tutorial, it isn’t finished.

Read the case studies

Where I have worked.

Ten years across logistics, fintech and industrial software, most recently at Autodesk.

Read the full CV

Case studies.

Four projects from the last seven years. Each one opens into a full case.

Software for the people who fix the machines

MaintainX is the CMMS frontline industrial teams use to log work orders, track assets and keep plants running. I was lead designer on Reporting, Search, Automations and Chat, the parts of the app people open every shift.

I shipped Report Builder AI, which builds a report from a sentence typed in plain language. Since the acquisition I’ve been at Autodesk, working on asset intelligence and connected data strategy for maintenance.

Acquired by Autodesk, 2026

Read the case

CMMS Reporting & search AI Report Builder AI
Custom formulas, redrawn: a formula written with the columns’ letters, nested in a second, the table working both outCustom formulas Switching the chart, redrawn: the formula’s column as a pie, with the select that changes itThe formula as a chart The redesigned builder, redrawn: the table built a column at a time, the column list openBuild your table, live The first builder, redrawn: chart type first, a pie with two slots and the third column goneThe first builder Copilot, redrawn: a table of the most used parts built from a sentence, and the card that says it was generatedCopilot The template selector, redrawn: maintenance metrics filtered to work ordersTemplates The dataset step, redrawn: what a report can be about, with a tooltip on oneThe dataset step The Reporting page, redrawn: work-order widgets and the Create Report menuReporting The builder’s first door, redrawn: a prompt for Copilot, or a template, or by handThe first door Six close-ups of the builder: keys, chart types, Copilot’s orb, a formula column, live update, feedbackSix small things

The dashboard banks run their card programs on

Pomelo is fintech infrastructure for Latin America. I designed the partner dashboards, where banks and neobanks run their card and account programs, and grew them from a handful of partners to dozens.

As lead I ran the UX team, still designing Billing and Automations myself, and got us building reusable systems where we used to design feature by feature. The case study is about billing, which we moved from a spreadsheet to invoices built from each contract. On-time invoices went from 22% to 95%.

Read the case

Fintech-as-a-service Partner dashboards Design systems Led the UX team
The invoices, redrawn: February’s invoices as cards, one opened and its detail beside the listThe invoices The invoices in two tabs, redrawn: the ones still to issue, with what has accrued so far and the days left before each goes outIssued and still to issue Reporting a payment, redrawn: the bank’s details beside a code, and the receipt attachedReporting a payment Reporting a problem, redrawn: a reason chosen, a description typed, a file attached and the report sentReporting a problem A client’s detail, redrawn: its data, its contracts and its products, the id just copiedThe client list and detail The contract entry, redrawn: the price rules of a contract, with a list open on one of themThe contract entry The price addendum, redrawn: two prices retyped and a billing milestone chosen from its listThe price addendum Billing settings, redrawn: the modal where the day a client’s invoices go out is chosenHow invoices are sent A new invoice, redrawn: its data and two concepts filled in beside a preview of the invoiceA new invoice A credit note, redrawn: one concept ticked, its correction typed and the totals following itA credit note Six close-ups of the screens’ small things: an invoice’s state, a row’s actions, a feedback card, a copied number, switches and a tourSix small things

Routing the packages that used to go out in an Uber

Mercado Envíos is around 2M delivery assignments a day across six countries. The team I joined was new and had to build the router that would replace an external program. I gave exceptions a screen of their own, which cut daily exception resolution time by 40% and helped cut manual route planning by 70% across more than forty facilities.

Next to it I designed a simulator, where a planner runs a routing, compares it with earlier ones and only publishes the one they trust.

Read the case

Logistics Routing −40% exception resolution time
The routing detail, in motion The routing detail, redrawn: eleven routes in colour on the map, the packages left without a route in orangeThe routing detail The address fix, redrawn: a suggested address taken and the form filled inFixing an address Validating addresses, redrawn: the map flown to an address the tool could not place, with its suggestionValidating addresses The routing simulator, redrawn: a new simulation at the top of the listThe simulator The routing templates, redrawn: narrowed by filters to one template whose vehicles are openTemplates The import, redrawn: a thousand packages imported, and a button to carry onThe import A package’s detail, redrawn: its status changed and a new line in its historyA package The menu, redrawn, open on PlanningThe menu Six close-ups of the redrawn screens: a route’s capacity, hiding a route, an address placed, a suggestion taken, three states, an arrival worked outThe details

Letting each region set up its own facilities

Alongside routing I designed GT, four internal tools for coverage, transit times, capacity and the connections between facilities. Setting up a new facility used to take eleven days, configured by hand in Excel. We gave the tools to the people running each region, and it went down to under three hours.

I was the only designer, with thirty developers, so I wrote very detailed specs: every table, every state a configuration can be in, and what happens on every click.

Read the case

Internal tools Role-based IA 11 days → 3 hours
A facility’s connections, redrawn: its counts and donut, the first connection open on its departuresA facility’s connections A transport zone, redrawn: drilled down to its last node, its postcode ranges listedThe transport zones A service’s transit times, redrawn: the predictor switched on, a day taken off, the change savedThe transit times The shift schedule, redrawn: a departure loaded for the whole week at once, every day tickedThe shift schedule A special date, redrawn: the calendar and hours open on the 15th at 09:00The special dates A transport zone from a spreadsheet, redrawn: the upload done, the zone ready to be reviewedThe spreadsheet upload Notifications, redrawn: a GT approval just arrived on top of the listThe notifications The approval email, redrawn: a change of capacity waiting on its approver, line by lineThe approval email The capacity screen, redrawn: a destination being searched, the matching ones listed under itThe capacity screen

Fun side projects.

Things I make on my own time. Making them is how I learn fastest. All five are live, and each has a page of field notes on what I was after and what broke.

What I work with.

Most of my prototypes now start in code, with a coding agent working next to me. This site was designed and built that way, down to the checks that keep it on the grid.

Elsewhere.

Federico Kotek · Product Designer · Buenos Aires
linkedin.com/in/federicokotek · fedekotek.design

The long version.

Seventeen years (if you count the motion graphics). Most of it taught me that the interesting problems are the ones nobody wants to look at.

Experience
Education

Got something hard to design?

I like talking to people building almost anything: a tool for the shop floor, a bank, a map, a toy. If someone uses it and it gets in their way, I want to hear about it. Based in Buenos Aires. Write to me in English or Spanish (or Spanglish).

Message me on LinkedIn