A

Ai2iO

Manager, Software Engineering - Engineering Tools

Engineering LeadershipUpdated on Nov 11
Full-timeRemote in USA$120.8k - $148.3k /yr

About the Job

Requirements

  • At least 8 years of professional software engineering or closely related technical-delivery experience, including at least 2 years of formal people management within a software organization.
  • Meaningful professional experience with Autodesk Revit and AEC, BIM, design technology, engineering design, construction technology, or commissioning workflows, with practical understanding of how Revit-dependent tools affect real project work.
  • Demonstrated experience managing software engineers and technical leaders while preserving Software Engineer Technical Lead and Architect authority over feasibility, estimates, standards, implementation, and architecture.
  • Experience managing performance, difficult feedback, recognition, development, reviews, promotions, and sustained performance concerns.
  • Experience with workforce planning, hiring, onboarding, skill-gap assessment, retention, succession, and staffing recommendations for specialized teams.
  • Sufficient software-engineering depth to assess C#/.NET and web application architecture, APIs, data, identity, security, testing, CI/CD, observability, dependency, delivery, and production-support risks without directing implementation.
  • Ability to communicate across software engineering, mechanical and electrical design, BIM, commissioning, product, quality, project delivery, adoption, and leadership audiences.
  • Experience supporting software across deployment, installers, licensing, version compatibility, documentation, training, support, or productization concerns.
  • Experience managing distributed or remote teams and improving operating practices, communication, onboarding, and leadership continuity.
  • Bachelor's degree in Mechanical Engineering, Electrical Engineering, Computer Science, Software Engineering, Information Systems, Architecture, Construction Management, or a materially related field, or equivalent experience is preferred.
  • Hands-on production experience with Autodesk Revit, particularly MEP models, families, parameters, worksharing, project standards, or model-dependent workflows, is preferred.
  • A professional background as a mechanical or electrical engineer, BIM or design-technology leader, commissioning professional, AEC technology specialist, or software leader supporting Revit products is preferred.
  • Experience managing teams that build Revit add-ins, Revit API solutions, Blazor applications, installers, deployment tooling, licensing systems, integrations, or model-dependent software is preferred.
  • Experience preparing internal software for affiliate, contractor, client, or public use, including deployment, licensing, support, documentation, quality, and adoption is preferred.
  • Experience with Microsoft Azure, C#/.NET, ASP.NET Blazor, SQL Server, Azure DevOps, Microsoft Graph API, Autodesk Platform Services, or adjacent platforms is preferred.
  • Relevant management, coaching, Autodesk, BIM, Agile, project-management, or technical certifications are preferred.

Responsibilities

  • Serve as the formal people manager for all engineers and Technical Leads assigned to the specialty team through regular one-on-ones, clear expectations, timely feedback, performance reviews, professional development planning, and credible support for every direct report.
  • Provide recognition and development feedback throughout the year and address sustained performance concerns through clear expectations, documented support, follow-through, and appropriate organizational processes.
  • Connect individual goals to meaningful assignments, coaching, learning, mentoring, and increasing ownership without promising advancement before readiness is demonstrated.
  • Partner with Technical Leads to understand technical contribution and development needs while retaining accountability for career evaluation, formal performance decisions, employee relations, and team health.
  • Maintain a current view of capacity, critical skills, experience distribution, key-person dependencies, succession risk, and staffing needs.
  • Identify capability gaps and coordinate learning, pairing, assignments, mentoring, hiring, and onboarding plans.
  • Develop future Technical Leads and management candidates through scoped assignments, calibrated feedback, explicit readiness criteria, and partnership with current leaders.
  • Reduce leadership and knowledge-continuity risk through distributed ownership, documentation, coverage, and succession options.
  • Ensure teams have sufficient staffing, capability, role clarity, decision pathways, tools, and organizational support to deliver sustainably.
  • Partner with Technical Leads and Project Managers on delivery health, risk, dependencies, capacity, and recovery without replacing technical or project-management ownership.
  • Ensure material delivery problems receive appropriate management intervention, including staffing changes, escalation, cross-team negotiation, or leadership decisions.
  • Review recurring delays, incidents, rework, quality concerns, support burdens, and workload imbalance to identify organizational or capability improvements.
  • Protect teams from sustained overload and commitments incompatible with available capacity.
  • Use practical Revit and AEC fluency to help software engineers understand the design, BIM, commissioning, and project-delivery context surrounding Engineering Tools work.
  • Help Product Owners, Business Analysts, Technical Leads, and engineers clarify organization-specific Revit content, standards, parameters, families, model structures, workflows, and downstream constraints without assuming product or technical authority.
  • Recognize when staffing, sequencing, support, or training approaches do not reflect real design workflows, supported Revit versions, model integrity, user productivity, or discipline-specific needs.
  • Facilitate clear communication between software specialists and mechanical, electrical, commissioning, BIM, design-technology, and field stakeholders.
  • Promote solutions and practices that are understandable, supportable, maintainable, reusable, and appropriate for real engineering project conditions.
  • Own workforce capability, staffing, development, and training plans spanning C#/.NET, Revit add-ins and API patterns, Blazor applications, data and integrations, installers, deployment, licensing, diagnostics, quality, support, and commercialization readiness.
  • Ensure the team has the mix of software-engineering and AEC-domain capability required to maintain internal tools while preparing selected products for broader use.
  • Develop learning plans that help software engineers understand Revit workflows and help domain practitioners work effectively with software teams.
  • Reduce single-person dependencies in organization-specific workflow knowledge, deployment, installer behavior, licensing, supported-version strategy, model-dependent testing, and operational support.
  • Partner with Technical Leads, Architects, Product Owners, Project Managers, Software Quality, Product Adoption, and support partners on releases, deployment, licensing, installation, compatibility, documentation, training, and support.
  • Plan the people, process, and capability changes required when selected internal tools are prepared for affiliate, contractor, client, or public use.
  • Use domain awareness to identify risks involving organization-specific content, external users, permissions, data handling, installer behavior, licensing, support, and adoption.
  • Ensure credible support and escalation coverage for Revit add-ins, Blazor applications, integrations, installers, deployment services, and licensing components.
  • Establish practices that support candid discussion of risks, uncertainty, mistakes, technical disagreements, workload concerns, and alternative viewpoints without individual blame.
  • Address observable patterns such as unresolved conflict, sustained overload, escalation failures, knowledge bottlenecks, or reluctance to surface delivery problems.
  • Maintain reliable communication rhythms so engineers understand priorities, decisions, role boundaries, and available support.
  • Address performance, conduct, and employee-relations concerns through appropriate management processes rather than transferring formal accountability to Technical Leads.
  • Partner with the Director on workforce planning, role requirements, interview plans, evaluation criteria, and hiring priorities.
  • Lead structured and equitable selection processes, calibrate interviewers, document evidence, and make clear candidate recommendations.
  • Own consistent onboarding expectations, including role clarity, access, relationships, learning objectives, 30/60/90-day plans, and ramp check-ins.
  • Evaluate onboarding effectiveness through independence, role understanding, contribution, and feedback and improve the process based on evidence.
  • Identify retention risks early and coordinate appropriate responses.
  • Partner with Technical Leads, who own technical feasibility, estimates, dependencies, execution health, engineering standards, implementation direction, and team-level technical decisions.
  • Partner with Architects, who own cross-team architecture, technical standards, governance, and long-term technical direction.
  • Partner with Project Managers, who own the integrated schedule, formal stakeholder communication, scope coordination, project governance, and overall delivery process.
  • Partner with Product Owners and Business Analysts while preserving their authority for product value, priority, requirements, workflow analysis, and backlog readiness.
  • Use technical and domain fluency to understand risk, ask informed questions, clarify context, develop people, and improve the environment without becoming the default Technical Lead, Architect, Product Owner, Business Analyst, or Project Manager.
  • Lead improvements to performance management, career development, hiring, onboarding, workforce planning, team operating practices, and leadership continuity.
  • Identify patterns spanning teams and coordinate improvements with peer Managers, Technical Leads, Architects, Project Managers, Product Owners, Business Analysts, and the Director.
  • Contribute to department-level capability planning, organizational design, role definition, career frameworks, cross-team staffing, leadership development, and organizational change.
  • Evaluate whether adopted practices improve clarity, fairness, staffing effectiveness, internal growth, management consistency, and sustainability.
  • Represent capacity, capability, succession, and organizational risk in department planning with concise evidence and decision-ready recommendations.
  • Travel up to 5%, which may include travel to any or all 50 U.S. states.

About the Company

Company size
Not listed
Company stage
Not listed
Total funding
Not listed
Headquarters
Not listed
Founded
Not listed

Recently Posted Jobs

Explore more opportunities at Ai2iO

See more jobs