Technical Specialist

As a Technical Specialist at Fusion Plus Solutions, you will be responsible for developing and validating control algorithms, managing software architecture for CAB ECU applications, and ensuring compliance with coding standards. You will also mentor junior engineers, oversee software integration processes, and ensure the successful release of software for Body Control Modules in commercial vehicles.

To qualify for the Technical Specialist position at Fusion Plus Solutions, candidates must have a Bachelor’s degree in Engineering or Engineering Technology with at least 12 years of experience, or a Master’s degree with at least 8 years of experience in product design and development. Additionally, a minimum of 2 years in a leadership role related to specialized or new technologies is required.

A Technical Specialist at Fusion Plus Solutions will engage in the full V-cycle of embedded development, including system-level requirements gathering, detailed software design, coding, testing, and vehicle-level testing. Your role will focus on the complete lifecycle of ECU applications development for commercial vehicles, ensuring high quality and performance standards throughout.

Fusion Plus Solutions is committed to the professional growth of its Technical Specialists by providing mentoring opportunities, supporting continued education, and encouraging participation in leading industry practices and standards. As a mentor, you’ll also guide other engineers in their understanding of technical requirements and best practices, fostering a culture of learning and innovation.

Yes, the Technical Specialist position at Fusion Plus Solutions requires onsite work starting from day one. This setup promotes collaboration and immediate engagement with project teams, which is essential for developing high-quality embedded software solutions.

In your response, highlight specific projects you’ve worked on that involved embedded software development, emphasizing your role, the technologies used, and the outcomes. Include details about the control algorithms you developed and how they contributed to the overall success of the application.

Outline a step-by-step approach detailing how you gather requirements, design software architecture, conduct testing, and manage releases. Stress the importance of effective communication with project managers and stakeholders throughout each phase.

Explain your methodology for adhering to coding standards—this could include using checklists, participating in code reviews, and staying updated on best practices in the industry. Discuss any tools or frameworks you utilize to maintain code quality.

Share a specific example where you guided a junior engineer through a challenging project or technical problem. Focus on the strategies you used to mentor them, how you supported their development, and the positive results that followed.

Discuss instances where you identified performance issues in software. Explain the steps you took for analysis, testing, and implementing optimizations, showcasing your understanding of the balance between performance and maintainability.

Identify the programming languages and tools (such as C, C++, MATLAB, or specific IDEs) relevant to embedded software development that you are experienced with. Be sure to mention how and where you applied these skills in previous projects.

Reflect on the complexities involved in developing ECU applications, such as integration with hardware, real-time constraints, and the safety-critical nature of automotive systems. Highlight your strategies for navigating these challenges in previous roles.

Provide insights on your experience with software version control, deployment processes, and documentation practices needed for successful software releases. Mention any tools you have used for managing releases effectively.

Emphasize the importance of maintaining clear and comprehensive documentation throughout the development process, and discuss any systems or tools you utilize for this purpose. Use examples that illustrate effective practices you’ve employed in past projects.

Recall an experience where you addressed a challenging issue that arose after deployment. Describe your approach to troubleshooting, working with stakeholders or clients, and how you ensured that a solution was implemented swiftly and efficiently.