Interview Questions
The following are a list of the potential question that will be asked during a given interview. Some of the questions are also expanded to included some focused questions that will be used should the broader question prove to be too high level. Commenting on any of this is very much encouraged. We are looking for better ways to surface quantitative data and to highlight known problem areas.
Feedback can be added here or emailed to mbest@mozilla.com.
Background
* What bugzilla components people feel responsible for?
Workflow
* How does Bugzilla fit into your teams workflow?
* submitting bugs?
* bug triage?
* what triage process (if any) for new bugs is being used?
* set priority?
* track status?
* requesting reviews or approvals?
* are tests part of r+'ing a patch?
* how do they manage their review queue?
* are there r+ w/nits, r+ nit self-fixers or r- until nits type people?
* approving bugs or reviews?
* How do you hand bugs off to someone else?
* How is bug ownership tracked?
* How do you decide what bug to work on next?
* What conditions must be met to change the status field of a bug?
* Unconfirmed to New
* New to Assgined
* Assgined to Resolved
* Resolved to Verified
* Other combinations
* What are the key issues that are adding friction to your workflow?
* Is there changes you would like to see that would make that work better?
* What is working well with regards to workflow?
* Do you use other tools to track bugs and tasks?
* How is QA involved in your development process?
Bug Fields
* How does your team use priority?
* Do you consider it a key part of how you order tasks?
* How does your team use whiteboards?
* Do you feel it's important to your process?
* How does your team use Keywords?
* Do you feel it's important to your process?
* Are there areas of the bug form that you feel are redundant or particularly useful that haven't been mentioned?
Effectiveness
* How rapid is response to someone within your team,
* On a scale of 1 to 10, how confident are you that filing a bug will get you the result you need to complete your work quickly?
* How rapid is response to filing a bug to someone outside your team,
* On a scale of 1 to 10, how confident are you that filing a bug will get you the result you need to complete your work quickly?
* How efficient is the review process,
* On a scale of 1 to 10, how fast do you feel that these will be turned around?
* How efficient is the approval process,
* On a scale of 1 to 10, how fast do you feel that these will be turned around?
* How aware are you of important orphaned bugs that related to your team,
* On a scale of 1 to 10, how confident are you that your group knows about every bug that is important?
Discovery
* Does Bugzilla give you the information you need it to?
* How would you improve it to give you better insight?
* Is there a hack or report you have found particularly useful?
* Is there a key feature that you would like to see added?
* What are your key complaints about Bugzilla?
Feature Pages (if time allows)
* Do you use the feature pages?
* What do you find most useful about the feature pages?
* What simple changes could be made to the feature pages to make them more useful for you?
* What do you find most frustrating about the feature pages?
* What would you change to fix that or make them less frustrating?
* How often do you read (not change, just read) feature pages? several times/day? daily? several times/wk? weekly? less often? never?
* How often do you edit feature pages? several times/day? daily? several times/wk? weekly? less often? never?
* When you edit a feature page, what are you usually doing? Changing status, adding content, modifying content...?
* Have feature pages made your job easier or more efficient? If so, how?
* Have feature pages been a detriment to your work? If so, how?
Interview List
Module Owners
* Gavin Sharp
* Dave Townsend
* Ben Smedberg
* Ted Mielczarek
* Neil Deakin
* Rob Strong
* Justin Dolske
* Shawn Wilsher (no longer an employee)
* Mark Finkle
* Dão Gottwald
* Doug Turner
* David Bolter
* Nick Thomas
* Boris Zbarsky
* Johnny Stenback
* Jeff Muizelaar
* Blake Kaplan
* Marco Pesenti Gritti
* Henri Sivonen
* Simon Montagu
* Chris Jones
* Dan Witte (no longer an employee)
* Robert O'Callahan
* Taras Glek
* Mark Finkle
* Matt Brubeck
* Alon Zakai
* Gervase Markham
* Johnathan Nightingale
* Aakash Desai
* Byron Jones (bugzilla)
* Dave Lawrence (bugzilla)
Write-in Candidates
* Axel Hecht (l10n)
* Scoobidiver/Alice0755/Ria Klassen (community quality guardians)
* Juan Becerra (QA)
* Stephen Donner (QA)
* Rob Campbell (DevTools module owner)
* timeless
* Robert Kaiser (long time community person)
* Italian localizer
Short List
Do not alter unless you are in the advisory group
* Justin Dolske
* Third email sent
* Interviewed Canceled.
Completed Interviews
* Joe Drew (MoCo)
* Christian Legnitto (MoCo)
* Brad Lassey (MoCo)
* David Baron (MoCo)
* Jesse Ruderman (MoCo)
* Ehsan Akhgari (MoCo)
* Dave Mandelin (MoCo)
* Matthew Brubeck (MoCo)
* Tyler Downer (Community)
* Kevin Brosnan (MoCo & Community)
* Christopher Blizzard (MoCo)
* Asa Dotzler (MoCo)
* Gavin Sharp (MoCo)
* David Mason (MoCo - GitHub)
* Brian Warner (MoCo - GitHub)
* Boris Zbarsky (MoCo)
* Ed Morley (Community Email: bmo@edmorley.co.uk)
* Juan Becerra (MoCo)
* Axel Hacht (MoCo)
* Scoobidiver (Community Email: scoobidiver@netcourrier.com)
* Chris Atlee (MoCo)
* Romaxa (Community Email: romaxa@gmail.com)