Quote:
Originally Posted by KatoKrazy
I don't really do a lot of coding in my spare time, and my employer (and specifically my non-disclosure agreement) certainly wouldn't let me show you code from work.
If you want to see how they write code, perhaps you should assign them some sort of task to complete in between a first and second interview or something?
Wat? Isn't that basically what a resume is? I mean, I would probably get a little more specific about the skills I have and how they were applied in previous roles, but what exactly is it you are looking for in a resume?
Again its just culture stuff that will never change but it just makes sense to me to do everything possible to show you can do the job and they don't at all. Not going to keep ranting on this though.
As far as the resume thing though - India resumes are literally just their name, education, list of supposed skills (bullet points) and then where they worked and what
the company did, not what the applicant's did there or what they worked on or even the product, just the general what field the company was in basically. I guess its some prestige thing? I have no idea what these companies are or care. I've gotten 4 page resumes of page after page of stints that is 100% meaningless to me. Weird.
And disagree re: look at code I've had several interviews in the last few months that literally was an hour of talking about my current side project (full stack JS react redux websocket app).