Engineering Manager with Networking/Hardware background

Role overview Lead delivery and people development across software engineering, quality assurance, or observability projects, drawing on a hands-on technical background to guide teams and client discussions. This is a non-coding management role with opportunities in either networking and hardware or observability and QA; project scope ranges from team augmentation to complex delivery engagements.

Responsibilities - Clarify client goals and technical requirements, facilitate architecture discussions, and align decisions with client leads. - Track delivery health, manage risks, scope changes, and dependencies, and help teams resolve blockers. - Support engineers’ growth through career guidance, one-to-ones, performance feedback, and conflict resolution. - Coordinate with other engineering and project managers across a portfolio of engagements. - Contribute to presales and business development, and visit clients occasionally.

Requirements - At least 7 years of experience in a relevant domain and 3 years in a people-management role, such as project, engineering, delivery, technical, or QA leadership. - Prior hands-on engineering experience and the ability to discuss technical details with engineers and client architects. - Strong foundations in Linux, networking concepts, and protocols such as L2/L3. - Practical understanding of CI/CD, test automation, and software delivery practices. - Proven ability to lead teams, build trust, support career development, and handle difficult conversations. - Fluent English at C1 level or above for written and spoken work with international stakeholders.

Nice to have - Experience in consulting, outsourcing, or software services, including management of external client expectations. - For networking and hardware projects: experience with network adapters, SmartNICs, DPUs/IPUs, network operating systems, hardware bring-up, drivers, or porting to new hardware. - For observability and QA projects: experience with monitoring domains or tools such as APM, NPM, Grafana, Splunk, Prometheus, or ELK; network testing, benchmarking, or testbed orchestration; and cloud, virtualization, or container infrastructure.

Benefits and work setup - Remote, hybrid, or office-based arrangements, with flexible working hours. Some afternoon work may be needed for clients in the United States. - Teams typically have fewer than 10 people; occasional client travel is usually up to twice per year. - Internal training, a training budget, supported onboarding, and the option to change projects.