- Dec 29, 2000
- 954
- 0
- 0
Doh!
Interviewed for an entry-level test engineer position this past Monday. Thought it went pretty well, but I guess they didn't like me. I asked for some constructive criticism, and the hiring manager mentioned that I didn't know anything about TCP/IP (on my resume, I noted that I implemented a light TCP/IP stack for an embedded system).
He told me that I should "be careful" of doing that on my resume. The issue is that they didn't ask me questions about TCP/IP, just very light layer 2 switches, some ARP, trunking, and spanning tree. I really do know some stuff about TCP/IP, otherwise I wouldn't have been able to code TCP/IP for my embedded system project... I'm not hurt about them not hiring me, but is it typical for employers to not remember what they asked you and to give you a baseless/ambiguous reason for not hiring you?
Interviewed for an entry-level test engineer position this past Monday. Thought it went pretty well, but I guess they didn't like me. I asked for some constructive criticism, and the hiring manager mentioned that I didn't know anything about TCP/IP (on my resume, I noted that I implemented a light TCP/IP stack for an embedded system).
He told me that I should "be careful" of doing that on my resume. The issue is that they didn't ask me questions about TCP/IP, just very light layer 2 switches, some ARP, trunking, and spanning tree. I really do know some stuff about TCP/IP, otherwise I wouldn't have been able to code TCP/IP for my embedded system project... I'm not hurt about them not hiring me, but is it typical for employers to not remember what they asked you and to give you a baseless/ambiguous reason for not hiring you?
