I work in a team with excellent team spirit and culture; people help each other and cooperate, and are encouraged to learn and grow.
"You own your career" is helpful as well as important to remember throughout your career.
Many learning resources are available at work, as well as on home devices (Pluralsight, Egghead, Safari Books, ...).
It's a big bank, but the NJ office (30 Hudson St) has a general "casual dress" policy; suit and tie are okay, but few people wear them.
Some wicked smart people work there; there's lots to learn from them.
I was able to work from home whenever needed (family, sickness, ...), and be productive from home.
Big companies come with many restricting policies from the Feds, which limit personal trading and require more paperwork to get seemingly important stuff done. More paperwork means less focus on what you think is job-relevant.
The company blocks (has to block) many websites because they might allow you to post text that it cannot retain and track. Unfortunately, that includes many sites that can be very useful for developers, such as Google Groups and blogs.
Keep educating your people. Give them chances to be efficient and productive. Stay on top of salaries in the industry.
A recruiter contacted me via LinkedIn and set up a phone screen. The technical phone interview used a coding tool, and the questions were of easy/average difficulty. Note that at GS, the VP Engineering position is similar to a Senior Software Engin
They had an initial 45-minute phone interview. I came to know via the recruiter after a week that I needed to go for an in-person interview. I was called in at 2:00 pm. There were four rounds of 1:1 interviews. The interview level was not as good as
I had an interview with a recruiter for a consultant position. A face-to-face interview was required and the whole process took three and a half hours. I met three developers and one manager. It was mostly technical-related questions, for example, h
A recruiter contacted me via LinkedIn and set up a phone screen. The technical phone interview used a coding tool, and the questions were of easy/average difficulty. Note that at GS, the VP Engineering position is similar to a Senior Software Engin
They had an initial 45-minute phone interview. I came to know via the recruiter after a week that I needed to go for an in-person interview. I was called in at 2:00 pm. There were four rounds of 1:1 interviews. The interview level was not as good as
I had an interview with a recruiter for a consultant position. A face-to-face interview was required and the whole process took three and a half hours. I met three developers and one manager. It was mostly technical-related questions, for example, h