Delegate, lean toward mission command. You have some great, motivated engineers, analysts, and managers. They know how to overcome the obstacles holding them back. Let them. Empower people. Let managers have power to request equipment and accounts, and specify defaults they expect for newhires/transfers. Let analysts have regular dedicated time to study domain, or pair with devs/testers to learn broad technical details. Let engineers have a say in estimates, and a regular way to recommend internal improvements that require nontrivial time investment. Most of all, let teams have autonomy to self-reflect and figure out their own best way to work. Because right now... Managers often feel helpless to set up newcomers.
Before, they could directly grant access to code repositories, or documents, or kept a spare license and so could get new guy up and going in the span of a conversation. Now they have to babysit tickets... and it can take a week. Analysts are always pressed for time. Investment in knowledge sharing can wait until next week... for months on end. Help them out please. Engineers roll their eyes at deadlines they know are fantasy from minute 1, which for them, materialized from the wishful thinking of some clueless unseen fool. And if they have an idea for a fix or tool with high productivity ROIs, it's a difficult and clumsy process to get board time for it. Because there's no reference, training, or example provided for pitching internal stories.
Finally, teams need autonomy in order to pursue continuous improvement. Currently, they have no final, or even, approval assumed until vetoed ability to meaningfully change process in story slicing, code ownership, code review, or handoffs (e.g. UAT). Nor are priorities specified, you know, just in case requirements directly conflict and they have to be balanced. Which is all the time.
I applied through University/college and the interview was supposed to be around "45 to an hour". But, the interview was delayed for 20 mins. I don't know why but the interviewer decided to get the time on track during my interview. When I came in,
HR screening, 1st round technical, 2nd round technical with team manager. Process typically includes an initial recruiter screen, a technical phone or online coding test, and onsite interviews. These cover data structures, algorithms, system design,
It was a 4 step process. 1. Application 2. HR interview 3. Technical interview 4. Technical interview with current employees present. Through all of these steps, you are tested on your problem-solving and your ability to talk about your thinking beh
I applied through University/college and the interview was supposed to be around "45 to an hour". But, the interview was delayed for 20 mins. I don't know why but the interviewer decided to get the time on track during my interview. When I came in,
HR screening, 1st round technical, 2nd round technical with team manager. Process typically includes an initial recruiter screen, a technical phone or online coding test, and onsite interviews. These cover data structures, algorithms, system design,
It was a 4 step process. 1. Application 2. HR interview 3. Technical interview 4. Technical interview with current employees present. Through all of these steps, you are tested on your problem-solving and your ability to talk about your thinking beh