A recruiter reached out to me via LinkedIn. After a brief chat with the recruiter, a phone screen was scheduled.

The interviewer was late by a few minutes for the call and immediately jumped into the question without any introduction about himself or me. It was an object-oriented design question, and I was able to model it, making me think that it went well.

After two weeks, I received an automated email with the usual boilerplate message.

I am very disappointed with the way the information was communicated, the way the phone-screen interviewer conducted the interview, and what he found to be missing, given that I was able to provide two approaches, weigh those options, and come up with the code for it.

Implement a ‘bank’ class. The bank should keep track of the account balances for different accounts, designated by numeric identifiers. It should support the following operations:

• Deposit and withdraw to a single account.
• Transfer between two accounts.
• Calculate the total amount of money in the bank.

Opening a new account should be done by depositing or transferring money to a previously unused account ID. Accounts cannot have negative balances. Regulations also state that no account may hold more than $100M.