Our interview process has the candidate implement a couple (extremely simplistic) API routes, with the specific approach left up to the candidate. It’s more about having something they can talk through and evolve than it is about us looking for any specific approach.

Basically it exists as a way for us to have a starting point for talking about scalability topics, asking the candidate how they would evolve their implementation as we scale up the system. Does a pretty good job of giving us an idea of how they think through system design problems.

Umm I use Jira and Confluence on Firefox every day without issue. Not sure what you’re talking about. The only time I’ve ever had to use Chrome in my professional career were certain tools that require chrome dev tools. Otherwise, it’s Firefox for everything.

Am 35, just started getting into birdwatching. Weird how true this is.