Cadence Architects’ Post

From IC engineer to C-Level exec, the most effective people I've worked with have one thing in common: they break down and decouple decisions. Optionality, trade-offs, last responsible moment, one-way and two-way door decisions, slicing, MVPs, proof of concepts etc. are all techniques they use for breaking decisions down and getting them made. The best engineers did this when working on code. Rather than trying to decide on all the functionality at once they'd be able to say "I can break this story down into smaller pieces of value that we can get released to users fast" or "we don't need to deliver this piece of functionality now, we can wait until we see how user's respond". The best architects, product managers and business leaders do the same thing. It's a real skill to decouple decisions. It's a real skill to be able to defer parts of a decision to next or later (or even never) to enable faster movement and lower risk. I have always been impressed when I witness it. Often it's obvious with hindsight and sometimes its completely out-of-the-box and you would have never have realised.

Hello All, We are hiring Sr Physical Design Engineers for Bangalore and Noida location. If interested please drop your profile to [email protected] Experience: 5+ years JD: Physical design engineer who have exp in Netlist to GDS flows, and have good exposure to signoff flows. knowledge on Innovas Good knowledge of timing closure in PnR. Skill required on Synthesis/FV/ STA basics , basics of shell scripting , TCL scripting Working on lower Nodes, #physicaldesign #physicalverification #sta #sysnthesis #clp #innovus #primetime #cts #floorplan #powerplan #pnr #routing #scripting #tcl #python #shellscripting

Unity SFB is hiring Enterprise Architecture and Standards in the IT Team for Mumbai. Exp: 15+yrs Location: Seawoods (Navi Mumbai) **Good to be TOGAF certified** Roles and Responsibilities:- 1.      Develop and Maintain Enterprise Architecture (EA): Create, implement, and manage EA frameworks to align IT infrastructure with business goals. 2.      Ensure Compliance: Oversee that all IT deployments (new and legacy) adhere to established EA standards and develop controls for enforcement. 3.      Architectural Leadership: Provide leadership in resolving inter-program and inter-project issues while ensuring alignment with EA. 4.      Business Alignment: Collaborate with business units to understand their needs, drivers, and strategies, ensuring integration with EA initiatives. 5.      Legacy System Review & Migration: Evaluate legacy systems and develop migration roadmaps aligned with EA standards. 6.      Communication and Publicity: Promote awareness of EA across business and IT units, ensuring understanding and adoption. 7.      Auditing and Compliance: Regularly audit systems to ensure adherence to EA standards. 8.      Solution Strategy Development: Assist in formulating IT solution strategies, roadmaps, and compliance methods. 9.      State Architecture Diagrams: Create and update current vs. future state diagrams and lifecycle roadmaps to guide IT evolution. 10.  Training and Skills Development: Organize training programs to align employees' skills with EA and future organizational needs. 11.  Cost Optimization and Future Technology: Recommend strategies to reduce IT costs and identify future technology needs by analyzing industry trends.     #enterprisearchitecture #techarchitecture #ITArchitecture

Don't hire a rockstar engineer who works in isolation. Hire engineers who create engineering programs Engineering programs helped me grow and raise the bar of my organization In my article with Eugene Shulga, where you'll learn - How to start a group - How to manage a group - How to do good reviews Read it here: https://lnkd.in/dJw5jRQv #softwareengineers #careergrowthtips

Ever heard of the T Shape Engineer model? 🤔 "Have broad knowledge outside the core area, and deep knowledge of the functional area" I am now trying to become a T-shaped engineer, with broad knowledge of frontend and a deep understanding of backend, architecture, and system design! This versatility makes T Shape Engineers highly effective in diverse tech environments. Are you ready to shape up? #rehansattar #softwareengineering #backend

🌐 All About System Engineering 🌐 🔍 Systems Engineering (Broadest Category)   - Systems Integration Engineer   - Solution Architect   - Embedded Systems Engineer   - Hardware-Software Engineer   - IT Systems Engineer 🔎 Key Takeaways: 🔅 Systems Engineering encompasses a broad range of roles focused on integrating and managing both hardware and software components. 🔅 Systems Integration Engineer handle integration at different levels, ensuring components and subsystems work together seamlessly. 🔅 Solution Architect designs overarching solutions and often works with both Systems Integration Engineers and Hardware-Software Engineers. 🔅 Embedded Systems Engineer and Hardware-Software Engineer focus on hardware-software integration, each in specific contexts. 🔅 IT Systems Engineer manages IT infrastructure while also intersecting with systems integration tasks. Understanding these roles and their interconnections can provide valuable insights into how complex systems are designed and managed. Feel free to share your thoughts or experiences related to these roles! 💬👇 🔅 Thankyou and Keep Growing! #SystemsEngineering #EngineeringRoles #TechCareers #Integration #SolutionArchitecture #outofbox

Some low-level design patterns for senior engineers: 1. Read your writes: https://lnkd.in/dJYZ3Z_7 2. Asynchronous Processing with Futures: https://lnkd.in/d55-j-G8 3. Request Collapsing: https://lnkd.in/dFbJmwJC 4. What are threads: https://lnkd.in/dF4q9ez2 5. Ordering requests with threads: https://lnkd.in/dV_fqwW8 6. Event Bus Publishers and Subscribers: https://lnkd.in/dcciJ4vM 7. What is a software client library: https://lnkd.in/dbYzNXeH 8. Classes and package structuring: https://lnkd.in/dqagPDG9 9. Dependency Inversion: https://lnkd.in/djU2uw4K 10. What is backpressure: https://lnkd.in/dksjQb7N If you work as a software engineer, you are probably using a few of these patterns already :D Cheers! #SoftwareEngineering #LowLevelDesign #DesignPatterns

Some low-level design patterns for senior engineers: 1. Read your writes: https://lnkd.in/dJYZ3Z_7 2. Asynchronous Processing with Futures: https://lnkd.in/d55-j-G8 3. Request Collapsing: https://lnkd.in/dFbJmwJC 4. What are threads: https://lnkd.in/dF4q9ez2 5. Ordering requests with threads: https://lnkd.in/dV_fqwW8 6. Event Bus Publishers and Subscribers: https://lnkd.in/dcciJ4vM 7. What is a software client library: https://lnkd.in/dbYzNXeH 8. Classes and package structuring: https://lnkd.in/dqagPDG9 9. Dependency Inversion: https://lnkd.in/djU2uw4K 10. What is backpressure: https://lnkd.in/dksjQb7N If you work as a software engineer, you are probably using a few of these patterns already :D Cheers! #SoftwareEngineering #LowLevelDesign #DesignPatterns

Importance of #Architect : One of the often overlooked roles in Electronics is that of a Hardware Architect. While Hardware Engineers and Design Engineers are widely recognized, the Hardware Architect plays a crucial role in shaping the future of products and their functionalities. A good Hardware Architect should possess Product Architect skills as well. These valuable skills are becoming increasingly rare, especially in the Electronics domain. #Product #Electronics #Embedded