One of the major pros is that you get to own projects, regardless of whether you are considered 'management'. That certainly makes things exciting.
Almost all the focus is on getting stuff out there 'fast!' Good coding style and good software design aren't as important. While that may work in the short run, in the long run it causes a lot of headaches in terms of software maintenance. But the management doesn't care about that. They just want you to churn more software out, as fast as you can.
And of course, there is nothing called 'testing'. It's the developer's job, of course. And you still have to get things out there 'in time'.
Please understand that you can't have more and more software out there, and still expect it to be churned out in a short time. The more software we have out there, the more we need to maintain it. If we just churn it out, with all the focus on time (and very little focus on good design), it's like trying to juggle priceless eggs in variable gravity. At some point, the bug rate is gonna overwhelm new development, and that's not what we want.
While I understand the business need to develop new products in a short time, it needs to be balanced with good design too.
The interview was a technical phone screen conducted via video call with screen sharing. After brief introductions, the interviewer asked about my Java experience and previous projects. Then we moved to a live coding challenge where I needed to solve
Traditional interviews start with LeetCode-style interviews, followed by behavioral. Be prepared for hard/medium level problems, even one problem to solve for the entire interview. Interviews were standard, and feedback was provided quickly.
Telephonic interview. The interviewer asked me to write a code for deep copy of a linked list. I did, but I did not get selected for the next rounds. Overall, the interviewer was helpful.
The interview was a technical phone screen conducted via video call with screen sharing. After brief introductions, the interviewer asked about my Java experience and previous projects. Then we moved to a live coding challenge where I needed to solve
Traditional interviews start with LeetCode-style interviews, followed by behavioral. Be prepared for hard/medium level problems, even one problem to solve for the entire interview. Interviews were standard, and feedback was provided quickly.
Telephonic interview. The interviewer asked me to write a code for deep copy of a linked list. I did, but I did not get selected for the next rounds. Overall, the interviewer was helpful.