⟩ Senior Software Engineer Integration Related Questions Part Three
► What Source Control systems have you worked with?
► What is Continuous Integration? Have you used it and why is it important?
► Describe a software development life cycle that you've managed.
► How do you react to people criticizing your code/documents?
► Whose blogs or podcasts do you follow? Do you blog or podcast?
► Tell me about some of your hobby projects that you've written in your off time.
► What is the last programming book you read?
► Describe, in as much detail as you think is relevant, as deeply as you can, what happens when I type "cnn.com" into a browser and press "Go".
► Describe the structure and contents of a design document, or a set of design documents, for a multi-tiered web application.
► What's so great about <cool web technology of the day>?
► How can you stop your DBA from making off with a list of your users' passwords?
► What do you do when you get stuck with a problem you can't solve?
► If your database was under a lot of strain, what are the first few things you might consider to speed it up?
► What is SQL injection?
► What's the difference between unit test and integration test?
► Tell me about 3 times you failed.
► What is Refactoring ? Have you used it and it is important? Name three common refactorings.
► You have two computers, and you want to get data from one to the other. How could you do it?
► Left to your own devices, what would you create?
► Given Time, Cost, Client satisfaction and Best Practices, how will you prioritize them for a project you are working on? Explain why.
► What's the difference between a web server, web farm and web garden? How would your web application need to change for each?
► What value do daily builds, automated testing, and peer reviews add to a project? What disadvantages are there?
► What elements of OO design are most prone to abuse? How would you mitigate that?
► When do you know your code is ready for production?
► What's YAGNI? Is this list of questions an example?
► Describe to me some bad code you've read or inherited lately.