The most unexpected questions were during the presentation of the interview exercise where questions were asked that seemed outside of the scope of the 'project'. For example, if you wanted to accomplish XYZ, how would you do that? I was so focused on meeting the requirements that I wasn't prepared to think outside of the box very much. Having a good understanding of the platform would definitely aid in these types of questions.
Nothing stands out as particularly difficult question other than the SFDC project which was complex and time consuming especially if new to SFDC.
No difficult questions.
Detailed business questions for IT people. Know your markets and instruments!
Explaion the use of a Metastorm ProVision in the context of a particular project. Why would you use certain modelers over others
Nothing much on the technical part, but interviewe should familiar with ETL, how to consolidate data from various sources into one repository.
There were no real difficult questions but I was surprised at the detail to which I was expected to know Salesforce when I had been told that mastery of the program was not a requirement prior to hiring. I was told my weak spot was data modeling, which in turn is difficult to express without knowing the full functionality of the Salesforce site.
What is the null-coalescing operator and how is it used.
Impromptu Data Modeling
What was the most challenging problem you had to solve in your current position, with a follow up question on how you solved the problem, what skills and resources you used.
Viewing 5001 - 5010 interview questions