Manager, Software Engineering

About the role

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Apply the principle of fixing the process rather than automating broken steps by deeply engaging with the work to validate solutions.

Manage performance actively by setting clear expectations, giving direct feedback, recognizing strong results, and addressing underperformance without delay.

Model AI-native development practices in planning, communication, analysis, and day-to-day operations as a manager.

Clarify priorities and rationale for the team so individuals understand their work and its purpose amid ambiguity.

Requirements

Demonstrate experience managing a software engineering team of meaningful size with a track record of hiring, developing, and managing direct reports.

Show proven ability to own end-to-end delivery across multiple concurrent workstreams with accountability for outcomes.

Use kanban-based delivery fluently, including WIP management, flow metrics, continuous prioritization, and outcome-based planning.

Exercise judgment to weigh trade-offs and make defensible decisions while communicating clearly to engineers and senior leadership.

Employ AI-assisted development tools and agentic systems with depth, forming and modeling standards for engineers on your team.

Approach change with curiosity and adaptability, engaging rather than resisting new tools, processes, and circumstances.

Practice high judgment in ambiguous situations by weighing competing priorities and taking ownership of results.

Maintain clarity for the team in a fast-moving environment through strong written and verbal communication.

Drive scope and priority decisions at the team level, linking work to measurable business outcomes and challenging misaligned initiatives.

Practical notes

This role is based in Boston, Massachusetts, with hybrid work expectations.

You must hold at least a Bachelor of Science in Computer Science or equivalent work experience.

An equal opportunity employer, Vestmark prohibits employment discrimination and requires compliance with Massachusetts law on lie detector tests.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

The team and operating model are new, offering an opportunity to shape structure and culture.

Success is tied to measurable efficiency and outcome metrics tied to a large-scale wealth management platform.

The role expects hands-on AI fluency and active modeling of AI-native practices for the engineering team.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.