Hacker Newsnew | past | comments | ask | show | jobs | submit | _null_pointer_'s commentslogin

This is great. Thank you for the detailed answer.

I found two 6-course specializations on Coursera earlier, which one do you think would be a good starting point for me?

1 - https://www.coursera.org/specializations/robotics

2 - https://www.coursera.org/specializations/modernrobotics


I don't known them, but it looks like they both introduced the same concepts, so either of them is probably right.


Thank you! The role I am interviewing for is also responsible for system architecture and design, not at the code level but at the level of services and components, sort of a Technical Director who is at the same time the Chief Architect (small company). Do you see this working or do you think it's too much of a scope?


Go for it!

In any new position, you will have to learn and grow into it and if the jump is gradual, all the better. Assuming that you have the engineering domain covered, you may only lack experience on the management side which will have to be worked on but that will be easier since it is a small company and hence will not be onerous. You can also request help (i.e. informal mentoring from peers/seniors) and later on grow your team to delegate some burden off of you if needed. Necessary commitment and hard-work will take you up the career ladder.

Finally, don't sell yourself short while also not losing sight of your limitations. Focus and sell on your strengths while simultaneously working on improving your weaknesses i.e. stretch yourself and don't always stay within your "comfort zone". Have a clear view of Expectations vs. Responsibilities and you can takeup any challenge.

Good Luck!


Thank you very much for your help and support.

I have been developing software since 2008/2009 and have been a technical team leader for 4 years now. This is definitely a big jump up the career ladder where I will be responsible for three different engineering teams. Sounds exciting.


I think the position isn't then of a Director of Engineering. This seems to be more of a technical role. Lead Architect or something. Director of Engineering implies that you manage teams, not directly people/architecture/code.


Well, the role is titled as Technical Director of Data Engineering. The DoE will be responsible for 3 different engineering teams with a headcount of 5-7 full-timers each team. What makes you think that this is not a DoE role?

A bit about myself, I have a total of 11 years of developing software, out of which I have been technically leading a team of 5 full-time engineers for 4 years now.


You didn't leave that clear on your post.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: