If you get the right team, you'll be working with modern tools and encouraged to contribute to inner source.
A supportive environment. A lot of access to continuing education, volunteering, and benefits.
Clear boundaries and responsibilities, an energetic environment.
Very technically capable employees (collaborative growth).
Good pay.
Internal mobility is now encouraged.
If you get a bad team or a bad legacy project, it can be a horrible experience. I've seen several talented engineers get frustrated at the lack of impetus to improve existing systems.
Business often bleeds its responsibilities into engineering, leading to rushed projects or bad decisions because non-engineers are driving the conversation. A lot of internal forks of third-party projects or dated Bloomberg implementations of existing tech (related to the above, fortunately changing). Normal trappings of internal politics expected of large organizations.
Not much, a lot of these cons are slowly being addressed. Engineering heads are pushing for better practices. If anything, pinpoint bad engineering managers and reshuffle them. Emphasize that engineering is ultimately in charge of leading project implementation decisions, and they're encouraged to push back on business when demands are unreasonable.
I applied online through the University recruiting website. I was asked for my availability to schedule a phone interview. After providing my timings, the process took only two weeks. The phone interview initially involved a review of my resume, fol
The first round was a technical phone interview. In the first half, they picked some things from my resume to ask me more technical questions about. The second part involved two coding questions. The first was fairly easy and more of a warm-up, and
I was interviewed at the school campus. The interview started with a review of my resume and proceeded with two technical questions. The questions were not difficult. The interviewers were very helpful and chill.
I applied online through the University recruiting website. I was asked for my availability to schedule a phone interview. After providing my timings, the process took only two weeks. The phone interview initially involved a review of my resume, fol
The first round was a technical phone interview. In the first half, they picked some things from my resume to ask me more technical questions about. The second part involved two coding questions. The first was fairly easy and more of a warm-up, and
I was interviewed at the school campus. The interview started with a review of my resume and proceeded with two technical questions. The questions were not difficult. The interviewers were very helpful and chill.