?

Log in

Previous Entry | Next Entry

Juniper phone interview

I had an interview last Friday morning at 8am (!!) with the hiring manager for a JUNOS (Juniper OS) engineering group. He asked me a lot of questions about things that are on my resume describing things that I do while not being currently employed. (Recall that I was advised some time ago by a Cisco recruiter that I should not leave any gaps on my resume, or else no one would consider it, treating me as if I was trying to hide something.) So we talked about some of my recent activity with IETF WGs, such as getting RFC 796 moved to Historic status, because it references IPv4 networks (and addressing schemes) that are very out of date. He also asked me to explain how the Equinix MLPE route servers worked, and how my provisioning code produces their configuration files.

He then asked me a lot of questions about what type of work environment I was looking for. I told him about wanting to continue to be involved with the IETF community (if possible), being in the loop of (technological) progress, and having authority commensurate with responsibility. He seemed to pick up on the latter point, because he said he tries to run his group that way. However, he did warn me that there are times when people are expected to work as much as 80 hours per week, even handling customer issues directly. I said that wouldn't be a problem, since I've had to do that for most of my career anyway.

He then told me that he'd like me to come in for an in-person interview. He asked how much programming I had been doing during this period of unemployment, especially C programming. I said that I have written code in several languages, depending upon the project in question. He cautioned me that the interview would be very difficult, involving questions about data structures and algorithms in C, because the engineers on his team make the questions very difficult. He asked me how I felt about that, and I said that I would just do the best I can, and that everyone experiences the same feelings on these types of interviews.

So, we'll see. (Nothing has been scheduled yet because of the Memorial Day holiday weekend.) But one thing that is now very very clear to me is that there is no substitute for the type of interview practice I have been doing. The competition is too stiff, and the interviews themselves too challenging, not to spend time developing code, studying algorithms and data structures, getting involved with open-source projects and/or standards bodies, etc.