Getting an Interview
Getting an Interview
Interviews for Top Jobs at Rackspace
- Windows Systems Administrator II (22)
- Linux Systems Administrator (13)
- Linux Systems Administrator II (10)
- Software Developer (10)
- Network Security Administrative I (9)
- Linux Systems Administrator I (8)
- Business Development Consultant (6)
- Sales Representative (6)
- Support Specialist (5)
- Systems Administrator II (5)
- Windows Systems Administrator I (5)
- Software Developer II (4)
- Software Developer III (4)
- Account Manager (4)
- Senior Manager (3)
- Linux Administrator (3)
- Intern (3)
- Systems Engineer (3)
- Windows Systems Administrator III (3)
- Data Centre Operations Technician (3)
- Support Technician I (2)
- Account Management (2)
- Systems Administrator (2)
- Sales Engineer (2)
- Financial Analyst (2)
- Security Engineer (2)
- Windows Administrator (2)
- Manager (2)
- Devops Engineer (2)
- DCOPS (2)
Software Developer III Interview
It was not too difficult. Had to go through 3 interviews. First one involved delivery managers interview. Next involved talking to the team. Team was mostly focused on algorithms. It was not too difficult. Had to go through 3 interviews. First one involved delivery managers interview. Next invovled talking to the team. Team was mostly focused on algorithms.
- It was not too difficult. Had to go through 3 interviews. First one involved delivery managers interview. Next invovled talking to the team. Team was mostly focused on algorithms. Answer Question
Other Interview Reviews for Rackspace
Software Developer III InterviewDeclined OfferNegative ExperienceDifficult Interview
I applied through a recruiter. The process took a week – interviewed at Rackspace (San Antonio, TX) in September 2014.
Contact made through a recruiter. Phone interview went well, could tell the interviewer was not very experienced. Couple of questions were confusing because of terminology mix up. Went into the technical interview, which was a four hour process. Several technical interview questions that were from CS 101 classes, Binary trees, searches, Sorts, Data Structures etc. Second meeting was with managers. They mainly vented about frustration with corporate culture, little unprofessional, but what the heck. Second management meeting, they also vented frustrations about culture and inability for upper management to make decisions. By the third interview, I had decided that this was probably not a great fit for me. The fourth interview was technical and had nothing to do with any experience I had on my resume. Was asked if I knew how memory was mapped by the Java virtual machine. Pretty much looked the interviewer in the eye and said "Nope!". Decided I would not be giving up my day job to make a move to Rackspace. If you really want to work there, I suggest pulling out your Data Structures book and some go through some algorithm review. Best of luck.
- Java JVM memory mapping, (How is it done?) Answer Question
Reasons for Declining
The corporate culture is a little to chaotic. It felt a little to unstable.
Software Developer III InterviewAccepted OfferPositive ExperienceEasy Interview
I applied through a recruiter. The process took 5 days – interviewed at Rackspace (San Antonio, TX) in December 2013.
I had a very positive interview process but was involved with interviewing other candidates. Some of those interviews were not conducted in what I consider a pleasant manner. This could be because I had a huge portfolio and lots of code sample. We had a hard time finding good candidates.
- How would I convert an Array to an Object or vica-versa? 1 Answer
I was told I would have 10 days of vacation upon signing which was not the case. I was offered 10K less than market average and accepted because I was told historically the yearly bonus has been $20-$30K. This year it's $4K.
Software Developer III InterviewDeclined OfferPositive ExperienceEasy Interview
The process took 2 weeks – interviewed at Rackspace in May 2009.
Basic questions in phone interview. After that there were interviews with 2-3 developers. No hard questions, mostly behavioral ones. Technical questions were alarmingly trivia based (what does X mean in c#) which seems to imply they are looking for knowledge rather than ability to learn. Developers seemed friendly enough. Was given another test to do over a 48hr period. String focus on OOP and design and nearly none on algorithms.
Reasons for Declining
Interview wasn't hard enough