Software Engineer, Build Infrastructure (ADAS)

As a Software Engineer specializing in Build Infrastructure at Woven by Toyota, you will be responsible for consolidating and integrating large-scale C++ software stacks, maintaining software systems, and supporting CI/CD pipelines. You'll also engage with various engineering sub-teams, assisting with troubleshooting build failures, establishing best practices, and configuring environments that cater to new projects.

To be a suitable candidate for the Software Engineer, Build Infrastructure position at Woven by Toyota, you should possess extensive experience in C++, Ubuntu or Linux operating systems, and Git. Additionally, moderate experience with Bazel and scripting languages like bash or Python will be beneficial, along with some familiarity with CI/CD solutions.

In the Software Engineer, Build Infrastructure role at Woven by Toyota, you'll engage with projects related to autonomous driving technology. This includes working on core software systems that enhance everyday software development across multiple teams, focusing on build, test, and deployment processes crucial for the performance and safety of autonomous vehicles.

At Woven by Toyota, the work environment emphasizes collaboration and innovation. As a Software Engineer on the Build Infrastructure team, you'll work in a supportive atmosphere that values problem-solving, encourages relationship building among teams, and offers flexibility with a focus on impactful work that shapes the future of mobility.

A Software Engineer in Build Infrastructure at Woven by Toyota can expect ample career growth opportunities. As you support autonomous driving projects and expand your skillset in modern C++, CI/CD systems, and various infrastructure tools, you’ll be well-positioned for advancement within our dynamic company that values innovation and personal development.

When addressing your experience with C++, focus on specific projects where you've utilized modern C++ standards. Discuss any challenges faced and how you overcame them while adapting to large-scale software environments. Highlight your contributions to code quality and performance improvements.

In troubleshooting build failures, I recommend systematically isolating the issue by checking logs, analyzing recent changes, and collaborating with affected sub-teams. Share examples of your strategies for diagnosing and resolving build issues, emphasizing your collaborative mindset and problem-solving skills.

Discuss specific CI/CD tools like GitHub Actions or BuildKite that you have used, detailing how you set them up and maintained pipelines for projects. Mention any notable improvements in deployment speeds or efficiency that resulted from your implementations.

Emphasize the importance of effective dependency management in maintaining code integrity, preventing conflicts, and ensuring smooth builds. Talk about any tools you’ve used for dependency management, and share your experiences optimizing these processes within your previous roles.

Explain your methods for staying updated, whether through online courses, industry blogs, or community forums. Share insights on how this knowledge has influenced your past work and helped improve the CI/CD processes you've implemented.

Detail your familiarity with cloud platforms like AWS or GCP, discussing specific projects where you've leveraged these technologies. Illustrate how you've incorporated cloud infrastructure into CI/CD solutions to enhance scalability and reliability.

When working with multiple sub-teams, I prioritize tasks based on urgency and impact. Describe your approach to balancing requests, communicating transparently with teams, and ensuring that critical needs are met without compromising the quality of your work.

Share your experiences with automation tools and processes that you've employed to streamline builds. Provide examples of how automation improved efficiency in your previous roles and emphasizes the outcomes achieved.

Discuss your strategies for setting up a robust and flexible build environment, referencing specific tools you've used, like Bazel or Docker. Highlight your focus on scalability and how you adapt configurations as project needs evolve.

Talk about the practices you implement to ensure high quality, such as thorough testing, leveraging CI/CD pipelines effectively, and regular code reviews. Share how these strategies contributed to successful deployments in your past roles.