-Mostly work with very smart people who want to collaborate-Complicated frontend work that can be interesting if you get to work on it-Good place to learn how to be in a large company and program within a team
-There’s not enough challenging work for experienced engineers to go around -What you learn isn’t very helpful when trying to find another job. Frontend engineers only do the node layer and Vue. There are different teams for deployment, database accessing, and even build tools. -Complaints or suggestions for improvements frequently get lost or brushed off -My engineering managers gave all prioritization power to the PDs so it was really difficult to address tech debt -Lots of maintenance mode code isn’t acknowledged as such and still gets requested department-wide updates.
Then you have to pray the build still works and you can install everything and know how to test it since they “shifted left” and got rid of the QA department. -Most of the code reviews of fresh college grads falls on the senior members of the team, not the manager, and the amount of turnover means I rarely got to put up any code reviews of my own because we were constantly training new hires. -Low pay and lack of transparency around it. Asking what the average raise was for your position and rating will only get you a “you’re better off than X person”
-Listen to your senior engineers when they suggest new or existing projects to work on. Leave the rote feature work to the junior engineers. -Make the pay bands transparent to everyone -There are college degrees for project management, maybe hire some people with those for PDs instead of letting anyone become one. -In meetings where employees get to vote on the questions for Q&A, answer the top voted question, not whatever the moderator chooses.
HR was really nice and very prompt. However interviewer seemed to be a software engineer with not much background in interviewing people. Even though I applied for a software engineer position and I informed him that I have not worked with web techno
Standard interview process with initial HR call, coding assessment with an engineer and 5 on-site interviews. Questions: 4 DSA questions and 1 system design discussion. The interview process started at 9am with a demo of FactSet's applications and
Initially their response was prompt, which was encouraging. I set up a phone interview which went very well. I guess the interviewer was a little unclear about my C/C++ programming knowledge, so he asked me to write a 40 line program that reads dat
HR was really nice and very prompt. However interviewer seemed to be a software engineer with not much background in interviewing people. Even though I applied for a software engineer position and I informed him that I have not worked with web techno
Standard interview process with initial HR call, coding assessment with an engineer and 5 on-site interviews. Questions: 4 DSA questions and 1 system design discussion. The interview process started at 9am with a demo of FactSet's applications and
Initially their response was prompt, which was encouraging. I set up a phone interview which went very well. I guess the interviewer was a little unclear about my C/C++ programming knowledge, so he asked me to write a 40 line program that reads dat