Mixing
Interview: asked to give an hour long presentation on architecture of previous project
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
4
down vote
favorite
During an interview for a potential new employer, I was asked for a second meeting. For this second meeting I'm expected to present in one hour the architecture and implementation of a random previous project I have worked on. A couple of developers and architects would be attending. This would be to judge my skills.
I'm having some doubts:
- Is this just a way to get free consulting? Red flag?
- Is this unethical in terms of confidentiality? How much info can you give in an interview setting? Red flag?
- Is the time investment preparing a presentation, slides... acceptable?
- Possible alternative: should I just make up an imaginary project?
interviewing inside-information
asked May 17 '16 at 20:33
Jeremy
2,329814
suggest improvements |Â
up vote
4
down vote
favorite
During an interview for a potential new employer, I was asked for a second meeting. For this second meeting I'm expected to present in one hour the architecture and implementation of a random previous project I have worked on. A couple of developers and architects would be attending. This would be to judge my skills.
I'm having some doubts:
- Is this just a way to get free consulting? Red flag?
- Is this unethical in terms of confidentiality? How much info can you give in an interview setting? Red flag?
- Is the time investment preparing a presentation, slides... acceptable?
- Possible alternative: should I just make up an imaginary project?
interviewing inside-information
asked May 17 '16 at 20:33
Jeremy
2,329814
1
A hour seems a bit much, but checking candidates understand the projects they've worked on and asking what they would have done differently is a good interviewing approach.
– Nathan Cooper
May 18 '16 at 4:18
suggest improvements |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
During an interview for a potential new employer, I was asked for a second meeting. For this second meeting I'm expected to present in one hour the architecture and implementation of a random previous project I have worked on. A couple of developers and architects would be attending. This would be to judge my skills.
I'm having some doubts:
- Is this just a way to get free consulting? Red flag?
- Is this unethical in terms of confidentiality? How much info can you give in an interview setting? Red flag?
- Is the time investment preparing a presentation, slides... acceptable?
- Possible alternative: should I just make up an imaginary project?
interviewing inside-information
asked May 17 '16 at 20:33
Jeremy
2,329814
During an interview for a potential new employer, I was asked for a second meeting. For this second meeting I'm expected to present in one hour the architecture and implementation of a random previous project I have worked on. A couple of developers and architects would be attending. This would be to judge my skills.
I'm having some doubts:
- Is this just a way to get free consulting? Red flag?
- Is this unethical in terms of confidentiality? How much info can you give in an interview setting? Red flag?
- Is the time investment preparing a presentation, slides... acceptable?
- Possible alternative: should I just make up an imaginary project?
interviewing inside-information
asked May 17 '16 at 20:33
Jeremy
2,329814
asked May 17 '16 at 20:33
Jeremy
2,329814
asked May 17 '16 at 20:33
Jeremy
2,329814
asked May 17 '16 at 20:33
Jeremy
2,329814
2,329814
1
A hour seems a bit much, but checking candidates understand the projects they've worked on and asking what they would have done differently is a good interviewing approach.
– Nathan Cooper
May 18 '16 at 4:18
suggest improvements |Â
1
A hour seems a bit much, but checking candidates understand the projects they've worked on and asking what they would have done differently is a good interviewing approach.
– Nathan Cooper
May 18 '16 at 4:18
1
1
A hour seems a bit much, but checking candidates understand the projects they've worked on and asking what they would have done differently is a good interviewing approach.
– Nathan Cooper
May 18 '16 at 4:18
A hour seems a bit much, but checking candidates understand the projects they've worked on and asking what they would have done differently is a good interviewing approach.
– Nathan Cooper
May 18 '16 at 4:18
suggest improvements |Â
3 Answers
3
active
oldest
votes
up vote
6
down vote
accepted
Do not make up an imaginary project. Period. You cannot possibly fake enough knowledge of a made-up project to answer the kind of questions you'll get and you won't have the time to make a reasonable facsimile.
Whether this is on the level depends and whether the request and the amount of work it will entail is reasonable depends on a number of factors that you don't mention. Based on the info you provide I'm inclined to consider this a legitimate request from the hiring company to get to know your style as they just asked you for any random project you worked on. It could be a hobby project or something from a past employer. As long as you sanitise the architecture, which is to say scrub all company-specific references or business logic, you won't give them any useful information from a previous employer. Since it can be on anything this isn't a request for you to do free work. The lack of restrictions also mean that you are free to avoid projects that might be covered by an NDA.
As for whether it's reasonable, I would probably balk at the kind of effort this would involve if this was a low-level programming gig. But if presentations or client contact are a significant part of the description this is entirely reasonable and I'd say it's a great way for them to filter out good candidates. Even if that's not the case, this kind of interview lets them select for a specific kind of candidate that matches their culture, which isn't a bad thing at all.
Finally, I can't tell from your post if this would be an hour-long presentation, but that seems a bit long for talking about a random project. I would sooner expect a twenty-minute presentation followed by Q&A. If you're unsure I'd ask clarification on that. In fact, it's entirely reasonable to ask for some more details on this and I highly encourage you to do so. You should ask the hiring manager about:
- the goal of the presentation: they can answer your question better than this site could
- timeline: how much content should you give
- focus: architecture? languages? interface points? documentation? training?
- audience: what's their tech level and background? This is probably not an issue if they're all developers but even asking the question is a good sign as it shows that you're aware of the need to adjust your presentation based on what you're trying to get across
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
suggest improvements |Â
up vote
3
down vote
Before you partake in such an exercise, make sure it's worth your time. How many more interviews? Will they make a final hiring decision based on the outcome? How much time and effort have you already spent interviewing for this position? Some companies have no issue with wasting applicants' time.
Additionally - is architecture a part of the job description? Because if it's not, I'd question the relevance.
answered May 17 '16 at 21:17
Xavier J
26.3k104797
suggest improvements |Â
up vote
2
down vote
This seems to be a completely reasonable interview technique to me. They want to see how you think, how deeply you understand projects you work on, etc. It is highly unlikely the prospective employer will gain anything significant from an hour of lecture on a random project of your choice (i.e. consulting or confidential trade secrets) except a better understanding of you as a potential employee.
As for time investment, that is completely up to you. From my perspective, it is not a particularly onerous requirement.
answered May 17 '16 at 20:43
dyeje
43129
suggest improvements |Â
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();
);
);
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
Do not make up an imaginary project. Period. You cannot possibly fake enough knowledge of a made-up project to answer the kind of questions you'll get and you won't have the time to make a reasonable facsimile.
Whether this is on the level depends and whether the request and the amount of work it will entail is reasonable depends on a number of factors that you don't mention. Based on the info you provide I'm inclined to consider this a legitimate request from the hiring company to get to know your style as they just asked you for any random project you worked on. It could be a hobby project or something from a past employer. As long as you sanitise the architecture, which is to say scrub all company-specific references or business logic, you won't give them any useful information from a previous employer. Since it can be on anything this isn't a request for you to do free work. The lack of restrictions also mean that you are free to avoid projects that might be covered by an NDA.
As for whether it's reasonable, I would probably balk at the kind of effort this would involve if this was a low-level programming gig. But if presentations or client contact are a significant part of the description this is entirely reasonable and I'd say it's a great way for them to filter out good candidates. Even if that's not the case, this kind of interview lets them select for a specific kind of candidate that matches their culture, which isn't a bad thing at all.
Finally, I can't tell from your post if this would be an hour-long presentation, but that seems a bit long for talking about a random project. I would sooner expect a twenty-minute presentation followed by Q&A. If you're unsure I'd ask clarification on that. In fact, it's entirely reasonable to ask for some more details on this and I highly encourage you to do so. You should ask the hiring manager about:
- the goal of the presentation: they can answer your question better than this site could
- timeline: how much content should you give
- focus: architecture? languages? interface points? documentation? training?
- audience: what's their tech level and background? This is probably not an issue if they're all developers but even asking the question is a good sign as it shows that you're aware of the need to adjust your presentation based on what you're trying to get across
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
suggest improvements |Â
up vote
6
down vote
accepted
Do not make up an imaginary project. Period. You cannot possibly fake enough knowledge of a made-up project to answer the kind of questions you'll get and you won't have the time to make a reasonable facsimile.
Whether this is on the level depends and whether the request and the amount of work it will entail is reasonable depends on a number of factors that you don't mention. Based on the info you provide I'm inclined to consider this a legitimate request from the hiring company to get to know your style as they just asked you for any random project you worked on. It could be a hobby project or something from a past employer. As long as you sanitise the architecture, which is to say scrub all company-specific references or business logic, you won't give them any useful information from a previous employer. Since it can be on anything this isn't a request for you to do free work. The lack of restrictions also mean that you are free to avoid projects that might be covered by an NDA.
As for whether it's reasonable, I would probably balk at the kind of effort this would involve if this was a low-level programming gig. But if presentations or client contact are a significant part of the description this is entirely reasonable and I'd say it's a great way for them to filter out good candidates. Even if that's not the case, this kind of interview lets them select for a specific kind of candidate that matches their culture, which isn't a bad thing at all.
Finally, I can't tell from your post if this would be an hour-long presentation, but that seems a bit long for talking about a random project. I would sooner expect a twenty-minute presentation followed by Q&A. If you're unsure I'd ask clarification on that. In fact, it's entirely reasonable to ask for some more details on this and I highly encourage you to do so. You should ask the hiring manager about:
- the goal of the presentation: they can answer your question better than this site could
- timeline: how much content should you give
- focus: architecture? languages? interface points? documentation? training?
- audience: what's their tech level and background? This is probably not an issue if they're all developers but even asking the question is a good sign as it shows that you're aware of the need to adjust your presentation based on what you're trying to get across
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
suggest improvements |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
Do not make up an imaginary project. Period. You cannot possibly fake enough knowledge of a made-up project to answer the kind of questions you'll get and you won't have the time to make a reasonable facsimile.
Whether this is on the level depends and whether the request and the amount of work it will entail is reasonable depends on a number of factors that you don't mention. Based on the info you provide I'm inclined to consider this a legitimate request from the hiring company to get to know your style as they just asked you for any random project you worked on. It could be a hobby project or something from a past employer. As long as you sanitise the architecture, which is to say scrub all company-specific references or business logic, you won't give them any useful information from a previous employer. Since it can be on anything this isn't a request for you to do free work. The lack of restrictions also mean that you are free to avoid projects that might be covered by an NDA.
As for whether it's reasonable, I would probably balk at the kind of effort this would involve if this was a low-level programming gig. But if presentations or client contact are a significant part of the description this is entirely reasonable and I'd say it's a great way for them to filter out good candidates. Even if that's not the case, this kind of interview lets them select for a specific kind of candidate that matches their culture, which isn't a bad thing at all.
Finally, I can't tell from your post if this would be an hour-long presentation, but that seems a bit long for talking about a random project. I would sooner expect a twenty-minute presentation followed by Q&A. If you're unsure I'd ask clarification on that. In fact, it's entirely reasonable to ask for some more details on this and I highly encourage you to do so. You should ask the hiring manager about:
- the goal of the presentation: they can answer your question better than this site could
- timeline: how much content should you give
- focus: architecture? languages? interface points? documentation? training?
- audience: what's their tech level and background? This is probably not an issue if they're all developers but even asking the question is a good sign as it shows that you're aware of the need to adjust your presentation based on what you're trying to get across
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
Do not make up an imaginary project. Period. You cannot possibly fake enough knowledge of a made-up project to answer the kind of questions you'll get and you won't have the time to make a reasonable facsimile.
Whether this is on the level depends and whether the request and the amount of work it will entail is reasonable depends on a number of factors that you don't mention. Based on the info you provide I'm inclined to consider this a legitimate request from the hiring company to get to know your style as they just asked you for any random project you worked on. It could be a hobby project or something from a past employer. As long as you sanitise the architecture, which is to say scrub all company-specific references or business logic, you won't give them any useful information from a previous employer. Since it can be on anything this isn't a request for you to do free work. The lack of restrictions also mean that you are free to avoid projects that might be covered by an NDA.
As for whether it's reasonable, I would probably balk at the kind of effort this would involve if this was a low-level programming gig. But if presentations or client contact are a significant part of the description this is entirely reasonable and I'd say it's a great way for them to filter out good candidates. Even if that's not the case, this kind of interview lets them select for a specific kind of candidate that matches their culture, which isn't a bad thing at all.
Finally, I can't tell from your post if this would be an hour-long presentation, but that seems a bit long for talking about a random project. I would sooner expect a twenty-minute presentation followed by Q&A. If you're unsure I'd ask clarification on that. In fact, it's entirely reasonable to ask for some more details on this and I highly encourage you to do so. You should ask the hiring manager about:
- the goal of the presentation: they can answer your question better than this site could
- timeline: how much content should you give
- focus: architecture? languages? interface points? documentation? training?
- audience: what's their tech level and background? This is probably not an issue if they're all developers but even asking the question is a good sign as it shows that you're aware of the need to adjust your presentation based on what you're trying to get across
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
answered May 17 '16 at 21:06
Lilienthal♦
53.9k36183218
53.9k36183218
suggest improvements |Â
suggest improvements |Â
up vote
3
down vote
Before you partake in such an exercise, make sure it's worth your time. How many more interviews? Will they make a final hiring decision based on the outcome? How much time and effort have you already spent interviewing for this position? Some companies have no issue with wasting applicants' time.
Additionally - is architecture a part of the job description? Because if it's not, I'd question the relevance.
answered May 17 '16 at 21:17
Xavier J
26.3k104797
suggest improvements |Â
up vote
3
down vote
Before you partake in such an exercise, make sure it's worth your time. How many more interviews? Will they make a final hiring decision based on the outcome? How much time and effort have you already spent interviewing for this position? Some companies have no issue with wasting applicants' time.
Additionally - is architecture a part of the job description? Because if it's not, I'd question the relevance.
answered May 17 '16 at 21:17
Xavier J
26.3k104797
suggest improvements |Â
up vote
3
down vote
up vote
3
down vote
Before you partake in such an exercise, make sure it's worth your time. How many more interviews? Will they make a final hiring decision based on the outcome? How much time and effort have you already spent interviewing for this position? Some companies have no issue with wasting applicants' time.
Additionally - is architecture a part of the job description? Because if it's not, I'd question the relevance.
answered May 17 '16 at 21:17
Xavier J
26.3k104797
Before you partake in such an exercise, make sure it's worth your time. How many more interviews? Will they make a final hiring decision based on the outcome? How much time and effort have you already spent interviewing for this position? Some companies have no issue with wasting applicants' time.
Additionally - is architecture a part of the job description? Because if it's not, I'd question the relevance.
answered May 17 '16 at 21:17
Xavier J
26.3k104797
answered May 17 '16 at 21:17
Xavier J
26.3k104797
answered May 17 '16 at 21:17
Xavier J
26.3k104797
answered May 17 '16 at 21:17
Xavier J
26.3k104797
26.3k104797
suggest improvements |Â
suggest improvements |Â
up vote
2
down vote
This seems to be a completely reasonable interview technique to me. They want to see how you think, how deeply you understand projects you work on, etc. It is highly unlikely the prospective employer will gain anything significant from an hour of lecture on a random project of your choice (i.e. consulting or confidential trade secrets) except a better understanding of you as a potential employee.
As for time investment, that is completely up to you. From my perspective, it is not a particularly onerous requirement.
answered May 17 '16 at 20:43
dyeje
43129
suggest improvements |Â
up vote
2
down vote
This seems to be a completely reasonable interview technique to me. They want to see how you think, how deeply you understand projects you work on, etc. It is highly unlikely the prospective employer will gain anything significant from an hour of lecture on a random project of your choice (i.e. consulting or confidential trade secrets) except a better understanding of you as a potential employee.
As for time investment, that is completely up to you. From my perspective, it is not a particularly onerous requirement.
answered May 17 '16 at 20:43
dyeje
43129
suggest improvements |Â
up vote
2
down vote
up vote
2
down vote
This seems to be a completely reasonable interview technique to me. They want to see how you think, how deeply you understand projects you work on, etc. It is highly unlikely the prospective employer will gain anything significant from an hour of lecture on a random project of your choice (i.e. consulting or confidential trade secrets) except a better understanding of you as a potential employee.
As for time investment, that is completely up to you. From my perspective, it is not a particularly onerous requirement.
answered May 17 '16 at 20:43
dyeje
43129
This seems to be a completely reasonable interview technique to me. They want to see how you think, how deeply you understand projects you work on, etc. It is highly unlikely the prospective employer will gain anything significant from an hour of lecture on a random project of your choice (i.e. consulting or confidential trade secrets) except a better understanding of you as a potential employee.
As for time investment, that is completely up to you. From my perspective, it is not a particularly onerous requirement.
answered May 17 '16 at 20:43
dyeje
43129
answered May 17 '16 at 20:43
dyeje
43129
answered May 17 '16 at 20:43
dyeje
43129
answered May 17 '16 at 20:43
dyeje
43129
43129
suggest improvements |Â
suggest improvements |Â
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%2f67308%2finterview-asked-to-give-an-hour-long-presentation-on-architecture-of-previous-p%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
1
A hour seems a bit much, but checking candidates understand the projects they've worked on and asking what they would have done differently is a good interviewing approach.
– Nathan Cooper
May 18 '16 at 4:18