AppDynamics Software Developer In Test interview questions
based on 3 ratings - Updated Dec 30, 2021
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
100%
Employee Referral
Employee Referral
Interview search
3 interviews
AppDynamics interviews FAQs
Software Developer In Test applicants have rated the interview process at AppDynamics with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 57.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer In Test roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at AppDynamics overall takes an average of 24 days.
Common stages of the interview process at AppDynamics as a Software Developer In Test according to 1 Glassdoor interviews include:
Phone interview: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
It was a good and comprehensive interview process. And it was in campus placements and it was 4 rounds and 2 technical rounds 1 hiring manager round and 1 HR round.
Good interview process, interviewers are really helpful and medium to hard difficulty questions based on DSA and computer science concepts.
The interview was conducted on WebEx. Questions were on arrays, matrix, and sliding windows.
I applied through an employee referral. The process took 2 weeks. I interviewed at AppDynamics (San Francisco, CA) in Oct 2013
Interview
Had an initial conversation with the recruiter who gave an overview about the team and work. Had 2 phone interviews, one with a developer and another with the team manager. The first one involved shared screen coding -
Given an array of numbers and a target number, return true if the target number can be formed by adding 2 numbers in the array, else false. Write test cases for the same.
The next interview involved talking to manager about the team and some basic questions on java. What are access modifiers in java and static usage in java etc. Was also asked about factory and builder design pattern. After these interviews I was called onsite for a final round of onsite interview.
Onsite interview was with 5 different people, 2 developers, 1 manager and 2 test engineers.
Sample questions -
1. Write a linked list class in java and provide an init method which takes a count and returns a list having count elements, with head starting from count and tail having count.
2. What is singleton pattern and what is double locked checking? Why is it needed? Write code for singleton pattern
3. What is synchronization in java? What is volatile in java?
4. Write code to find the Nth to last element in a linked list. What are the test cases for the same?
5. What's the difference between abstract class and interface? Can an abstract method be declared static? If so, why? If not, why?
Most other questions were based on core java like garbage collection, primitive type and objects. Was also asked about inheritance in java and javascript.
Interview questions [1]
Question 1
You are given a list of call stacks, which represents the call stack at a particular instance of time starting from 0 ms, say at every ms. You need to create a call graph from this data, which is a hierarchical structure and also provide the time in ms, that each call in the hierarchy took.
After I struggled a bit, the question was further simplified where I had to find the number of times a particular method is called and also provide a parent-child hierarchy between the calls.
So basically, the input was a list of stacks and the output was a tree graph with count of each method.