Top of the ladder for investment banks, bragging rights amongst other friends on the street (though you quickly feel identified as a tool when around normal people).
Good job security and compensation for those that have been there a while and have broken through the steep learning curve and unique operating practices.
Long hours; you can work less and make more elsewhere.
Survives mostly on reputation, which doesn't really apply to tech roles.
Development role involved mostly 1st line business support on an archaic, proprietary, poorly designed system (stressful).
Poor dissemination of tech knowledge/documentation past your initial initiation training.
Slang/SecDB is indeed an interesting platform with great ideas, but the tools and UIs are ancient and make those used to more modern development environments wince.
Lateral experienced hires take a significant hit as the tech knowledge you can carry in is minimized.
Technology is led mostly out of the Quant area, not IT, leading to poor quality, complicated code.
Place more focus on development standards and understand that building easily supportable, consistent systems is as important as the initial time to delivery.
Understand that business support is not a role that tech developers are interested in and can necessarily add much value in.
Phone interview vs. online interview: Phone interview was better. Pretty basic expectations. Online interview: Need to solve a problem in a hackathon. Easy to medium-hard LeetCode problems. Need to write test cases and execute them as well.
A recruitment agency reached out to me. Then, it was a 7-round interview process spanning over a 2-month period. This included: * Telephone screening * Online test * Telephone interview * Multiple rounds of on-site panel interviews.
Had a basic 30-minute phone interview. Questions were around the advantages and disadvantages of using normalization, Java collections, and writing thread-safe code. The phone interview was followed by an on-site interview. The on-site interview co
Phone interview vs. online interview: Phone interview was better. Pretty basic expectations. Online interview: Need to solve a problem in a hackathon. Easy to medium-hard LeetCode problems. Need to write test cases and execute them as well.
A recruitment agency reached out to me. Then, it was a 7-round interview process spanning over a 2-month period. This included: * Telephone screening * Online test * Telephone interview * Multiple rounds of on-site panel interviews.
Had a basic 30-minute phone interview. Questions were around the advantages and disadvantages of using normalization, Java collections, and writing thread-safe code. The phone interview was followed by an on-site interview. The on-site interview co