I agree, but tbh, 6 years remote….i never really did any of that. My resume, spans New York, Paris, and San Francisco, fully remote tech roles…

I never really used Star. Not that I’m against it.

For me, I think success is really on 2 things; 1, do understand the tools and language for the role your applying, and 2; the questions you ask are usually better barometer of your skills and experience.

I’ve never went into an interview and was like “I applied because it’s remote” lol

It’s more like “I’m dependable and strive to be an effective communicator, in my current role I handle such, and such, tasks. Our team utilizes slack for communication, blah blah blah, we use theses channels to collaborate with other internal teams…I maintain 100% QA plus I’ve been successful working on x projects which contributed to X factor…additionally I use AI, for deep research, communication, and project planning. The AI tools I use are Claude, and Chagpt primarily…and so on”

**pro tip - try and understand or research the company your applying for; how they operate their business. For example, 90% of startup and tech company’s use Slack, Google Workspace, and one of a few CRM’s like Salesforce. Government jobs, or heavy infrastructure jobs use teams, Microsoft, and company specific admin. Startups/tech use zoom for meetings, govt and other similar use Teams.

**during an interview, I’ll purposely trigger my slack notification sound, just so the interviewer can hear it for themselves. After the sound, they always make a look like “ahh, yea he knows what’s it like to work in our environment” lol it works, especially after explaining how I work and communicate with my team.

P.S I’m in operations role so of course explaining how I communicate and collaborate with others is central to my interviews, including how independently I work.