Main Missions of the System Architect :
* Design advanced MCU and DSP products that are efficient, compact, and suitable for battery-powered use.
* Turn customer and market requirements into actionable technical specifications, ensuring that each feature aligns with user needs.
* Decide how different functions should be divided between hardware and firmware, analyzing trade-offs to achieve the best balance of performance, cost, and power efficiency.
* Work with business leaders, design teams, marketing, and other departments to promote a unified product development approach, maximizing IP (Intellectual Property) reuse and reducing development costs.
* Act as the technical point person for customers, helping them align their goals with the long-term roadmap and bringing new business opportunities to the company.
The successful System Architect should have part or entire set of skills mentioned below :
* 7+ years of experience in mixed-signal semiconductor design with low-power MCU/DSP expertise.
* Strong background in system architecture, IP reuse, and system partitioning for power-efficient design.
* Strong background in system-level design, particularly for industrial or medical devices.
* Ability to balance design choices against business goals.
* Proven experience in customer-facing roles, with clear communication skills for translating technical insights to various stakeholders.
* Experience working cross-functionally and promoting IP reuse to streamline development and maximize efficiency.
Technical Skills must/nice to have :
* Languages: Verilog, SystemVerilog
* Verification Methods: UVM, Static and Dynamic Verification
* System Partitioning: Expertise in balancing hardware/software partitioning for power efficiency
* Low-Power Design Concepts: Deep knowledge of low-power, mixed-signal design principles for battery-operated devices
* Product Feasibility and Costing: Tools for feasibility analysis, cost estimation, and technical assessments
* Collaboration Tools: Familiarity with IP reuse frameworks, platform-based product development approaches
* Industry Knowledge: Experience with industrial and medical device standards, safety requirements, and regulatory considerations,
* Firmware Development Needs: Understanding firmware requirements for programmable architectures to guide system-level design