IIVI
Superstar
Basically for resumes in general, if I know how something works I just say I built it because I can talk enough about how it works inside out.What do you mean by back up?
I worked on certain parts of codebases long enough to basically understand it's workings so I legit put it on my resume I "architected" it. If they want a reference, use a trusted co-workers or if manageable, one of an irl friend that knows software.
shyt, even if I don't fully understand how something works I'll post that I made it if it's a big feature and I understand most of it. During interviews if they ask anything specific about it that I don't know I just say "that was an abstraction layer handled by another team primarily, I didn't really attend to the implementation details of it" but if I do know some about it I'll drop in what I know as well then hit them with the "abstraction" reason.
Remember, these guys weren't with us in the gym. They know absolutely nothing about what we did at a company. Blow that shyt up on your resume and rehearse your talking point around it for the interview. Plus honestly, if you understand it enough you can bring that experience with you where you go.
Last edited: