Firmware Infrastructure Engineer

About Sibros Technologies

Who We Are

Sibros is accelerating the future of SDV excellence with its Deep Connected Platform™ that orchestrates full vehicle software update management, vehicle analytics, and remote commands in one integrated system. Adaptable to any vehicle architecture, Sibros’ platform meets stringent safety, security, and compliance standards, propelling OEMs to innovate new connected vehicle use cases across fleet management, predictive maintenance, data monetization, and beyond.

Learn more at www.sibros.tech.

Our Mission

Our mission is to help our customers get the most value out of their connected devices.

Follow us on

LinkedIn | Youtube | Instagram

About the Role:

Job Title: Firmware Infrastructure Engineer

Experience: 4-9 years

Job Level: L4/L5

Reporting to: Manager, Firmware Infrastructure

Job Type: Full-Time

The Firmware Infrastructure team owns the Bazel build system, CI/CD pipelines, and developer tooling that every firmware engineer at Sibros depends on. The team is mostly based in the US, while most of the engineers it supports work from India.

This role is the team's presence in IST. You will sit with the firmware and solutions engineers in India, review their changes to infrastructure-owned code, and get the team involved early when a new customer request or design is going to need infrastructure work. The aim is to catch issues early, so changes move through review faster and infrastructure work is planned in from the start.

What You'll Do

• Review infrastructure changes in IST. Review merge requests that touch Bazel rules, .bzl files, CI configuration, and other infrastructure-owned files. Leave clear, actionable feedback and work with the author until the change is ready.
• Hold the quality bar. Apply the team's review guidelines, which you will help write and maintain. Push back when a change duplicates existing logic, pulls in a toolchain or dependency that is not needed, or works around the build system instead of with it. You will often be the one saying no to peers, and you need to be comfortable doing that respectfully.
• Scope requests early. Join planning and customer-driven discussions with the India firmware and solutions teams, and judge whether a piece of work needs Firmware Infrastructure involved and how much. Raise it with the team before it turns into an urgent review.
• Teach the practices. Help engineers in India understand why the build and CI work the way they do, so fewer issues reach review in the first place.
• Contribute to the team's backlog. Pick up infrastructure work that is not time-zone sensitive, such as Python tooling, dependency and package upgrades, and CI improvements. The scope here grows with your experience.

What You Should Know

• Bazel. Working knowledge of Bazel in a real codebase: you can read and modify BUILD and .bzl files, understand how rules, targets, and dependencies fit together, and spot when a change is going the wrong way. Deep knowledge of Bazel internals is not required.
• Python. You write Python as software, not only as scripts: structured code, tests, packaging, and code someone else can maintain. Starlark is a Python dialect, so this matters for the Bazel work too.
• CI/CD. Hands-on experience configuring and debugging CI/CD pipelines. GitLab CI is what we use; Jenkins, Buildkite, GitHub Actions, or similar experience transfers.
• Linux. Linux is your day-to-day development environment. You are comfortable on the command line and understand the basics of how the system works underneath.
• Git. Solid understanding of Git and merge request workflows.
• Judgment and communication. You can read a change, understand what it is trying to do, and explain clearly why it should be done differently. Fluent in English.
• Time zone overlap. Willing to shift your working hours during the first few months to overlap with the US-based team while you ramp up.

Preferred Qualifications

• Writing custom Bazel rules, macros, or toolchain configurations.
• Experience building or maintaining build systems for C/C++ or embedded firmware. Writing C/C++ is not required.
• Deeper Linux systems work, such as building and tuning CI build nodes, storage and partitioning, or containerized and reproducible builds.
• Experience with GCP or AWS, and Kubernetes.
• Comfortable using LLM-based tooling in daily engineering work, including agentic coding workflows.
• Experience reviewing code for engineers outside your own team.

What we offer

• Competitive Compensation: A package inclusive of performance incentives.
• Growth Environment: A dynamic work environment with a flat hierarchy and rapid career advancement.
• Learning & Development: Access to continuous learning and professional development opportunities.
• Work-Life Balance: Flexible working hours and a culture that promotes balance.
• Comprehensive Benefits: Health insurance and wellness programs.
• Modern Policy: Flexible vacation and paid time off,you decide when you need a break.
• Team Culture: Regular team events, off-sites, and a budget for online courses, books, and conferences.