System engineer or VHDL designer

[hhnn]

I'm about choosing what career path to embark on. Currently, the communication company is offering System engineer and VHDL designer. I need your expert advice on choosing which path.

For my understanding:
For system engineer, it deals with system level, works with many modules. Using a lot of C programming. Testing is also an important part to ensure the systems works after fab-out. May have to deal with firmware, driver.

For VHDL designer, as you know designing a particular module for long long time. when you switch to another company, that module may not be used anymore. So, start new things over again.

About me: I just graduated in IC design major in Singapore. However, knowledge in the university is more on basic and small circuit design. I'm not sure whether it's helpful when using VHDL because most of the time I know in my company the VHDL designer is doing the integration of IP block bought from somewhere else. I'm doing internship with the company in the system team. I feel it's ok, not so bad.

My knowledge on C programming and VHDL are just at beginning stage.

I really want to hear you thoughts on what to choose. what path has more prospect in the future ? Is reuse-ability of knowledge a factor to consider?

 

[hhnn]

Hello, anyone comments on this? Really appreciate your help

 

[vigneshwara_s]

Better Select the VHDL designer JOB Profile . There are N number of C programmers where as for VHDL programming Need is high and Programmers is low.

Even though your current job provider Outsource IP from others and allocate the VHDL programmers to integrate the Block, you can take separate interest in the IP core design and prove yourselves. Even you can switchover easily from current profile to any other company as a pure VHDL programmer.

Regards,
Vikeee ..

 

[hhnn]

Really appreciate your helpful answer Vikeee.

So you're saying that there are much less VHDL designer than C programmer. I think that is true also. It means that the employment chance for being a VHDL designer is higher than C programmer. I'm not being suspicious about your answer. But if you or anyone come across this kind of topic, please let me know to extend my horizon

The C programmer here implies the system/firmware engineer. Between system/firmware engineer and VHDL designer, which has brighter future say in the next 5-10 years?in asia? US? and Eu?

Greatly thanks

 

[verbatim]

If you become a really good VHDL engineer, you will be in big demand in US / EU over the next 5 years.
In ten years I predict, like assembly language (.ASM) the need for VHDL will drop, as software becomes more powerful and the firmware/software boundary blurs.
I think learning any specialist engineering skill like VHDL is a good thing before becoming a systems engineer, since a good systems engineer should understand how the specialist 'working level' or 'coal face' operates.
Consider also what kind of person you are - VHDL engineer may not need good social skills to work, but a systems engineer with poor skills in managing / interacting with relationships between people / groups may not be as successful as one who is good at this.
You are more likely to be successful at something you find interesting, challenging, motivating, ( some people are motivatied more by a challenging a problem, others are motivated by people - which are you? )

Good luck.