Programme Analyst applicants have rated the interview process at UC San Diego with 3.5 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 76.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Programme Analyst roles take an average of 1 day to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at UC San Diego overall takes an average of 25 days.
Common stages of the interview process at UC San Diego as a Programme Analyst according to 2 Glassdoor interviews include:
One on one interview: 33%
Drug test: 17%
Presentation: 17%
Group panel interview: 17%
Phone interview: 17%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at UC San Diego (San Diego, CA) in Mar 2016
Interview
1 round of technical interview with questions regarding spring, java, databases,agile process
second round of interview with the director for oveview of job. i was then offered the job within a week of the interview
I applied online. The process took 1 day. I interviewed at UC San Diego in Jun 2010
Interview
I received an email which requested availability for a phone interview. Once the hiring manager and I established a time for the phone consultation, we talked by phone. During the phone interview, I was asked general questions about my resume, skills, and current job. I was given an overview of the position and the team with which I'd be working. After passing that portion, I had a face-to-face interview with a small panel of co-workers. I was asked technical questions and analytical questions. Some scenario-style questions, a couple of hypotheticals. I was asked preference questions about programming language and work station. I was asked system-level troubleshooting questions.
Interview questions [1]
Question 1
You have a caching name server, a database server, two web application servers. The first two are physical and the last two are virtual. All three are critical and can have minimal downtime. What is your strategy to configure, backup, and monitor them.