Functional Assessment Interview: Fill & Download for Free

I had only a weekend's worth of Scala hobby experience when I was interviewed for my position as a Scala programmer, and no Scala syntax questions came up during any of the interviews. For the related programming exercise I could use one or more languages of my choice.In the skills assessment interview for the position I got a lot of questions that tested my knowledge of a broad range of topics in software engineering and computer science, and there were possibly a few extra questions about functional programming than in other similar interviews I have done.

Couch metaphors aside, if you’re asking about the actual job tasks of an I/O psychologist, there are 24 major tasks commonly. No particular job will have all (or even most) of these, though:Formulate and implement training programs, applying principles of learning and individual differences.Conduct research studies of physical work environments, organizational structures, communication systems, group interactions, morale, and motivation to assess organizational functioning.Conduct presentations on research findings for clients and at research meetings.Provide expert testimony in employment lawsuits.Study consumers' reactions to new products and package designs, and to advertising efforts, using surveys and tests.Review research literature to remain current on psychological science issues.Develop interview techniques, rating scales, and psychological tests used to assess skills, abilities, and interests for the purpose of employee selection, placement, and promotion.Conduct individual assessments, including interpreting measures and providing feedback for selection, placement, and promotion.Write articles, white papers, and reports to share research findings and educate others.Develop new business by contacting potential clients, making sales presentations, and writing proposals.Develop and implement employee selection and placement programs.Identify training and development needs.Train clients to administer human resources functions including testing, selection, and performance management.Facilitate organizational development and change.Analyze job requirements and content to establish criteria for classification, selection, training, and other related personnel functions.Assess employee performance.Observe and interview workers to obtain information about the physical, mental, and educational requirements of jobs as well as information about aspects such as job satisfaction.Coach senior executives and managers on leadership and performance.Study organizational effectiveness, productivity, and efficiency, including the nature of workplace supervision and leadership.Write reports on research findings and implications to contribute to general knowledge and to suggest potential changes in organizational functioning.Participate in mediation and dispute resolution.Provide advice on best practices and implementation for selection.Counsel workers about job and career-related issues.Advise management concerning personnel, managerial, and marketing policies and practices and their potential effects on organizational effectiveness and efficiency.This comes from the Occupational Information Network (O*NET), which was developed with the help of… you guessed it… I-O psychologists. The I-O entry that I got this list from can be found here: 19-3032.00 - Industrial-Organizational PsychologistsThanks for the A2A!

Hi, I'm a Google engineer who’s done about 200 interviews there, and has been on hiring committee.You may use one of the non-"big 5" languages (Java, Python, C/C++, JavaScript, Go), but you probably shouldn't. This is especially true if you are applying as a front-end engineer, then inability to code JavaScript will be a showstopper. But if you do choose this path....First, be prepared to explain how the language is working - I've had interviewees who want to write in Ruby, or Perl, or C#, or whatever (one used APL!), and I let them, but they have to take the time to explain to me anything I don't understand. That extra time reduced the time I could spend assessing their fit as a hire.Second, don't use the language as a 'cheat', as in "it just so happens that in language <X> there is a library function that does what you are asking me to code - so i'll just call that library function". That will just result in the interviewer asking you to implement that library function.Third, you are taking a risk - you are making communication with your interviewer more difficult, and that rarely redounds to your advantage. Every minute you spent showing OCaml's abilities is a minute you could have spent showing your abilities.