This is interesting, but not applicable toward all job types. In my experience as a software engineer, it's incredibly rare for day-to-day or project work to be measured by any of the metrics types listed in this video. Migrating systems out of need, introducing new tech in hopes of luring future customers, or bending over backwards to help develop the careers of inexperienced devs simply does not translate to the 6 categories you've listed here. And matters only become worse if the team and/or company does not have room for R&D, but rather is firmly entrenched in KTLO mode. And I haven't even touched upon organizations that cascade project directives in such an ambiguous manner that no IC can capitalize upon the completion of the work. So while I appreciate that many job-seekers will benefit from content like this, it simply isn't applicable to everyone. And I find it worrisome that some in the tech sector may exclusively scan for data like this on resumes without genuine perspective into how teams and projects actually function.
It can when you are working for someone. You can say you worked with X amount of clients delivering Y number of deliverables early and under budget or something similar. You can quantify!
Hey Farah, what about when you cant quantify ? let me give you an example, for enterprise companies // the software process to come out in public takes time, LA-local availability, GA-General availability and many times teams work on feature sets without any set metrics per say, it might come from 7-8 customers externally whom you dont have access to .... Now lets say you have designed for a version/ feature and you leave, how do you quantify in that case ? thanks !!
I had the same question. It's hard to describe complex projects and I just say "complex" and through a wall of text trying to describe all the responsibilities. The issue is that they also overlap in different companies, so it sounds the same ...
I have a question about the bullet point under the work experience section. Is it important for all the bullet points to be achievements? Thank you! Btw, great video. I was able to learn so much in a short time span compared to other videos out there :)
Good question! Yes in that you can have quantitative and qualitative data. Leading a team of people is an achievement. Mentoring others is an achievement. You got this!
I think your application of the XYZ formula is not as Google stated it. According to google it is: Accomplished [X] as measured by [Y], by doing [Z]. What you state is: Did (Z) to (X) resulting in (Y). Wouldn't it be: Increased sales by 20%, by leading a project?
At 4:17 you’ll see a slide: x = accomplishment, y = metric, z = result. The point is that it’s about stating your accomplishments via metrics. Listing out your bullet points in this same format for every single one will look weird and I’m giving another option that also works. Mix & match!
Thank you for the video, very good content! I have a few questions: 1 - For example I'm Front-end developer and I've implemented the feature that increase UX using the App (I defenetly know it). But how can I transform it into % if the company didn't do any AB testing for this feature? 2 - I've impemented the feature which increase revenue of the company by 50k$/m. But if I specify this number in my CV - will it violate the NDA between me and the company? Should I ask for permission from the company? P.S.: I didn't work in this company anymore
Great content! Keep it coming!
Thank you! More is on it's way!
Brilliant! The formula is so simple and easy to follow!
Thank you!
You deserve way more subscribers than you already have.
Thanks for your lovely comment! Glad you enjoy my videos 😀
This is interesting, but not applicable toward all job types. In my experience as a software engineer, it's incredibly rare for day-to-day or project work to be measured by any of the metrics types listed in this video. Migrating systems out of need, introducing new tech in hopes of luring future customers, or bending over backwards to help develop the careers of inexperienced devs simply does not translate to the 6 categories you've listed here. And matters only become worse if the team and/or company does not have room for R&D, but rather is firmly entrenched in KTLO mode. And I haven't even touched upon organizations that cascade project directives in such an ambiguous manner that no IC can capitalize upon the completion of the work.
So while I appreciate that many job-seekers will benefit from content like this, it simply isn't applicable to everyone. And I find it worrisome that some in the tech sector may exclusively scan for data like this on resumes without genuine perspective into how teams and projects actually function.
Well said!
Great tips!! Thank you!!
Glad you liked them!
This was amazing!!!✨✨✨
Thank you! 🙏🏼
Everyone keeps yapping about metrics but it just doesn't apply to most design.
It can when you are working for someone. You can say you worked with X amount of clients delivering Y number of deliverables early and under budget or something similar. You can quantify!
@@Farah_Sharghi Now assume you are just a working drone and don't get any of those numbers... in fact thats why you have 3 people managing you.
Hey Farah, what about when you cant quantify ? let me give you an example, for enterprise companies // the software process to come out in public takes time, LA-local availability, GA-General availability and many times teams work on feature sets without any set metrics per say, it might come from 7-8 customers externally whom you dont have access to .... Now lets say you have designed for a version/ feature and you leave, how do you quantify in that case ? thanks !!
You just quantified data for me. You can quantify time, amount of people, percentage of improvements, etc
I had the same question. It's hard to describe complex projects and I just say "complex" and through a wall of text trying to describe all the responsibilities. The issue is that they also overlap in different companies, so it sounds the same ...
I have a question about the bullet point under the work experience section. Is it important for all the bullet points to be achievements? Thank you!
Btw, great video. I was able to learn so much in a short time span compared to other videos out there :)
Good question! Yes in that you can have quantitative and qualitative data. Leading a team of people is an achievement. Mentoring others is an achievement. You got this!
@@Farah_Sharghi Thank you so much!
I think your application of the XYZ formula is not as Google stated it. According to google it is: Accomplished [X] as measured by [Y], by doing [Z].
What you state is: Did (Z) to (X) resulting in (Y).
Wouldn't it be: Increased sales by 20%, by leading a project?
At 4:17 you’ll see a slide: x = accomplishment, y = metric, z = result. The point is that it’s about stating your accomplishments via metrics. Listing out your bullet points in this same format for every single one will look weird and I’m giving another option that also works. Mix & match!
Thank you for the video, very good content!
I have a few questions:
1 - For example I'm Front-end developer and I've implemented the feature that increase UX using the App (I defenetly know it). But how can I transform it into % if the company didn't do any AB testing for this feature?
2 - I've impemented the feature which increase revenue of the company by 50k$/m. But if I specify this number in my CV - will it violate the NDA between me and the company? Should I ask for permission from the company?
P.S.: I didn't work in this company anymore
Show me the guy who increased IBMs revenue by 30% please
lol! Touché