Pros
Currently, there are pretty big moving pieces that we have to implement and refactor. That with writing production-level code makes this part of department pretty difficult. There are days where I work way past the normal work times, and even on weekends. But I enjoy the challenge because it only makes me better, especially when tackling the obstacle with such a smart team. It hasn't been a full year since I started working here and I feel as if I matured as a developer much more than I would ever have imagined. And to compliment that, they have the flexibility to let you work however you like as long as you get the job done and done correctly. They also encourage you to learn outside of the stack we use for work, to further improve your skills in programming.
Cons
I think the Engineering department is having too much demand on too little supply problem. With the limited resource of people in this department there are times when we get side tracked due to other things when we are trying to timely finish some major features. In general, it's not something too big, but I also wished some of the meetings were scheduled in more of a compact manner. In Engineering, there is a big meeting for sprint planning, then there is company's all hands meeting, then more of a "culture" encouraged meeting, and I'm aware the upper management have another major meeting. This is all fine and necessary, but having all of this separated to each day instead of merging some of the meetings to same day seems a bit inefficient, at least that's how I feel like in Engineering. I personally prefer working with out interruptions, and I don't mind having a designated day or two to expect long meetings, but when these meetings are spread out I do not feel as productive.
