In an interview when answering a question, should you say if you're not sure?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
2
down vote

favorite












This was embarrassing but in an interview I was asked if I what the current version of Java was and I wasn't sure but had an idea. I said 7 (and the correct answer is 8). In situations like this is it better not to guess and admit you'd have to look it up, or would you guess and say your not sure? I actually do know features new in Java 8 (such as lambda expressions) but the number slipped my mind. I could've answered "I forget the number but I am familiar with the newest version and features such as x y z". I know, rookie mistake.







share|improve this question



















  • Take a guess but mention that exact number slips your mind. People understand that we all have moments like that.
    – Jacobr365
    Apr 20 '16 at 19:54










  • I hope that some questions better than that.
    – paparazzo
    Apr 20 '16 at 20:00






  • 4




    You could say "The version with lambda expressions" but don't say the number if you forgot. Is it 8 or 1.8 or 1.8.0 update 1, or is it called "service pack 5"? These are questions whose answers are not easily memorised unless you often install Java.
    – Brandin
    Apr 20 '16 at 20:08






  • 4




    This is a bizarrely specific interview question.
    – Andrew Whatever
    Apr 20 '16 at 20:36










  • "I don't know the version number, but unless I'm massively out-of-date (again!), it's the version that introduced lambda expressions and that offered massively improved annotations."
    – David Hammen
    Apr 20 '16 at 21:01
















up vote
2
down vote

favorite












This was embarrassing but in an interview I was asked if I what the current version of Java was and I wasn't sure but had an idea. I said 7 (and the correct answer is 8). In situations like this is it better not to guess and admit you'd have to look it up, or would you guess and say your not sure? I actually do know features new in Java 8 (such as lambda expressions) but the number slipped my mind. I could've answered "I forget the number but I am familiar with the newest version and features such as x y z". I know, rookie mistake.







share|improve this question



















  • Take a guess but mention that exact number slips your mind. People understand that we all have moments like that.
    – Jacobr365
    Apr 20 '16 at 19:54










  • I hope that some questions better than that.
    – paparazzo
    Apr 20 '16 at 20:00






  • 4




    You could say "The version with lambda expressions" but don't say the number if you forgot. Is it 8 or 1.8 or 1.8.0 update 1, or is it called "service pack 5"? These are questions whose answers are not easily memorised unless you often install Java.
    – Brandin
    Apr 20 '16 at 20:08






  • 4




    This is a bizarrely specific interview question.
    – Andrew Whatever
    Apr 20 '16 at 20:36










  • "I don't know the version number, but unless I'm massively out-of-date (again!), it's the version that introduced lambda expressions and that offered massively improved annotations."
    – David Hammen
    Apr 20 '16 at 21:01












up vote
2
down vote

favorite









up vote
2
down vote

favorite











This was embarrassing but in an interview I was asked if I what the current version of Java was and I wasn't sure but had an idea. I said 7 (and the correct answer is 8). In situations like this is it better not to guess and admit you'd have to look it up, or would you guess and say your not sure? I actually do know features new in Java 8 (such as lambda expressions) but the number slipped my mind. I could've answered "I forget the number but I am familiar with the newest version and features such as x y z". I know, rookie mistake.







share|improve this question











This was embarrassing but in an interview I was asked if I what the current version of Java was and I wasn't sure but had an idea. I said 7 (and the correct answer is 8). In situations like this is it better not to guess and admit you'd have to look it up, or would you guess and say your not sure? I actually do know features new in Java 8 (such as lambda expressions) but the number slipped my mind. I could've answered "I forget the number but I am familiar with the newest version and features such as x y z". I know, rookie mistake.









share|improve this question










share|improve this question




share|improve this question









asked Apr 20 '16 at 19:48









DawnJoe

1036




1036











  • Take a guess but mention that exact number slips your mind. People understand that we all have moments like that.
    – Jacobr365
    Apr 20 '16 at 19:54










  • I hope that some questions better than that.
    – paparazzo
    Apr 20 '16 at 20:00






  • 4




    You could say "The version with lambda expressions" but don't say the number if you forgot. Is it 8 or 1.8 or 1.8.0 update 1, or is it called "service pack 5"? These are questions whose answers are not easily memorised unless you often install Java.
    – Brandin
    Apr 20 '16 at 20:08






  • 4




    This is a bizarrely specific interview question.
    – Andrew Whatever
    Apr 20 '16 at 20:36










  • "I don't know the version number, but unless I'm massively out-of-date (again!), it's the version that introduced lambda expressions and that offered massively improved annotations."
    – David Hammen
    Apr 20 '16 at 21:01
















  • Take a guess but mention that exact number slips your mind. People understand that we all have moments like that.
    – Jacobr365
    Apr 20 '16 at 19:54










  • I hope that some questions better than that.
    – paparazzo
    Apr 20 '16 at 20:00






  • 4




    You could say "The version with lambda expressions" but don't say the number if you forgot. Is it 8 or 1.8 or 1.8.0 update 1, or is it called "service pack 5"? These are questions whose answers are not easily memorised unless you often install Java.
    – Brandin
    Apr 20 '16 at 20:08






  • 4




    This is a bizarrely specific interview question.
    – Andrew Whatever
    Apr 20 '16 at 20:36










  • "I don't know the version number, but unless I'm massively out-of-date (again!), it's the version that introduced lambda expressions and that offered massively improved annotations."
    – David Hammen
    Apr 20 '16 at 21:01















Take a guess but mention that exact number slips your mind. People understand that we all have moments like that.
– Jacobr365
Apr 20 '16 at 19:54




Take a guess but mention that exact number slips your mind. People understand that we all have moments like that.
– Jacobr365
Apr 20 '16 at 19:54












I hope that some questions better than that.
– paparazzo
Apr 20 '16 at 20:00




I hope that some questions better than that.
– paparazzo
Apr 20 '16 at 20:00




4




4




You could say "The version with lambda expressions" but don't say the number if you forgot. Is it 8 or 1.8 or 1.8.0 update 1, or is it called "service pack 5"? These are questions whose answers are not easily memorised unless you often install Java.
– Brandin
Apr 20 '16 at 20:08




You could say "The version with lambda expressions" but don't say the number if you forgot. Is it 8 or 1.8 or 1.8.0 update 1, or is it called "service pack 5"? These are questions whose answers are not easily memorised unless you often install Java.
– Brandin
Apr 20 '16 at 20:08




4




4




This is a bizarrely specific interview question.
– Andrew Whatever
Apr 20 '16 at 20:36




This is a bizarrely specific interview question.
– Andrew Whatever
Apr 20 '16 at 20:36












"I don't know the version number, but unless I'm massively out-of-date (again!), it's the version that introduced lambda expressions and that offered massively improved annotations."
– David Hammen
Apr 20 '16 at 21:01




"I don't know the version number, but unless I'm massively out-of-date (again!), it's the version that introduced lambda expressions and that offered massively improved annotations."
– David Hammen
Apr 20 '16 at 21:01










3 Answers
3






active

oldest

votes

















up vote
6
down vote













I always answer with the truth. That's my "prime directive" in an interview.



If the truth is that I don't know something, I tell them. I would much rather have them see that I'm willing to admit that I don't know something than to have them discover through a wrong answer that I'm trying to put something past them.



When I've interviewed people, I've sometimes asked them questions I was nearly certain they wouldn't know the answer to in order to see how they would respond. That tells the interviewer something about the candidate and how they react under a stress situation as well.



I was applying for a Delphi position about 25 years ago and the interviewer asked several questions about C++. I answered him honestly that I didn't know. He later told me that he was specifically trying to see whether I'd try to BS my way through or not and also how I would react to the stress of seemingly being asked something for which I was not the least bit prepared.



I'm not suggesting that you should just say "I don't know." and leave it at that. I think your explanation about the features is the kind of elaboration mixed with forthrightness that would be the most helpful.






share|improve this answer

















  • 2




    +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
    – adelphus
    Apr 21 '16 at 13:49

















up vote
2
down vote













You should be open about you not knowing or not being sure about something.



And here is the main reason, in my opinion, for that:




If you say "I don't know" when you don't know, they will trust you
when you say "I know".




Now that might look stupid, but it is not! I like a lot working with people who are open about not knowing. Actually, I find it a quality: to be aware of your limitations and to be transparent about it.



In the other hand, I don't trust people who never say "I don't know". I know as a fact that nobody knows everything, so if someone never expresses doubt I will never be sure if they really know what they area talking about, as they never "don't know".



Besides this, as my own interview strategy I try to build a connection by being human: I make mistakes, I don't always know everything, but at least I am an honest person who will not lie about what I can do.






share|improve this answer




























    up vote
    1
    down vote













    I once interviewed a man where his answer to every question I threw at him was "I don't know, I would have to check the help files".



    I recommended that we hire him and we did.



    I saw his resume, I knew he could do the job, but the work was for a newspaper. I deliberately asked him questions he could not possibly know because I wanted to know if I was dealing with someone who would try to hide his mistakes, or who was overconfident.



    His honesty got him the job.






    share|improve this answer

















    • 3




      You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
      – Laconic Droid
      Apr 20 '16 at 22:01










    • Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
      – Richard U
      Apr 21 '16 at 12:21










    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "423"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    noCode: true, onDemand: false,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f65578%2fin-an-interview-when-answering-a-question-should-you-say-if-youre-not-sure%23new-answer', 'question_page');

    );

    Post as a guest

























    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













    I always answer with the truth. That's my "prime directive" in an interview.



    If the truth is that I don't know something, I tell them. I would much rather have them see that I'm willing to admit that I don't know something than to have them discover through a wrong answer that I'm trying to put something past them.



    When I've interviewed people, I've sometimes asked them questions I was nearly certain they wouldn't know the answer to in order to see how they would respond. That tells the interviewer something about the candidate and how they react under a stress situation as well.



    I was applying for a Delphi position about 25 years ago and the interviewer asked several questions about C++. I answered him honestly that I didn't know. He later told me that he was specifically trying to see whether I'd try to BS my way through or not and also how I would react to the stress of seemingly being asked something for which I was not the least bit prepared.



    I'm not suggesting that you should just say "I don't know." and leave it at that. I think your explanation about the features is the kind of elaboration mixed with forthrightness that would be the most helpful.






    share|improve this answer

















    • 2




      +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
      – adelphus
      Apr 21 '16 at 13:49














    up vote
    6
    down vote













    I always answer with the truth. That's my "prime directive" in an interview.



    If the truth is that I don't know something, I tell them. I would much rather have them see that I'm willing to admit that I don't know something than to have them discover through a wrong answer that I'm trying to put something past them.



    When I've interviewed people, I've sometimes asked them questions I was nearly certain they wouldn't know the answer to in order to see how they would respond. That tells the interviewer something about the candidate and how they react under a stress situation as well.



    I was applying for a Delphi position about 25 years ago and the interviewer asked several questions about C++. I answered him honestly that I didn't know. He later told me that he was specifically trying to see whether I'd try to BS my way through or not and also how I would react to the stress of seemingly being asked something for which I was not the least bit prepared.



    I'm not suggesting that you should just say "I don't know." and leave it at that. I think your explanation about the features is the kind of elaboration mixed with forthrightness that would be the most helpful.






    share|improve this answer

















    • 2




      +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
      – adelphus
      Apr 21 '16 at 13:49












    up vote
    6
    down vote










    up vote
    6
    down vote









    I always answer with the truth. That's my "prime directive" in an interview.



    If the truth is that I don't know something, I tell them. I would much rather have them see that I'm willing to admit that I don't know something than to have them discover through a wrong answer that I'm trying to put something past them.



    When I've interviewed people, I've sometimes asked them questions I was nearly certain they wouldn't know the answer to in order to see how they would respond. That tells the interviewer something about the candidate and how they react under a stress situation as well.



    I was applying for a Delphi position about 25 years ago and the interviewer asked several questions about C++. I answered him honestly that I didn't know. He later told me that he was specifically trying to see whether I'd try to BS my way through or not and also how I would react to the stress of seemingly being asked something for which I was not the least bit prepared.



    I'm not suggesting that you should just say "I don't know." and leave it at that. I think your explanation about the features is the kind of elaboration mixed with forthrightness that would be the most helpful.






    share|improve this answer













    I always answer with the truth. That's my "prime directive" in an interview.



    If the truth is that I don't know something, I tell them. I would much rather have them see that I'm willing to admit that I don't know something than to have them discover through a wrong answer that I'm trying to put something past them.



    When I've interviewed people, I've sometimes asked them questions I was nearly certain they wouldn't know the answer to in order to see how they would respond. That tells the interviewer something about the candidate and how they react under a stress situation as well.



    I was applying for a Delphi position about 25 years ago and the interviewer asked several questions about C++. I answered him honestly that I didn't know. He later told me that he was specifically trying to see whether I'd try to BS my way through or not and also how I would react to the stress of seemingly being asked something for which I was not the least bit prepared.



    I'm not suggesting that you should just say "I don't know." and leave it at that. I think your explanation about the features is the kind of elaboration mixed with forthrightness that would be the most helpful.







    share|improve this answer













    share|improve this answer



    share|improve this answer











    answered Apr 20 '16 at 20:45









    Chris E

    40.4k22129166




    40.4k22129166







    • 2




      +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
      – adelphus
      Apr 21 '16 at 13:49












    • 2




      +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
      – adelphus
      Apr 21 '16 at 13:49







    2




    2




    +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
    – adelphus
    Apr 21 '16 at 13:49




    +1 After conducting many interviews, I also ask at least one question which I'm sure the candidate doesn't know. If they don't reply somewhere with "I don't know", I would mark them down. When working in teams, straightforward honesty is incredibly important.
    – adelphus
    Apr 21 '16 at 13:49












    up vote
    2
    down vote













    You should be open about you not knowing or not being sure about something.



    And here is the main reason, in my opinion, for that:




    If you say "I don't know" when you don't know, they will trust you
    when you say "I know".




    Now that might look stupid, but it is not! I like a lot working with people who are open about not knowing. Actually, I find it a quality: to be aware of your limitations and to be transparent about it.



    In the other hand, I don't trust people who never say "I don't know". I know as a fact that nobody knows everything, so if someone never expresses doubt I will never be sure if they really know what they area talking about, as they never "don't know".



    Besides this, as my own interview strategy I try to build a connection by being human: I make mistakes, I don't always know everything, but at least I am an honest person who will not lie about what I can do.






    share|improve this answer

























      up vote
      2
      down vote













      You should be open about you not knowing or not being sure about something.



      And here is the main reason, in my opinion, for that:




      If you say "I don't know" when you don't know, they will trust you
      when you say "I know".




      Now that might look stupid, but it is not! I like a lot working with people who are open about not knowing. Actually, I find it a quality: to be aware of your limitations and to be transparent about it.



      In the other hand, I don't trust people who never say "I don't know". I know as a fact that nobody knows everything, so if someone never expresses doubt I will never be sure if they really know what they area talking about, as they never "don't know".



      Besides this, as my own interview strategy I try to build a connection by being human: I make mistakes, I don't always know everything, but at least I am an honest person who will not lie about what I can do.






      share|improve this answer























        up vote
        2
        down vote










        up vote
        2
        down vote









        You should be open about you not knowing or not being sure about something.



        And here is the main reason, in my opinion, for that:




        If you say "I don't know" when you don't know, they will trust you
        when you say "I know".




        Now that might look stupid, but it is not! I like a lot working with people who are open about not knowing. Actually, I find it a quality: to be aware of your limitations and to be transparent about it.



        In the other hand, I don't trust people who never say "I don't know". I know as a fact that nobody knows everything, so if someone never expresses doubt I will never be sure if they really know what they area talking about, as they never "don't know".



        Besides this, as my own interview strategy I try to build a connection by being human: I make mistakes, I don't always know everything, but at least I am an honest person who will not lie about what I can do.






        share|improve this answer













        You should be open about you not knowing or not being sure about something.



        And here is the main reason, in my opinion, for that:




        If you say "I don't know" when you don't know, they will trust you
        when you say "I know".




        Now that might look stupid, but it is not! I like a lot working with people who are open about not knowing. Actually, I find it a quality: to be aware of your limitations and to be transparent about it.



        In the other hand, I don't trust people who never say "I don't know". I know as a fact that nobody knows everything, so if someone never expresses doubt I will never be sure if they really know what they area talking about, as they never "don't know".



        Besides this, as my own interview strategy I try to build a connection by being human: I make mistakes, I don't always know everything, but at least I am an honest person who will not lie about what I can do.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered Apr 20 '16 at 21:43









        Mr Me

        1,558713




        1,558713




















            up vote
            1
            down vote













            I once interviewed a man where his answer to every question I threw at him was "I don't know, I would have to check the help files".



            I recommended that we hire him and we did.



            I saw his resume, I knew he could do the job, but the work was for a newspaper. I deliberately asked him questions he could not possibly know because I wanted to know if I was dealing with someone who would try to hide his mistakes, or who was overconfident.



            His honesty got him the job.






            share|improve this answer

















            • 3




              You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
              – Laconic Droid
              Apr 20 '16 at 22:01










            • Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
              – Richard U
              Apr 21 '16 at 12:21














            up vote
            1
            down vote













            I once interviewed a man where his answer to every question I threw at him was "I don't know, I would have to check the help files".



            I recommended that we hire him and we did.



            I saw his resume, I knew he could do the job, but the work was for a newspaper. I deliberately asked him questions he could not possibly know because I wanted to know if I was dealing with someone who would try to hide his mistakes, or who was overconfident.



            His honesty got him the job.






            share|improve this answer

















            • 3




              You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
              – Laconic Droid
              Apr 20 '16 at 22:01










            • Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
              – Richard U
              Apr 21 '16 at 12:21












            up vote
            1
            down vote










            up vote
            1
            down vote









            I once interviewed a man where his answer to every question I threw at him was "I don't know, I would have to check the help files".



            I recommended that we hire him and we did.



            I saw his resume, I knew he could do the job, but the work was for a newspaper. I deliberately asked him questions he could not possibly know because I wanted to know if I was dealing with someone who would try to hide his mistakes, or who was overconfident.



            His honesty got him the job.






            share|improve this answer













            I once interviewed a man where his answer to every question I threw at him was "I don't know, I would have to check the help files".



            I recommended that we hire him and we did.



            I saw his resume, I knew he could do the job, but the work was for a newspaper. I deliberately asked him questions he could not possibly know because I wanted to know if I was dealing with someone who would try to hide his mistakes, or who was overconfident.



            His honesty got him the job.







            share|improve this answer













            share|improve this answer



            share|improve this answer











            answered Apr 20 '16 at 21:04









            Richard U

            77.2k56200307




            77.2k56200307







            • 3




              You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
              – Laconic Droid
              Apr 20 '16 at 22:01










            • Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
              – Richard U
              Apr 21 '16 at 12:21












            • 3




              You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
              – Laconic Droid
              Apr 20 '16 at 22:01










            • Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
              – Richard U
              Apr 21 '16 at 12:21







            3




            3




            You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
            – Laconic Droid
            Apr 20 '16 at 22:01




            You're lucky he accepted. If someone used that interview technique on me I'd think they were talking to the wrong candidate or had no idea about the position I was interested in.
            – Laconic Droid
            Apr 20 '16 at 22:01












            Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
            – Richard U
            Apr 21 '16 at 12:21




            Perhaps, but I had to have someone who wouldn't try to cover his own backside, and have his mistakes seen by millions the next day in the paper. This was for one of the biggest name newspapers in the country.
            – Richard U
            Apr 21 '16 at 12:21












             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f65578%2fin-an-interview-when-answering-a-question-should-you-say-if-youre-not-sure%23new-answer', 'question_page');

            );

            Post as a guest

















































































            Comments

            Popular posts from this blog

            What does second last employer means? [closed]

            Installing NextGIS Connect into QGIS 3?

            One-line joke