Software Engineering Manager Jobs

About The Position

Requirements

• A BS in computer engineering, computer science, electrical engineering, or a related discipline, or equivalent practical experience.
• Substantial experience contributing to the development of complex embedded software, firmware, or closely related systems.
• Demonstrated technical judgment, including experience helping define architectures, resolve significant technical risks, guide integration, or diagnose complex system behavior.
• Demonstrated success leading and developing engineers. This evidence may come from formal management, technical or project leadership, mentoring, or a combination of these experiences.
• Ability to organize ambiguous technical work, establish priorities and ownership, and guide a team toward clear decisions and deliverables.
• Ability to work effectively across engineering disciplines and communicate decisions, risks, and tradeoffs to both technical and nontechnical audiences.
• Embedded C or C++ and resource-constrained systems
• Real-time systems, interrupts, concurrency, synchronization, timing, or deterministic behavior
• Embedded Linux, RTOS-based applications, board-support packages, bootloaders, or device drivers
• Hardware/software interfaces, networking, communications protocols, data acquisition, calibration, or hardware-control software
• Software architecture, interface definition, state modeling, error handling, requirements development, or system decomposition
• Unit, integration, regression, and hardware-in-the-loop testing; static analysis; continuous integration; or controlled build and release practices
• Investigation of interactions among software, firmware, FPGA logic, digital hardware, analog hardware, and physical system behavior

Nice To Haves

• Experience with every item above is not required. We are interested in the candidate's command of engineering fundamentals, the quality of their decisions, how they approach unfamiliar problems, and their ability to recognize when specialist expertise is needed.

Responsibilities

• Guide embedded software and firmware architecture for new products and major product revisions.
• Help translate product and system needs into clear, implementable, and testable software requirements, interfaces, and acceptance criteria.
• Work with domain experts to allocate functionality appropriately across processors, programmable logic, hardware, firmware, and application software.
• Promote maintainable software structures, stable interfaces, well-understood data flows and state behavior, and effective error-handling and recovery strategies.
• Lead or facilitate technical trade studies and design reviews involving performance, timing, communications, memory, power, security, testability, and maintainability.
• Ensure important technical decisions, assumptions, risks, and tradeoffs are supported by appropriate analysis, prototyping, measurement, or other objective evidence.
• Establish development and verification practices appropriate to the product risk, including design and code review, configuration management, reproducible builds, progressive integration, regression testing, release control, and structured defect investigation.
• Encourage purposeful experimentation to answer defined technical questions and use the results to improve requirements, architecture, plans, and decisions.
• Identify technical risks early and establish practical plans to reduce or retire them.
• Recruit, retain, coach, and develop embedded-software and firmware engineers.
• Establish clear expectations for technical quality, ownership, documentation, communication, collaboration, and execution.
• Provide timely, candid, and constructive feedback, recognize strong performance, and address performance concerns fairly and directly.
• Delegate meaningful ownership while providing the direction, context, and support engineers need to succeed.
• Assign work with consideration for technical needs, project priorities, employee capabilities, workload, and development goals.
• Develop engineers' capabilities in architecture, requirements, design analysis, testing, debugging, communication, and cross-disciplinary systems thinking.
• Build a culture in which engineers raise risks early, challenge assumptions constructively, debate technical alternatives objectively, and learn from mistakes.
• Hold the team accountable for complete engineering deliverables—including requirements, design, implementation, documentation, verification, integration, release, and lifecycle support—not only for producing code.
• Give the software team clear priorities, decision frameworks, ownership boundaries, and definitions of success.
• Develop credible plans and estimates based on technical scope, uncertainty, dependencies, staffing, integration needs, and verification effort.
• Distinguish preliminary estimates from commitments supported by adequate requirements and architecture work.
• Maintain visibility into progress, technical risk, resource constraints, dependencies, and unresolved decisions.
• Balance new-product development with sustaining work, defect correction, infrastructure improvement, and appropriate reduction of technical debt.
• Help the team make timely decisions without bypassing necessary engineering work; tailor the level of analysis, documentation, review, and process to the consequences and uncertainty involved.
• Strengthen the team's ability to plan, design, implement, test, integrate, release, and support complex products with increasing independence.
• Represent software opportunities, constraints, and risks in product, system, and business decisions.
• Partner closely with systems, electrical, RF, FPGA, test, quality, manufacturing, service, and product-management teams.
• Help establish clear ownership and resolve priorities, requirements, interfaces, and dependencies that cross functional boundaries.
• Communicate technical status, uncertainty, tradeoffs, resource needs, and risk clearly to engineers, managers, executives, and other stakeholders.
• Contribute to product feasibility, project authorization, architecture reviews, risk assessments, phase-gate decisions, and lifecycle planning.
• Support the testability, diagnosability, manufacturability, serviceability, security, and long-term maintainability of the complete product.
• Contribute to staffing, capability, technology, platform, supplier, and obsolescence plans that extend beyond a single project.
• Improve engineering practices across the organization in ways appropriate to the products, risks, team, and scale of the business.

Benefits

• medical/dental/vision
• basic life
• short term and long term disability
• paid parental leave
• 401K
• tuition assistance
• gainshare bonus