Mixing
How to reply to “Tell me about your last project?†in an interview
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
28
down vote
favorite
I am a software engineer, I get confused what to answer, where to start, when I am asked this question: "Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest or very desperate to finish quickly just wants me to jump straight to my module.
Listening 2-3 sentences they guess and ask me 2-3 direct technical questions before wrapping up. I find it difficult to answer these questions as, they had not allowed me to fully explain the modules. So I feel they might assume me as a person who has insufficient knowledge about the project or my module.
What's the best way to explain a big project within few minutes. And how would I know what they are looking for? ( Should I just limit my explanation limited to their requirement?)
interviewing software-industry
edited May 28 '13 at 21:32
Kazark
405716
asked May 28 '13 at 15:43
chello
142126
add a comment |Â
up vote
28
down vote
favorite
I am a software engineer, I get confused what to answer, where to start, when I am asked this question: "Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest or very desperate to finish quickly just wants me to jump straight to my module.
Listening 2-3 sentences they guess and ask me 2-3 direct technical questions before wrapping up. I find it difficult to answer these questions as, they had not allowed me to fully explain the modules. So I feel they might assume me as a person who has insufficient knowledge about the project or my module.
What's the best way to explain a big project within few minutes. And how would I know what they are looking for? ( Should I just limit my explanation limited to their requirement?)
interviewing software-industry
edited May 28 '13 at 21:32
Kazark
405716
asked May 28 '13 at 15:43
chello
142126
Start with a more basic answer and let them ask for more details if they want them.
– jmorc
May 28 '13 at 15:50
5
Are you selling your project or yourself? If you are selling your project, it might make sense to introduce all the modules. If you are selling yourself, it probably makes sense to jump straight into your module.
– emory
May 28 '13 at 22:47
add a comment |Â
up vote
28
down vote
favorite
up vote
28
down vote
favorite
I am a software engineer, I get confused what to answer, where to start, when I am asked this question: "Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest or very desperate to finish quickly just wants me to jump straight to my module.
Listening 2-3 sentences they guess and ask me 2-3 direct technical questions before wrapping up. I find it difficult to answer these questions as, they had not allowed me to fully explain the modules. So I feel they might assume me as a person who has insufficient knowledge about the project or my module.
What's the best way to explain a big project within few minutes. And how would I know what they are looking for? ( Should I just limit my explanation limited to their requirement?)
interviewing software-industry
edited May 28 '13 at 21:32
Kazark
405716
asked May 28 '13 at 15:43
chello
142126
I am a software engineer, I get confused what to answer, where to start, when I am asked this question: "Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest or very desperate to finish quickly just wants me to jump straight to my module.
Listening 2-3 sentences they guess and ask me 2-3 direct technical questions before wrapping up. I find it difficult to answer these questions as, they had not allowed me to fully explain the modules. So I feel they might assume me as a person who has insufficient knowledge about the project or my module.
What's the best way to explain a big project within few minutes. And how would I know what they are looking for? ( Should I just limit my explanation limited to their requirement?)
interviewing software-industry
edited May 28 '13 at 21:32
Kazark
405716
asked May 28 '13 at 15:43
chello
142126
edited May 28 '13 at 21:32
Kazark
405716
edited May 28 '13 at 21:32
Kazark
405716
edited May 28 '13 at 21:32
Kazark
405716
405716
asked May 28 '13 at 15:43
chello
142126
asked May 28 '13 at 15:43
chello
142126
asked May 28 '13 at 15:43
chello
142126
142126
Start with a more basic answer and let them ask for more details if they want them.
– jmorc
May 28 '13 at 15:50
5
Are you selling your project or yourself? If you are selling your project, it might make sense to introduce all the modules. If you are selling yourself, it probably makes sense to jump straight into your module.
– emory
May 28 '13 at 22:47
add a comment |Â
Start with a more basic answer and let them ask for more details if they want them.
– jmorc
May 28 '13 at 15:50
5
Are you selling your project or yourself? If you are selling your project, it might make sense to introduce all the modules. If you are selling yourself, it probably makes sense to jump straight into your module.
– emory
May 28 '13 at 22:47
Start with a more basic answer and let them ask for more details if they want them.
– jmorc
May 28 '13 at 15:50
Start with a more basic answer and let them ask for more details if they want them.
– jmorc
May 28 '13 at 15:50
5
5
Are you selling your project or yourself? If you are selling your project, it might make sense to introduce all the modules. If you are selling yourself, it probably makes sense to jump straight into your module.
– emory
May 28 '13 at 22:47
Are you selling your project or yourself? If you are selling your project, it might make sense to introduce all the modules. If you are selling yourself, it probably makes sense to jump straight into your module.
– emory
May 28 '13 at 22:47
add a comment |Â
4 Answers
4
active
oldest
votes
up vote
55
down vote
accepted
Yes, you should just limit your explanation to their requirement. As an interviewer, I am asking this question not to get the full picture of the project, but simply to understand enough to ask you follow-up questions. That's the real point of this question: to see whether you can explain the "why did you do x instead of y?". It's in those follow-up questions that you get to show that you really understood the full project. If you try to show all your understanding up-front, you will get bored looks, as you have already encountered. Also, explaining it up-front only shows that you've been able to memorize a script, not that you really understood the project.
Be especially careful of this with phone interviews, as you will not be able to read their body language. I've performed lots of phone interviews where I asked a simple question and got a 5-minute monologue which I then had to try to interrupt tactfully. At a bare minimum, you should pause at spots and ask something like "would you like to hear more detail on that, or does that give you the basics of what you wanted to know?"
answered May 28 '13 at 15:52
explunit
2,5471617
1
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
8
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
add a comment |Â
up vote
7
down vote
Keep it short and sweet by trying to stick to the following points:
Planning implementation and achieving results
Describe the project, activity or event which you have worked on and taken through to a conclusion. Include your objective, what you did, any changes you made or assisted in implementing plans and state how you measured your success.
Influencing, communication and teamwork
Describe how you have achieved a goal through influencing the actions and opinions of others (perhaps in a team context). What were the circumstances? What did you do to make a difference? How do you know the result was satisfactory?
Analysis, problem solving and creative thinking
Describe a difficult problem that you have solved during this project. State how you decided which the critical issues were. Say what you did and what your solution was. What other approaches could you have taken?
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
add a comment |Â
up vote
3
down vote
"Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest [...].
Try this:
Short sentence on what problem your last project was solving
If the architecture (or anything else) gave you bigger responsibilities or challenges that you overcame, mention them briefly here. As an interviewer, I wouldn't care that your project had six modules or what they were (I am not an interviewer).
Speak about your activity/responsibility in the last project.
E.g.: My last project was adding a reporting module for an in-house data management system. I was in charge of loading all the wibbles and generating wibble-reports from the non-expired ones, in real time.
answered May 29 '13 at 15:16
utnapistim
1,771914
add a comment |Â
up vote
-5
down vote
The best way would be to prepare a powerpoint slide (case study) with client background, about the project/ project focus, Problem description and solution, Business value (if needed), Key achievements in this order. Remember all headings can have 3 to 5 bullet points or a 4 or 5 line para. The entire slide fills up and whatever question interviewer asks will fall into any one of the headings.
answered Oct 17 '14 at 15:03
shankarsiva
1
1
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
1
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
55
down vote
accepted
Yes, you should just limit your explanation to their requirement. As an interviewer, I am asking this question not to get the full picture of the project, but simply to understand enough to ask you follow-up questions. That's the real point of this question: to see whether you can explain the "why did you do x instead of y?". It's in those follow-up questions that you get to show that you really understood the full project. If you try to show all your understanding up-front, you will get bored looks, as you have already encountered. Also, explaining it up-front only shows that you've been able to memorize a script, not that you really understood the project.
Be especially careful of this with phone interviews, as you will not be able to read their body language. I've performed lots of phone interviews where I asked a simple question and got a 5-minute monologue which I then had to try to interrupt tactfully. At a bare minimum, you should pause at spots and ask something like "would you like to hear more detail on that, or does that give you the basics of what you wanted to know?"
answered May 28 '13 at 15:52
explunit
2,5471617
1
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
8
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
add a comment |Â
up vote
55
down vote
accepted
Yes, you should just limit your explanation to their requirement. As an interviewer, I am asking this question not to get the full picture of the project, but simply to understand enough to ask you follow-up questions. That's the real point of this question: to see whether you can explain the "why did you do x instead of y?". It's in those follow-up questions that you get to show that you really understood the full project. If you try to show all your understanding up-front, you will get bored looks, as you have already encountered. Also, explaining it up-front only shows that you've been able to memorize a script, not that you really understood the project.
Be especially careful of this with phone interviews, as you will not be able to read their body language. I've performed lots of phone interviews where I asked a simple question and got a 5-minute monologue which I then had to try to interrupt tactfully. At a bare minimum, you should pause at spots and ask something like "would you like to hear more detail on that, or does that give you the basics of what you wanted to know?"
answered May 28 '13 at 15:52
explunit
2,5471617
1
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
8
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
add a comment |Â
up vote
55
down vote
accepted
up vote
55
down vote
accepted
Yes, you should just limit your explanation to their requirement. As an interviewer, I am asking this question not to get the full picture of the project, but simply to understand enough to ask you follow-up questions. That's the real point of this question: to see whether you can explain the "why did you do x instead of y?". It's in those follow-up questions that you get to show that you really understood the full project. If you try to show all your understanding up-front, you will get bored looks, as you have already encountered. Also, explaining it up-front only shows that you've been able to memorize a script, not that you really understood the project.
Be especially careful of this with phone interviews, as you will not be able to read their body language. I've performed lots of phone interviews where I asked a simple question and got a 5-minute monologue which I then had to try to interrupt tactfully. At a bare minimum, you should pause at spots and ask something like "would you like to hear more detail on that, or does that give you the basics of what you wanted to know?"
answered May 28 '13 at 15:52
explunit
2,5471617
Yes, you should just limit your explanation to their requirement. As an interviewer, I am asking this question not to get the full picture of the project, but simply to understand enough to ask you follow-up questions. That's the real point of this question: to see whether you can explain the "why did you do x instead of y?". It's in those follow-up questions that you get to show that you really understood the full project. If you try to show all your understanding up-front, you will get bored looks, as you have already encountered. Also, explaining it up-front only shows that you've been able to memorize a script, not that you really understood the project.
Be especially careful of this with phone interviews, as you will not be able to read their body language. I've performed lots of phone interviews where I asked a simple question and got a 5-minute monologue which I then had to try to interrupt tactfully. At a bare minimum, you should pause at spots and ask something like "would you like to hear more detail on that, or does that give you the basics of what you wanted to know?"
answered May 28 '13 at 15:52
explunit
2,5471617
edited May 28 '13 at 15:59
answered May 28 '13 at 15:52
explunit
2,5471617
answered May 28 '13 at 15:52
explunit
2,5471617
answered May 28 '13 at 15:52
explunit
2,5471617
2,5471617
1
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
8
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
add a comment |Â
1
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
8
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
1
1
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
Welcome to The Workplace and nice answer!
– Elysian Fields♦
May 28 '13 at 22:32
8
8
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
"would you like to hear more detail on that, or does that give you the basics of what you wanted to know?" I have interviewed more people than I can count. I don't think I've ever heard one of them say anything like this, drop this line on me and you'll have my attention (in a good way) Not many people consider the fact sometimes you really only want or need the bird's eye view on something.
– RualStorge
Oct 17 '14 at 17:08
add a comment |Â
up vote
7
down vote
Keep it short and sweet by trying to stick to the following points:
Planning implementation and achieving results
Describe the project, activity or event which you have worked on and taken through to a conclusion. Include your objective, what you did, any changes you made or assisted in implementing plans and state how you measured your success.
Influencing, communication and teamwork
Describe how you have achieved a goal through influencing the actions and opinions of others (perhaps in a team context). What were the circumstances? What did you do to make a difference? How do you know the result was satisfactory?
Analysis, problem solving and creative thinking
Describe a difficult problem that you have solved during this project. State how you decided which the critical issues were. Say what you did and what your solution was. What other approaches could you have taken?
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
add a comment |Â
up vote
7
down vote
Keep it short and sweet by trying to stick to the following points:
Planning implementation and achieving results
Describe the project, activity or event which you have worked on and taken through to a conclusion. Include your objective, what you did, any changes you made or assisted in implementing plans and state how you measured your success.
Influencing, communication and teamwork
Describe how you have achieved a goal through influencing the actions and opinions of others (perhaps in a team context). What were the circumstances? What did you do to make a difference? How do you know the result was satisfactory?
Analysis, problem solving and creative thinking
Describe a difficult problem that you have solved during this project. State how you decided which the critical issues were. Say what you did and what your solution was. What other approaches could you have taken?
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
add a comment |Â
up vote
7
down vote
up vote
7
down vote
Keep it short and sweet by trying to stick to the following points:
Planning implementation and achieving results
Describe the project, activity or event which you have worked on and taken through to a conclusion. Include your objective, what you did, any changes you made or assisted in implementing plans and state how you measured your success.
Influencing, communication and teamwork
Describe how you have achieved a goal through influencing the actions and opinions of others (perhaps in a team context). What were the circumstances? What did you do to make a difference? How do you know the result was satisfactory?
Analysis, problem solving and creative thinking
Describe a difficult problem that you have solved during this project. State how you decided which the critical issues were. Say what you did and what your solution was. What other approaches could you have taken?
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
Keep it short and sweet by trying to stick to the following points:
Planning implementation and achieving results
Describe the project, activity or event which you have worked on and taken through to a conclusion. Include your objective, what you did, any changes you made or assisted in implementing plans and state how you measured your success.
Influencing, communication and teamwork
Describe how you have achieved a goal through influencing the actions and opinions of others (perhaps in a team context). What were the circumstances? What did you do to make a difference? How do you know the result was satisfactory?
Analysis, problem solving and creative thinking
Describe a difficult problem that you have solved during this project. State how you decided which the critical issues were. Say what you did and what your solution was. What other approaches could you have taken?
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
answered May 28 '13 at 16:03
Michael Grubey
4,20432252
4,20432252
add a comment |Â
add a comment |Â
up vote
3
down vote
"Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest [...].
Try this:
Short sentence on what problem your last project was solving
If the architecture (or anything else) gave you bigger responsibilities or challenges that you overcame, mention them briefly here. As an interviewer, I wouldn't care that your project had six modules or what they were (I am not an interviewer).
Speak about your activity/responsibility in the last project.
E.g.: My last project was adding a reporting module for an in-house data management system. I was in charge of loading all the wibbles and generating wibble-reports from the non-expired ones, in real time.
answered May 29 '13 at 15:16
utnapistim
1,771914
add a comment |Â
up vote
3
down vote
"Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest [...].
Try this:
Short sentence on what problem your last project was solving
If the architecture (or anything else) gave you bigger responsibilities or challenges that you overcame, mention them briefly here. As an interviewer, I wouldn't care that your project had six modules or what they were (I am not an interviewer).
Speak about your activity/responsibility in the last project.
E.g.: My last project was adding a reporting module for an in-house data management system. I was in charge of loading all the wibbles and generating wibble-reports from the non-expired ones, in real time.
answered May 29 '13 at 15:16
utnapistim
1,771914
add a comment |Â
up vote
3
down vote
up vote
3
down vote
"Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest [...].
Try this:
Short sentence on what problem your last project was solving
If the architecture (or anything else) gave you bigger responsibilities or challenges that you overcame, mention them briefly here. As an interviewer, I wouldn't care that your project had six modules or what they were (I am not an interviewer).
Speak about your activity/responsibility in the last project.
E.g.: My last project was adding a reporting module for an in-house data management system. I was in charge of loading all the wibbles and generating wibble-reports from the non-expired ones, in real time.
answered May 29 '13 at 15:16
utnapistim
1,771914
"Tell me about your last project?"
I usually start with the problem description, then stating the solution as the project. Project architecture, one line intro about all the modules. By this time the interviewer looses interest [...].
Try this:
Short sentence on what problem your last project was solving
If the architecture (or anything else) gave you bigger responsibilities or challenges that you overcame, mention them briefly here. As an interviewer, I wouldn't care that your project had six modules or what they were (I am not an interviewer).
Speak about your activity/responsibility in the last project.
E.g.: My last project was adding a reporting module for an in-house data management system. I was in charge of loading all the wibbles and generating wibble-reports from the non-expired ones, in real time.
answered May 29 '13 at 15:16
utnapistim
1,771914
answered May 29 '13 at 15:16
utnapistim
1,771914
answered May 29 '13 at 15:16
utnapistim
1,771914
answered May 29 '13 at 15:16
utnapistim
1,771914
1,771914
add a comment |Â
add a comment |Â
up vote
-5
down vote
The best way would be to prepare a powerpoint slide (case study) with client background, about the project/ project focus, Problem description and solution, Business value (if needed), Key achievements in this order. Remember all headings can have 3 to 5 bullet points or a 4 or 5 line para. The entire slide fills up and whatever question interviewer asks will fall into any one of the headings.
answered Oct 17 '14 at 15:03
shankarsiva
1
1
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
1
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
add a comment |Â
up vote
-5
down vote
The best way would be to prepare a powerpoint slide (case study) with client background, about the project/ project focus, Problem description and solution, Business value (if needed), Key achievements in this order. Remember all headings can have 3 to 5 bullet points or a 4 or 5 line para. The entire slide fills up and whatever question interviewer asks will fall into any one of the headings.
answered Oct 17 '14 at 15:03
shankarsiva
1
1
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
1
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
add a comment |Â
up vote
-5
down vote
up vote
-5
down vote
The best way would be to prepare a powerpoint slide (case study) with client background, about the project/ project focus, Problem description and solution, Business value (if needed), Key achievements in this order. Remember all headings can have 3 to 5 bullet points or a 4 or 5 line para. The entire slide fills up and whatever question interviewer asks will fall into any one of the headings.
answered Oct 17 '14 at 15:03
shankarsiva
1
The best way would be to prepare a powerpoint slide (case study) with client background, about the project/ project focus, Problem description and solution, Business value (if needed), Key achievements in this order. Remember all headings can have 3 to 5 bullet points or a 4 or 5 line para. The entire slide fills up and whatever question interviewer asks will fall into any one of the headings.
answered Oct 17 '14 at 15:03
shankarsiva
1
answered Oct 17 '14 at 15:03
shankarsiva
1
answered Oct 17 '14 at 15:03
shankarsiva
1
answered Oct 17 '14 at 15:03
shankarsiva
1
1
1
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
1
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
add a comment |Â
1
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
1
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
1
1
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
I don't think this is plausible if you're asked in the interview without prior notice...
– Telastyn
Oct 17 '14 at 15:23
1
1
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
this doesn't seem to add anything substantial over points made and explained in prior answers
– gnat
Oct 17 '14 at 15:28
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f12040%2fhow-to-reply-to-tell-me-about-your-last-project-in-an-interview%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Start with a more basic answer and let them ask for more details if they want them.
– jmorc
May 28 '13 at 15:50
5
Are you selling your project or yourself? If you are selling your project, it might make sense to introduce all the modules. If you are selling yourself, it probably makes sense to jump straight into your module.
– emory
May 28 '13 at 22:47