Getting an Interview
Getting an Interview
Interviews for Top Jobs at Sybase
- Software Engineer (6)
- Senior Software Engineer (2)
- Sales Executive (2)
- Software Developer (1)
- Software Developer Coop (1)
- Staff Software Engineer II (1)
- Human Resources (1)
- QA Intern (1)
- Practice Manager (1)
- Sales Operations Analyst (1)
- Engineering (1)
- Support Engineer (1)
- Quality Assurance Co-op (1)
- Software Developer, Co-Op (1)
- Technical Support Analyst (1)
- Senior Engineering Manager (1)
- Senior Systems Consultant (1)
1 person found this helpful
Software Developer Interview
I applied through an employee referral. The process took a day – interviewed at Sybase in April 2009.
There were 2 rounds here: technical and HR.
Interviewers were friendly and interested even after interviewing many candidates. In the beginning they asked questions about previous experience and it was less Q&A but more like a discussion. Then they proceeded to technical questions. Initially they asked questions related to algorithms and operating systems. Operating systems questions did center around mostly theoretical questions on cache, memory, virtual memory. There were also questions related to linux shell commands. After this the questions switched to database related questions. They initially started with simple SQL commands and things like ACID property and RW locks. Then there were questions related to data warehousing and different types of schemas. Ultimately they talked about indexing and gave a question related to indexing a sample mock data. I solved the question on paper and they interested in seeing the approach. They were also helpful while question solving.
This was a standard HR interview which talked about location preferences and general questions outlining a group/team situation and how will you respond.
- Database indexing related questions are difficult so one should brush up on them.
There was nothing really unexpected but yes the HR did ask me this question, "How will you explain object oriented programming to a common man who does not understand programming at all?" Answer Question