Related Posts
Where them 30+ ladies at? 25M 🙋♂️😉
Anyone in to younger guys?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Where them 30+ ladies at? 25M 🙋♂️😉
Anyone in to younger guys?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

Project walkthroughs/explanations are standard not just in analytics, but in general for job seekers. Individuals can either over-explain, under-explain, get lost in detail-laden tangents, or even not capitalize on openings to showcase the work.
Personally I structure my projects as "What does this report/project tell us, and why is it important?" but sometimes just leaving it there, not getting into too much technical detail. My structure is generally:
Contextualize why/how the project came about, what it was intended to do
Explain the logistics but ~ Get confused on how much detail to go into~ very awkward at times (over/under explaining)
Explain project impact, if any, on the original problem
Do you think the onus should be on the interviewee to explain the project technicalities, or is it up to the hiring manager to probe?
What has really stuck out for you?