that was very helpful, thank you

1) 3 people 2) It's a flat structure, no hierarchy 3) We are embedded in the Product Org 4) 400-500 people; ratio is 1 designer : 23 developers

I also recommend checking out this report if you haven't already, someone has already collected most of the information you're asking about and made a report out of it: http://uxtools.co/survey-2018

I posted this comment after I clicked the link, I was expecting a long article not a sentence which was why I made the comment that I did. But if that's your style of writing, then c'est la vie.

the clickbait is real...

The team I work on used to be on that structure but that was back when designers were split on different teams working on different products; now we're all one team working on all of the products.

Back when we were on different teams, it didn't matter so much what tool we used since we were so far removed. As long as within each team, they used the same tool. For us, team A used Adobe Photoshop and team B used Sketch. Once we all merged, we all started using Figma since it was easier to collaborate.

So my question for you would be: How is your team structured and is there a need to collaborate? Or is it more a matter of having access to the design files but not really editing them? If the latter, I'd recommend using a tool like Zeplin which hosts all of the different files regardless of what design tool you use to create the designs.

Thanks for the update, I'm based in the US for reference

This is what I see still when I click the link: https://imgur.com/zRbQpnX

That link does not work

This also reminds me of the guy who made entire digital paintings from a spreadsheet

I've been saying this for years! When people ask "Do designers need to know how to code?", my response is always "you're asking the wrong question. We should be asking if designers should understand business?".