What are you looking for in a new position?

Congratulations on reaching this pivotal point in your career. Moving from an Engineering Manager to a Director isn’t merely a title change; it’s a fundamental reorientation of your responsibilities, influence, and the lens through which you perceive success. As a Manager, your primary focus has been on the “what” and the “how”—ensuring efficient execution, fostering team health, and mastering tactical implementation. You’ve been the conductor of an orchestra, ensuring each section plays its part harmoniously.

As a Director, your role elevates to the “why.” You’re no longer just ensuring the music is played well; you’re determining which symphony should be performed, why it aligns with the overall artistic vision of the institution, and how to acquire the resources and talent to make it happen. You become the architectural strategist, aligning your engineering efforts with the broader business objectives and cultivating organizational health at a much larger scale.

When considering what you are looking for in a new position, it’s essential to reflect on the importance of effective communication in the workplace. A related article that explores this topic in depth is titled “Some Ways to Strengthen Student-Teacher Communication,” which discusses strategies that can enhance interactions and understanding between educators and their students. You can read more about it by following this link: Some Ways to Strengthen Student-Teacher Communication. This article may provide valuable insights that can inform your expectations and aspirations for a new role.

Key Differentiators: Manager vs. Director Lenses

It’s crucial to internally understand and externally articulate this shift during your interviews. Here’s a breakdown of how the responsibilities and focus diverge:

Scope of Impact and Influence

Manager Focus: Primarily on a single team or a small group of related teams. Influence is direct, often through 1:1s, team meetings, and project management. Success is often measured by team output, project completion, and individual growth.
Director Focus: Across multiple teams, departments, or even entire product lines. Influence is indirect, through other leaders, strategic initiatives, and organizational design. Success is measured by product market fit, business growth, revenue impact, strategic enablement, and overall organizational resilience.

Strategic vs. Tactical Engagement

Manager Focus: Deep dives into technical challenges, resource allocation within the team, unblocking engineers, and refining team processes. The operational cadence is often weekly or bi-weekly.
Director Focus: High-level strategic planning, defining multi-quarter or multi-year roadmaps, identifying market opportunities, and assessing technological trends. The operational cadence is typically quarterly or annually, with continuous strategic adjustments.

Problem Definition and Resolution

Manager Focus: Solving immediate, concrete problems. “How do we fix this bug?” “How do we improve code quality?” “How do we meet this sprint deadline?” The problems are often well-defined with clear technical solutions.
Director Focus: Identifying ambiguous, systemic problems that impact the business. “Why are we losing market share in this area?” “How can we leverage AI to create a new revenue stream?” “What organizational structure best supports our long-term growth objectives?” The problems often lack clear solutions and require cross-functional collaboration and strategic thinking.

People Management and Development

Manager Focus: Nurturing individual careers, providing performance feedback, coaching on technical skills, and resolving interpersonal conflicts within the team. The emphasis is on team cohesion and individual professional growth.
Director Focus: Building leadership capabilities within their management layers, succession planning for critical roles, designing effective organizational structures, fostering a culture of innovation and psychological safety across departments, and mediating inter-team or inter-departmental conflicts. The emphasis shifts to the leadership pipeline and broad organizational health.

Communication and Stakeholder Engagement

Manager Focus: Communicating project status, technical decisions, and team needs to immediate stakeholders and senior management. Communication is often detailed and execution-focused.
Director Focus: Translating complex technical strategies into clear business language for executives, investors, and external partners. It involves influencing cross-functional leaders, managing expectations, and articulating the “why” behind significant engineering investments. Communication becomes less about “what” we’re doing and more about “why” it matters to the business.

Risk Management

Manager Focus: Identifying and mitigating technical risks within projects, managing sprint dependencies, and ensuring reliable software delivery.
Director Focus: Assessing strategic risks (e.g., market shifts, technological obsolescence, competitive threats), making trade-offs between technical debt and business velocity, and establishing processes for broader organizational resilience and security.

Budgetary Responsibility

Manager Focus: Managing team-level expenditures, estimating project costs, and ensuring efficient use of resources allocated to their team.
Director Focus: Contributing to departmental and organizational budget planning, justifying large capital expenditures (e.g., cloud infrastructure, significant tooling investments), and demonstrating ROI for engineering initiatives.

Interview Tactics: Elevating Your Narrative

When asked about your experience, or even a past project, it’s easy to default to the Manager-level “what” and “how.” Resist this impulse. Instead, adopt a Director’s perspective, framing your answers around strategy, impact, and “why.”

Instead of: “I led my team to ship Feature X on time, and we reduced the defect rate by 15%.” (Good, but Manager-level.)

Try this Interview Tactic (Script):

“While leading my team in shipping Feature X, my primary strategic objective wasn’t just on time delivery, but to address a critical gap in our product portfolio that was impacting our Q3 revenue targets and customer retention [strategic ‘why’]. I recognized that existing technical debt could hinder our speed to market, so I strategically allocated 20% of our capacity to technical hygiene concurrent with development. This proactive decision allowed us to not only launch Feature X on schedule but also saw a 15% reduction in post-launch defects, directly contributing to a 5% increase in customer satisfaction [business impact] for that product segment. Beyond the immediate feature, this experience also highlighted the need for a more robust architectural review process across engineering, which I then championed at the departmental level to prevent similar issues in future initiatives, thereby improving our overall engineering velocity and product stability long-term [organizational health and future strategy].”

Analysis of the Script:

Strategic “Why”: Immediately connects the project to business objectives (revenue, retention).
Director-level Decision-Making: Shows a trade-off decision (technical debt vs. speed) and the underlying strategic rationale.
Business Impact: Quantifies the benefit not just in technical terms, but in customer and business value.
Organizational Influence: Demonstrates the ability to identify systemic issues and drive change beyond the immediate team, influencing broader engineering processes.
Future Orientation: Connects past actions to future strategic improvements.

Here’s another example, shifting from a people management perspective:

Instead of: “I mentored a junior engineer who struggled with testing, and now they write great unit tests.” (Manager-level, tactical growth.)

Try this Interview Tactic (Script):

“Recognizing a recurring pattern of testing deficiencies across several junior engineers, which was leading to an elevated bug rate and impacting our release confidence [broader organizational problem], I didn’t just focus on individual coaching. While I did 1:1 mentor one engineer to elevate their testing practices, my larger strategic goal was to cultivate a culture of quality assurance at the foundational level for our emerging talent [strategic ‘why’ for people development]. I spearheaded the creation of a ‘Quality First’ internal training module for new hires and collaborated with other managers to integrate robust testing standards into our onboarding process. This broader initiative led to a 20% reduction in production critical bugs within six months across junior-led projects [quantifiable organizational impact], effectively scaling quality improvement beyond just my immediate team and building a stronger talent pipeline for future leadership [long-term organizational health].”

Key Takeaways for Your Interview Preparation:

Connect Everything to Business Value: Every project, every challenge, every success should ultimately link back to how it impacted the business, customers, or the organization’s strategic goals.
Think Beyond Your Team: How did your actions influence other teams, departments, or even the entire company? Did you establish new standards, processes, or shared understanding?
Demonstrate Strategic Foresight: Show that you’re not just reacting to problems, but anticipating future challenges and proactively positioning the organization for success.
Highlight Your Influence on Other Leaders: Discuss instances where you influenced peer managers, VPs, or even executives.
Use the Language of Strategy: Words like “strategic objective,” “organizational health,” “market opportunity,” “business alignment,” “risk mitigation,” and “long-term vision” should naturally appear in your answers.
Quantify Impact Broadly: Instead of just team metrics, think about department-wide or business-centric metrics (e.g., revenue, customer acquisition, operational efficiency, talent retention percentage, security posture improvement).

By consciously shifting your narrative from the “what” and “how” to the “why” and demonstrating your capacity to operate at a higher altitude, you will effectively articulate your readiness to step into the Director role. You’re not just a better conductor; you’re ready to become the artistic director, shaping the entire season.

FAQs

1. What does the question “What are you looking for in a new position?” typically aim to discover?

This question is designed to understand a candidate’s career goals, motivations, and what they value in a job. It helps employers assess if the candidate’s expectations align with the role and company culture.

2. How should candidates prepare to answer this question?

Candidates should reflect on their professional goals, skills they want to use or develop, and the work environment they thrive in. Researching the company and role beforehand allows for tailored and relevant responses.

3. What are common elements employers look for in answers to this question?

Employers often look for clarity about career direction, enthusiasm for the role, alignment with company values, and a realistic understanding of the job responsibilities.

4. Is it appropriate to discuss salary and benefits when answering this question?

While salary and benefits are important, it is generally better to focus on job responsibilities, growth opportunities, and company culture in this answer. Compensation discussions are usually reserved for later stages of the hiring process.

5. Can this question help candidates evaluate if a job is a good fit for them?

Yes, by articulating what they seek in a new position, candidates can better determine if the role meets their professional needs and aspirations, ensuring a mutually beneficial employment relationship.