Getting an Interview
Getting an Interview
Interviews for Top Jobs at Perceptive Software
- Software Engineer (7)
- Consultant (7)
- Software Developer (4)
- Product Support Engineer (4)
- Project Manager (4)
- Sales (2)
- Software Consultant (2)
- Intern (2)
- Product Manager (2)
- BDM (1)
- Systems Administrator (1)
- Manager - Professional Services (1)
- Business Development Position (1)
- Proposal Production Specialist (1)
- Program Readiness Professional (1)
- Consultant Internship (1)
- Solution Development Engineer (1)
- App Systems Analyst (1)
- Product Management (1)
- Marketing (1)
- Technical Consultant (1)
- Technical Support Analyst (1)
- Anonymous (1)
- Sales Director (1)
- Sales Engineer (1)
- Inside Sales Representative (1)
- Contract Manager (1)
- Knowledge Engineer (1)
- Software Implementation Consultant (1)
- Designer (1)
- No OfferNeutral ExperienceAverage Interview
I applied online. I interviewed at Perceptive Software in December 2014.
Interview process was pretty quick once I submitted resume online, about a day to get back with me and scheduled a technical skills test for the following week. Looked like a beautiful, newly built campus, everyone I encountered was very pleasant and professional. It was a pleasant experience. Too bad my technical skills were so rusty on Unix commands and sql queries, looked like it would be a great place to work.
- Just took a technical test, which I totally fumbled through, all hand written in pencil. I don't test well and was a nervous wreck. 1 Answer
- No OfferNegative ExperienceDifficult Interview
I applied through an employee referral. The process took 3 weeks. I interviewed at Perceptive Software.
Applied online for another position and was contacted by a recruiter a week later asking if I was interested in this position. I interviewed with three older men. I had to write an "article" on how to make a peanut butter and jelly sandwich. They did not react positively to any question I answered.
- What is your favorite software? Answer Question
- No Offer
Without meeting, I was asked to take a programming assessment. The assessment was essentially to write a queue using linked lists in C++, Java or C#. I only interacted with an HR representative who provided me we pencil and paper... eventually someone realized it should be typed out - took about 35 minutes to write the whole thing in Notepad++ then left. Waited 2 weeks to get an email saying they would not proceed with me and that "this is in no way a reflection of your abilities but more a better career fit with other candidates".
- Only the programming assessment, wasn't given the time of day for an interview or even phone interview. Answer Question
- No OfferNeutral ExperienceEasy Interview
I applied online. The process took a week. I interviewed at Perceptive Software (Shawnee, KS) in June 2013.
On-site technical assessment.
- Nothing difficult. create your own Queue class and document class. You have to use word pad an the clock on the laptop I used was 20 minutes fast. Answer Question
- No OfferNeutral ExperienceAverage Interview
I applied through a recruiter. The process took 2+ months. I interviewed at Perceptive Software.
Fairly straightforward interview process, if a little drawn out. Found out about the job through a head hunter, followed by a phone screen with the HR Recruiter, then a short phone interview the hiring manager, and ending with an in-person interview with a number of internal stakeholders. Questions were very straight forward and interviewers were all nice. The entire process took nearly 2 months. I was disappointed that I didn't receive an offer, and asked the HR person for some feedback, but didn't receive a response.
- Nothing too tricky or difficult if you come prepared. Answer Question
- No OfferPositive ExperienceAverage Interview
I applied online. The process took 3 weeks. I interviewed at Perceptive Software (Shawnee, KS) in April 2013.
Applied through an online job board. I was contacted by an HR representative via email asking about salary expectations. After that I was invited on campus for an interview. Interview was in two parts. The first part was a practical skills test (Basic scripting stuff, use a scripting language to perform various operations on a string, attempt to debug a chunk of code that isn't working using excerpts from an error log). The first part took about an hour. The second part was an in person interview with the Team Lead from the team you'd be working with as well as a couple of project managers. Lots of basic interview questions: Favorite class? Least favorite class? Favorite thing about software engineering? Have you ever been in [insert unfortunate situation here], and how did you deal with it? This also lasted about an hour.
- I can't remember the specifics of the practical test, because it has been awhile, but I think it was something along the lines of: "Cut the sub-string 'Mr.' our of the string "Mr. Jones". Answer Question
- No OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took 3 weeks. I interviewed at Perceptive Software (Shawnee, KS) in March 2013.
I applied for the job because I have a reference who already works for the company. The online application process is straight forward; in fact, it's one of the easier online applications I've used. Called their HR department a week after my submission to follow up; the HR recruiter told me that she had actually been meaning to call me and was glad that I called her. We set up a phone interview screen for a time the next week. She called me exactly at the time she said she would. Was a nice 45 minute conversation about my experience and why I wanted to work for Perceptive. We hit a snag in the conversation when I figured out that she had the wrong version of my resume (I applied for a different job in 2012 and used a different version of my resume), but the conversation was fine after that. She asked me to e-mail her my current resume, which was already in their system, so that she could send it to the hiring manager. I got an e-mail about a week after the phone screen from a different recruiter to set up an in-person panel interview. The interview lasted for a little over an hour and I met the hiring manager, the team's assistant, two of the other contract managers, and the company's general counsel who joined us over the phone. There were no off the wall or "clever" questions that seem to be popular these days. All of the questions were very much in the vein of: - Tell me two things you like and don't like about your current job. - Tell me about the culture at your current company. - What kind of contract experience do you have? - What kinds of contracts do you work with? - What do you do outside of work? What are your hobbies? The only weird question they asked was "give us the answer a question that we didn't ask but you thought we would." I had about 15 minutes worth of questions at the end of the interview. On my way out the hiring manager told me that I would be contacted either way and that it would be in the next couple of days. I waited a week and never heard back from anyone, so I sent an e-mail to my recruiter who never responded. Two weeks later the job was removed from the careers website and I still hadn't heard a peep from anyone at Perceptive. In fact, it wasn't until two and a half weeks after I interviewed that I got a rejection e-mail from my recruiter. I thought Perceptive would be a little more prompt in its communications with interview candidates, especially candidates who were referred by a current employee. I never expected special treatment, but when the team is only interviewing 4 or 5 candidates, I expected better communication between the hiring manager, human resources, and myself.
- Answer the question we didn't ask but you thought we would. Answer Question
Helpful (1)No OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 7 weeks. I interviewed at Perceptive Software (Shawnee, KS) in September 2012.
Was introduced to the job through a recruiter. Submitted resume and a written pre-screen, at which point I was invited in for a programming assessment. Programming assessment consisted of coding (in a word processor) in C++, Java, or C# some basic object-oriented things (subclassing, virtual methods) and writing a linked list implementation. I passed the programming assessment and was invited to an in-person interview. This consisted of two hour-long sessions with two interviewers each. The interviewers were software developers/architects. There were no "soft" questions (e.g. "What is your greatest weakness?") nor random puzzle questions. All the discussion was focused on tangible things that I could bring to the company, my attitudes, and also a review of the code that I wrote in the assessment. It was a very pleasant interview with obviously very talented people. In the end, they deemed me a good candidate but still declined to give me an offer. My only criticism of the process was that it took quite a long time. After the assessment, there was a three-week wait until the interview, and after the interview there was a three-week wait before a final decision. So the entire process was several months long, and comments from my recruiter led me to believe they were unnecessarily dragging their feet.
- There weren't really any difficult questions, to be honest. Answer Question
Helpful (1)No OfferPositive ExperienceAverage Interview
The process took 2 weeks. I interviewed at Perceptive Software (Shawnee, KS) in July 2012.
Initially, I did a 40 minute phone interview with two people. Some of the topics discussed: How do you make a pure virtual function in C++. Explain abstract classes, inheritance, polymorphism in Java. Why do we need it? What's the benefit? Describe your favorite data structure. Whats your favorite programming book? What was the biggest problem you ever faced? Got a call back and was flown out to Kansas for a technical skills test and more face-to-face interviews. Had 90 minutes to solve a problem in any language. It's level of difficulty was at the level of a homework assignment in undergraduate course. After skills test, interviewed with two separate teams for an hour each. We went over my test and discussed typical behavioral questions and my background. Interview was very casual and free-flowing. Overall time it took was 3 hours 40 minutes that day.
- Create a linked list queue with push / pop functions for a document class. Answer Question
Helpful (2)No OfferNegative ExperienceAverage Interview
I applied through a recruiter. The process took 2 weeks. I interviewed at Perceptive Software (Shawnee, KS) in June 2012.
After a 20 minute informal phone interview, I was invited to fly to their office in Shawnee for a Programming test and an interview with project managers. I never met with an HR representive during the entire process, and was 'greeted' at the main desk by a disinterested receptionist. After about a 20 minute wait, she sent me to what was nothing more than a closet with a glass viewing window and a desk. As soon as I sat to take the test, they lost power and had to take the first 15 minutes of the test in the dark. At least she supplied a bottle of water - a good thing since there was almost no air movement in there, and it got quite warm. The test was as a previous poster described - create a linked list utilizing a document class with a pure virtual function that has Push and Pop methods for the last item in the list. This was all hand written. The test took about 45 minutes to get all written out, by which time I was rushing to just get out of the closet and get cooled off. Upon completion, I returned the test to the receptionist who said I could leave. I had to remind her I was there for interviews and she instructed me to sit and wait. After about a 30 minute wait, one of the project managers came out to great me and we headed to a conference room in the basement. It appears most if not all of the developers are kept in the unfinished basement in bullpen settings. They adhere tightly to the SCRUM philosophy - odd for a company with only one product. The interview was split into 2 groups - the first group consisting of 3 project managers. The were all quite cordial and friendly, and I felt we had a very good conversation. There were few technical questions asked - primarily it was a discussion of what the company does (only one product, with each project manager overseeing their chunk of that product). We discussed what they were lacking in their development - good testing methodologies, abysmal mobile development (I've been doing mobile development since Pocket PCs were first introduced, and testing sounded interesting, so I thought this position was going to be a very good fit). This lasted about an hour before the next group of managers arrived. The second group of managers were quite a bit less cordial and considerably less friendly. One acted as a mediator of the interview, a second had little if anything to ask or comment on, while the last 3 were the antagonists of group. First they nitpicked my programming test - I chose to use stdio and string (what I have used for 20 years of coding in C/C++) but they obviously wanted std:string to be used. They also admonished me for not using const when returning a pointer to the string name of the document. There were a couple of other minor quibbles they had, that would have been quickly caught had the code actually been done on a computer and compiled. It is ridiculous to think that hand writing code on paper won't have some syntactical issues. The were also unhappy that I didn't use a recursive routine to print out the nodes of the linked list - I chose to use a simple do/while loop. Then came the usual inane interview questions - what is your favorite data structure? Who is your favorite author? What is a design pattern? Well, to me, data structures are tools to get the job done - I have no favorite, just like I don't have a favorite wrench size. I don't read much anymore because books are overpriced and offer much less value than what can be found on the net. And a design pattern is really nothing more than what us old timers called algorithms. Very little was discussed about my work history. They said they ignored everything but the most current 10 years of work, which has been mostly in the entertainment industry, so they glossed over 20 years of development and management experience saying it was all too old to be considered. After an hour of badgering, the interview was over, I was escorted to the front door and left there. I've not had many interviews in my 30+ years of experience (only 5 counting this one), but this was by far the least professional of them all. Mind you, I've created over 30 commercial titles in my career, as well as designed hardware and software for high energy physics research and worked in several other industries such as medical, telecommunication, telemarketing, weather monitoring and forecasting, and entertainment for quite prominent companies. Yet, I was rejected by Perceptive as not having technical depth. As it turns out, they have interviewed over 45 candidates for this position (actually it is for 5 developer positions) and have rejected all of them. I'm not sure what their issue is - are they looking for perfection, or yes men, or do they simply have a fear that someone will come in and take their jobs.
- What is your favorite data structure? 1 Answer
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review