shiv_emf said:Job satisfaction is another issue... but thing is scope shud be gud rite!!
as of now BE ppl r getting highly paid but thry hav lots of work load...
with little exp .. thry r earning fat amount
Shiv
littlebu said:I am a fresh FE designer, some times i am confused: all time i am doing dynamic verification , like simulation, EC check, not RTL Coding. This job more like a verification Enginner.
littlebu said:I am a fresh FE designer, some times i am confused: all time i am doing dynamic verification , like simulation, EC check, not RTL Coding. This job more like a verification Enginner.
omara007 said:littlebu said:I am a fresh FE designer, some times i am confused: all time i am doing dynamic verification , like simulation, EC check, not RTL Coding. This job more like a verification Enginner.
Verification Engineer is not a bad job .. sometimes it's more important than design job .. yet, when we were students we got more design dosage than verification dosage .. and we learnt that designer is intellictual and whom is verifying his designs is less intellictual ..
In the industry world, RTL design needs skills but not smartness .. the one who puts the system specs, functional specs, and chip architecture might need to be more intellictual .. but this comes from experience and higher-level academia ..
Anyhow .. u need to have some RTL skills in order not to mess up with your verification ..
shiv_emf said:After 5years or so ...tools will be automated n there will nt be any Backend design ...
is this statement true??
thanks for giving facts !!kpsai26779 said:Hi folks,
FE Vs BE really its very interesting topic of discussion. Every field has its own importance in every aspect.
Here I will take example of power saving
By designing good RTL design we can save 60-70%,
But by doing good back end design (PR, Ckt & Layout) we can save only 10-20% of power which makes design to survive.
in figures we interpret FE is important but BE makes design to survive.
shiv_emf said:After 5years or so ...tools will be automated n there will nt be any Backend design ...
is this statement true??
avimit said:1. To be honest: BE engineer is a tool engineer: his job is to run a tool where as FE engineer is a design engineer, he is responsible for wot the chip actually does.
2. 10years BE exp person: wot he knows is how to run tools.
10Years FE exp person: knows a lot about chip, hadfull of system specs, or may be some standard specs.
3. FE engg can switch to BE at any time where as BE from FE? the more experience you have of BE the more it is difficult to switch to FE. And if you have 10+ years of exp in BE, chances are : no FE for you my dear friend.
Kr,
Avi
really helpful reply .. thanks
one shud hav both FE n BE knowledge for better ASIC engineer
how far BE guy needs FE knowledge ? ... i think juzz data flow chart is enough for floorplanning
FE guys who r into rtl design ... do they need BE knowledge for better design
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?