Maintain build servers, build scripts, containers, toolchains, Yocto/BitBake environments, and CI pipelines.
Keep builds reproducible and shared development infrastructure reliable.
Investigate and resolve build and CI failures.
Automate recurring build, integration, and release tasks.
Maintain artifacts, versioning, tagging, and release traceability.
Integrate software and firmware delivered by internal teams and external technology partners.
Maintain integration branches and resolve complex Git integration conflicts.
Manage compatibility across independently versioned firmware, Linux software, middleware, and vendor components.
Maintain clear version matrices defining validated component combinations.
Produce traceable integrated builds for development, QA, and manufacturing.
Investigate problems spanning firmware, Linux, middleware, transport, and processor boundaries.
Validate software changes that require system-level technical knowledge beyond normal product QA.
Verify bug fixes and technical stories by examining logs, services, processes, IPC, network traffic, system state, and interactions between processors and software components.
Investigate systemd/journald logs, crashes, traces, and runtime behavior to confirm whether changes actually resolve the underlying problem.
Develop repeatable tests for technical requirements that are difficult to verify through user-facing QA.
Verify compatibility across firmware/software version combinations.
Work with developers when failures cross subsystem boundaries and help determine where the problem originates.
Automate recurring integration and system-level validation where practical.
Giving coding agents controlled access to multiple repositories, Git history, build results, logs, and test results.
Automating cross-repository investigation of difficult system-level bugs.
Tracing interfaces, dependencies, and changes across subsystems.
Comparing failing and known-good builds.
Generating diagnostic tests and investigation steps.
Apply for this job in 1 click
Skip the repetitive application forms
Install the Base Career Chrome Extension and autofill job applications across major job boards with your profile.
Trusted by over 500,000 job seekers on Base Career
Integrating AI-assisted analysis into build, debugging, and failure-triage workflows.
Yocto / BitBake build systems and embedded Linux development/troubleshooting — mandatory.
C/C++ codebases in embedded environments.
Advanced Git: branching, merging, rebasing, and complex conflict resolution across vendor and internal development streams.
Automated build or CI infrastructure such as Jenkins, GitLab CI, GitHub Actions, or custom build servers.
Python, Bash, or similar scripting for build, release, and engineering automation.
Docker or comparable container tooling for reproducible build environments.
Systematic debugging across subsystem boundaries , including systems involving multiple processors, IPC, serial consoles, and system logs such as systemd/journald.
Ability to investigate unfamiliar systems by gathering evidence, forming hypotheses, and isolating root causes.
Repository-scale or multi-repository code analysis.
Integrating LLM APIs or coding agents with repositories, build/test infrastructure, or diagnostic data.
Tool calling, MCP, agent orchestration, or similar mechanisms.
Automated debugging, test generation, failure triage, or engineering analysis.
Developers do not lose productive time fixing shared build infrastructure.
External software deliveries are integrated predictably without destabilizing active development.
The team always knows which firmware and software versions belong together.
Technical integration problems are caught and diagnosed before becoming product-level QA problems.
QA receives stable, traceable, and documented builds.
Senior developers spend less time on recurring build, merge, and release work.
Cross-system bugs are diagnosed systematically rather than relying on tribal knowledge.
Useful AI-assisted engineering capabilities evolve from individual tool usage into repeatable team workflows.
Describe one difficult embedded integration or build problem you personally diagnosed. What initially appeared to be wrong, what evidence did you gather, and how did you isolate the actual root cause?
Describe one build, test, integration, or release workflow you personally automated. What manual work did it replace, and how was it implemented?
Optional: Describe one engineering workflow where you used LLMs, APIs, or coding agents programmatically rather than through an interactive web chat interface.
About PML Sound International
Verified company details for this employer are not available yet.