1

Assistant Engineering Manager Jobs in Massachusetts

RESPONSIBILITIES * Assist the Director of Engineering / Assistant Director of Engineering/ Engineering Manager in the full upkeep of the preventative maintenance, including the keeping of logs on ...

RESPONSIBILITIES * Assist the Director of Engineering / Assistant Director of Engineering/ Engineering Manager in the full upkeep of the preventative maintenance, including the keeping of logs on ...

The service has multiple facets of delivery including and on-prem appliance, a traditional datacenter and cluster of virtualized servers, a team of scan engineers who assist customers to configure ...

The service has multiple facets of delivery including and on-prem appliance, a traditional datacenter and cluster of virtualized servers, a team of scan engineers who assist customers to configure ...

Showing results 41-60

Assistant Engineering Manager information

See Massachusetts salary details

$43.4K

$84.8K

$120.2K

How much do assistant engineering manager jobs pay per year?

As of Aug 18, 2026, the average yearly pay for assistant engineering manager in Massachusetts is $84,817.00, according to ZipRecruiter salary data. Most workers in this role earn between $76,167.00 and $92,795.00 per year, depending on experience, location, and employer.

What is an assistant engineering manager?

Assistant Engineering Managers support the Engineering Manager in overseeing engineering projects, coordinating teams, and ensuring that technical tasks are completed efficiently and on schedule. They help manage day-to-day operations, assist with project planning, and often serve as a bridge between engineers and upper management. Their role may also include monitoring budgets, ensuring safety standards, and troubleshooting technical issues. This position is ideal for someone with strong technical expertise and leadership skills aiming to advance into higher management roles.

What are the key skills and qualifications needed to thrive as an assistant engineering manager?

To thrive as an Assistant Engineering Manager, you need a solid background in engineering principles, project management experience, and typically a bachelor's degree in engineering or a related field. Familiarity with technical tools like AutoCAD, project management software (e.g., Microsoft Project), and knowledge of industry standards or certifications (such as PMP or Lean Six Sigma) are often required. Strong leadership, problem-solving, and communication skills are vital for coordinating teams and ensuring project goals are met. These skills and qualifications are crucial for delivering successful engineering projects on time and within budget while fostering a productive team environment.

What are some typical challenges an assistant engineering manager faces when transitioning from an individual contributor to a leadership role?

One common challenge for new Assistant Engineering Managers is balancing hands-on technical work with leadership responsibilities such as team coordination, mentoring, and project oversight. Adapting to this dual role requires strong time management and communication skills, as you'll need to guide your team while still contributing your technical expertise. Additionally, you may encounter situations where you must resolve conflicts or make decisions that impact project timelines and team morale. Support from senior management and a willingness to learn from feedback can help you navigate these challenges successfully.

What is the difference between Assistant Engineering Manager vs Mechanical Engineer?

AspectAssistant Engineering ManagerMechanical Engineer
Required CredentialsBachelor's degree in engineering, management experience often preferredBachelor's or Master's degree in Mechanical Engineering
Work EnvironmentSupervisory role overseeing engineering teams and projectsDesign, analysis, and development of mechanical systems
Employer & Industry UsageManufacturing, construction, engineering firmsAutomotive, aerospace, manufacturing, product design

The Assistant Engineering Manager typically oversees engineering teams and manages projects, requiring leadership skills and management experience. Mechanical Engineers focus on designing and analyzing mechanical systems, primarily requiring technical expertise. Both roles are common in manufacturing and engineering industries, but the Assistant Engineering Manager has a broader supervisory scope.

Is an assistant engineering manager a stressful job?

An assistant engineering manager role can be stressful due to responsibilities such as project management, team coordination, and meeting deadlines. The level of stress often depends on workload, organizational culture, and experience with technical and leadership skills.

What are the most commonly searched types of Engineering Manager jobs in Massachusetts?

The most popular types of Engineering Manager jobs in Massachusetts are:

What are popular job titles related to Assistant Engineering Manager jobs in Massachusetts?

For Assistant Engineering Manager jobs in Massachusetts, the most frequently searched job titles are:

What job categories do people searching Assistant Engineering Manager jobs in Massachusetts look for?

The top searched job categories for Assistant Engineering Manager jobs in Massachusetts are:

What cities in Massachusetts are hiring for Assistant Engineering Manager jobs?

Cities in Massachusetts with the most Assistant Engineering Manager job openings:

Infographic showing various Assistant Engineering Manager job openings in Massachusetts as of August 2026, with employment types broken down into 83% Full Time, 14% Part Time, 1% Temporary, and 2% Contract. Highlights an 84% Physical, 3% Hybrid, and 13% Remote job distribution, with an average salary of $84,817 per year, or $40.8 per hour.

Engineering Operations Manager

QuEra Computing, Inc.

Boston, MA • On-site

Other

Re-posted 2 days ago


Job description

Engineering Operations Manager:
QuEra is seeking an Engineering Operations Manager to make execution across software, hardware, test infrastructure, and QPU programs more predictable, visible, and efficient.
This person will facilitate the operating system around engineering: planning cadence, cross-team dependency visibility, Jira and Confluence hygiene, release and integration coordination, operational metrics, and follow-through on decisions and action items. The role is designed to give engineering leaders and senior technical staff more time for architecture, technical decisions, team development, and delivery.
This is a hands-on individual-contributor role with broad organizational influence. It is not a substitute for technical ownership, product management, engineering management, or infrastructure ownership. Engineering and functional leaders remain accountable for priorities, staffing and resource allocation, architecture, technical acceptance criteria, technical risk acceptance, and release or machine go/no-go decisions. The successful candidate will create the structure that lets those functions work together effectively.
What you will own:
  • Facilitate engineering planning and execution
  • Run a consistent planning and review cadence across software, hardware, QPU programs, and test and engineering infrastructure.
  • Translate company and program priorities set by the appropriate leaders into a coherent, capacity-aware engineering plan with named owners, milestones, dependencies, and acceptance criteria supplied or approved by technical owners.
  • Maintain a single, decision-useful view of active initiatives, planned work, critical-path dependencies, risks, and delivery confidence.
  • Facilitate weekly execution reviews, periodic roadmap reviews, release-readiness reviews, and milestone retrospectives.
  • Surface priority or resource conflicts early, document their delivery impact, and bring them to the accountable leader for decision.
  • Track decisions and actions to closure without becoming the priority setter, resource owner, or technical approver.
  • Assist with Jira, Confluence, and GitHub operating discipline
  • Establish and maintain, in partnership with engineering leaders, practical standards for initiative, epic, issue, and release hygiene across engineering Jira projects.
  • Work with technical owners to ensure active work has a clear owner, current status, leadership-approved priority and target, dependency context, and definition of done.
  • Keep Jira roadmaps, Confluence status pages, engineering documentation, and GitHub delivery activity aligned enough to support reliable reporting.
  • Facilitate regular backlog and work-in-progress reviews so accountable leaders can disposition stale, duplicate, unowned, or poorly scoped work.
  • Improve traceability from requirements and engineering decisions through implementation, validation, release, and operational follow-up.
  • Automate recurring status collection and reporting where practical, while preserving clear human ownership of priorities and decisions.

Cross-functional dependency and milestone management:
  • Coordinate dependency visibility among software, hardware, systems, science, test infrastructure, lab operations, procurement, facilities, security, and external partners.
  • Build integrated plans for machine milestones, hardware/software integration gates, testbed readiness, infrastructure transitions, and customer or partner commitments using estimates and technical inputs approved by accountable owners.
  • Track long-lead procurement, vendor, lab, compute, network, storage, test-equipment, and staffing dependencies that can affect engineering delivery.
  • Prepare decision briefs when scope, schedule, capacity, or technical dependencies require leadership tradeoffs.
  • Maintain risk, assumption, issue, and dependency logs for critical programs and ensure mitigations have accountable owners and target dates.
  • Escalate unresolved conflicts without independently committing another team's resources, changing technical scope, or accepting technical risk.

Facilitate release, quality, and operational readiness:
  • Coordinate release and deployment readiness across repositories, CI/CD pipelines, test environments, hardware configurations, and target machines.
  • Facilitate the development and use of lightweight readiness gates covering code, hardware, test evidence, documentation, rollback or recovery plans, observability, and operational ownership; technical owners define and approve the criteria and make go/no-go recommendations.
  • Partner with engineering owners to improve build, test, release, and deployment flow without taking ownership of the underlying technical systems.
  • Coordinate post-incident follow-up, ensuring significant failures produce clear corrective actions, owners, due dates, and updates to engineering plans; the responsible engineering or infrastructure owner leads incident response, diagnosis, and root-cause approval.
  • Track operational and quality signals such as aging work, escaped defects, reopened issues, cycle time, blocked work, release predictability, and action-item closure.

Encourage engineering communications and continuous improvement:
  • Produce concise, trustworthy weekly and monthly engineering updates for technical and company leadership.
  • Create meeting agendas, pre-reads, decision records, and action logs that reduce meeting time and ambiguity.
  • Improve shared onboarding processes and make engineering processes, ownership, and authoritative sources easier to find, while functional leaders retain ownership of role-specific onboarding and technical training.
  • Identify recurring coordination work that should be standardized, automated, delegated, or eliminated.
  • Help pilot and operationalize QuEra's unified hardware/software engineering process, including synchronized planning and integration gates approved by engineering leadership.

Decision-rights summary:
  • The Engineering Operations Manager owns the engineering operating cadence, integrated plan, dependency and risk visibility, reporting, readiness coordination, and action follow-through.
  • Engineering, Product, Science, Hardware, Software, and Test & Engineering Infrastructure leaders retain ownership of strategy and priorities, architecture and design, people management, staffing and resource allocation, technical estimates and acceptance criteria, underlying build/release/deployment systems, incident command and root-cause conclusions, and final technical go/no-go decisions.

We consistently monitor external market data and update base salary ranges accordingly. We determine base compensation decisions on several factors, including as geographic placement, role-specific knowledge, skills, and/or experience. In addition to our base salary offerings, we also provide equity grants for all new hires. $180,000-$250,000. Note: This role is located in Boston, MA and requires you to be on-site 5 days per week.
QuEra is committed to cultivating a diverse work environment and is proud to be an equal opportunity employer. We highly value diversity in our current and future employees and do not discriminate (including in our hiring and promotion practices) based on race, religion, color, national origin, gender, gender expression, sexual orientation, age, marital status, veteran status, disability status, or any other characteristic protected by law.