The Director of Engineering Site Lead at Harvey is responsible for building and growing a landing team of over 10 engineers, launching our Engineering Product Development (EPD) team in New York. This role requires partnering with EPD leadership and the San Francisco team to foster collaboration while enhancing engineering velocity. Additionally, the Director will work closely with customers to identify their needs and develop a strategic product roadmap.

Candidates applying for the Director of Engineering Site Lead role at Harvey should possess at least 6+ years of experience in a software engineering management position, particularly in leading customer-facing product teams. A proven track record of building and coaching high-performing engineering teams in diverse locations is essential, along with 5+ years of hands-on software engineering experience.

At Harvey, the Director of Engineering Site Lead plays a key role in cultivating a culture of engineering excellence by encouraging innovation and calculated risk-taking among team members. This involves creating an environment where engineers feel empowered to explore new ideas while maintaining Harvey’s dedication to enterprise trust and safety.

The compensation range for the Director of Engineering Site Lead position at Harvey is competitive, falling between $300,000 and $360,000. This reflects the key responsibilities and the high level of expertise required for this pivotal role within our rapidly growing organization.

Joining Harvey as a Director of Engineering Site Lead offers significant opportunities for professional growth and development. As part of a hypergrowth startup, you will have the chance to expand your responsibility, influence the engineering direction, and shape the overall technology organization while being in the early stages of a generational company.

When answering this question, it's essential to highlight specific examples of past leadership roles where you've successfully built and managed teams. Discuss the strategies you employed for talent acquisition and team development, focusing on metrics that illustrate your team's performance or engagement.

Emphasize your communication strategies and tools you use to facilitate collaboration among remote teams. Discuss how you set clear goals and expectations while encouraging open lines of communication, ensuring all teams are aligned with overall organizational objectives.

Share your methodologies or frameworks that help balance speed with safety in product development. Examples such as Agile methodologies, regular code reviews, and safety checks before deployment can provide insight into your ability to maintain quality while accelerating timelines.

Provide a detailed account of a specific project, including the challenges faced, your approach to problem-solving, and the ultimate outcomes. Highlight your leadership and decision-making skills to showcase how you effectively navigated issues and achieved results.

Discuss your commitment to continuous learning and professional development, whether through attending conferences, participating in webinars, or engaging with industry literature. Mention specific sources that keep you updated on trends in software engineering and AI.

Talk about strategies you would implement, such as encouraging team brainstorming sessions, allowing time for experimentation, and celebrating wins and learning moments. Illustrate how you create an environment that inspires creativity and risk-taking.

Share a specific incident where you addressed a performance issue directly and fairly. Explain your approach to providing constructive feedback, the steps taken to support improvement, and the eventual outcomes that benefited both the team and individual.

Discuss your experience with various methodologies like Agile, Scrum, or Waterfall, providing insights on why you favor a particular approach. Highlight how your chosen methodology aligns with the goals of enhancing team productivity and delivering high-quality products.

Explain the key performance indicators (KPIs) and metrics you track to assess engineering success, such as deployment frequency, lead time for changes, and team engagement scores. Illustrate how these metrics align with organizational goals.

Articulate your views on the importance of collaboration, emphasizing how it fosters innovation, enhances problem-solving, and improves project outcomes. Provide examples of how you've built collaborative environments in previous roles.