I've been struggling to put my resume together for new senior/lead front end roles. My current position came through a referral and only needed my resume as a formality so didn't really put thought into it. Now that I'm looking for new roles and going through the application process, I've struggled to get any traction. I've gone through the how to write a stellar resume course here and implemented a lot of that thinking. I believe the one thing I'm missing is metrics. Unfortunately they're hard to get at my company but I've built custom features for large clients who use our platform. Is there a way to get around specifying number of users and what are some other metrics I can use?
So if you have large clients, definitely mention them by name. Don't be afraid to use ballparks.
For example, let's say you're building an app to help Home Depot's warehouse workers and there are 475,000 of them (this is a super rough number I pulled from Google for the sake of the example). You can say something like "Delivered an inventory solution for Home Depot's 475,000 warehouse workers". You have 0 idea of how many workers among that pool are actually using your software, but this statement is also technically true as it is for that general group overall.
If you can't do that for any of your prior projects, make sure to add basic logging to your future projects so you stop this lack of numbers bleeding. I imagine your clients would want to know metrics too, so that's a win-win. Of course, the overall business wants to know as well - There's no point writing software with 0 users. This is classic senior+ engineer behavior and building a logging instinct was a huge part of my growth from mid-level to senior at Meta. Check out this thread: "How do you measure the impact of an initiative you are leading?"