It'l be interesting to know what exactly a program manager does. I have read enough descriptions/profiles but its still not clear to me as to how a program manager is involved in the software developement aspect of a product. Most descriptions say that PMs
define feature set, hold meetings, manage timelines.. how are these things related to software development?
Do program managers build architecutres? As in lets say theres a certain product- Is it the program managers job to come up with a software architecture (class heirarchy etc)? Are they supposed to care about details like 'use recursion instead of iteration'
kind of issues? Do they write/read/troubleshoot code?
Ive heard and seen people work their bottoms off in my school 'preparing' for a microsoft interview- they revise all thier coursework, read books on interviewing etc.
I wonder if all that is required? The palindrome question in the second video seems simlpe, but lets say i didnt remember C syntax and mess up in writing the program but wrote a good and correct algorithm- what kind of impression does that give to the interviewer?
Lets say I did n number of courses during my degree program? Iam sure noone expects us to know all the coursework?
I just want to know what the interviewer is expecting out of the candidate? A general tip given is: Know whatever you have on your resume inside out. are we supposed to know the minutest implementation details of all projects?
Also, are coding questions asked in PM interviews? because PMs dont code (please correct me if wrong)
what kind of non technical and non design questions should one expect in a PM interview, given that the careers website say most hires for PM are comp science backgrounds?
are we supposed to think Cost/Business perspective while responding? If so how would someone expect a CS guy to know that?