Related Posts
Community Builder
How is FTI compare to Accenture?
What do you wear to atlanta ballet performances?
Worst process to get into project in nagarro.
First go through the internal project interview then client interview if not selected then again tons of interview.Why they people take interviews at the time of hiring.
I am feeling depressed now.
In this tough time where companies are firing their employees, i am not having any project due to this pissed process in nagarro.
Joined on 1sep 2022.One more interesting fact giving interview in zs associate account(contractor) I never want to work as permanent.
Visual Storyteller
Conversation Starter
PE firms with the best WLB?
Additional Posts in Engineering
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Prior to Honeywell acquiring us, I would complete jobs in 8-12 hours. Now it takes 30 hours or more to complete the same engineering task. More effort is invested in corporate oversight than actually doing the work, with a bunch of useless people monitoring “progress.”
Thanks for sharing!
I’d have an entirely different role if I’m being honest. I wouldn’t work on my daily activities at all and that would suffer, but all future projects would benefit greatly from process changes I’d make
Thanks for sharing!
One big stressor and inefficiency I've noticed is teams/IM taking over from Email for non-critical communications. As a general rule, I don't expect a response to an Email for 24 hours, so the person I'm reaching out to has some flexibility not to drop what they're working on and has some time to create a considered response. IM is the electronic equivalent to going up to someone and asking them Face-to-face, basically forcing them to drop what they're doing and either answer or ask me to wait. Sure the faster response will be needed on occasion, but often the mechanical engineering field I find that 24 hours is fast enough, gets me a better quality answer, and allows me to work to a plan instead of firefighting. Also, Teams Chat and IM are poor for finding old info, especially for group chats, Outlook is much better for that. So from my experience I would encourage organizations to reserve teams chat for true emergencies, and encourage engineers to think about how quickly you really need to have something answered and align communication accordingly.
That said, one thing I look for in companies is having incredibly robust processes. Having a process is more than having a change approval & PLM system, it’s having a documented way to do every thing you need to do to design your product. While this does add process tasks, having a good process for things that need to be done regularly protects the engineer and company from unnecessary risks, captures lessons learned, and actually makes it easier to get things done. If the company has a good process for doing something I never begrudge having to fill out the forms, and in fact I always put time, thought, and effort into them, my standard being that the target audience shouldn't need to ask me anything to carry out the work. Bottom line a company that has processes and follows them will be better to work for and can get more done.