Could be updated: Interviewer: Could you give us a couple of examples of carpentry projects you have completed in your spare time, and do you have a portfolio of projects you have worked on outside of your day-to-day job? Carpenter: Uhm, what do you mean? Interviewer: I mean like carpentry in your community, or a project you've completed to hone your skills outside work? Carpenter: Oh, I am usually quite tired of ham…
Interviewer: Also, do you have any full stack experience?
Carpenter: Yeah, I guess.
Interviewer: How quickly would you adapt to using a new tool framework that comes out in the market?
Carpenter: I would rather choose to use the tools that I have honed my skills in and am good at.
Interviewer: But, considering the toolbase that our org uses, our other carpenter say that some new kit/framework comes out every other day and they all keep up. I think that toolbench is called JS in short.
Carpenter: ...
Interviewer: Also, how about the fragile methodology, any experience in that?
Carpenter: Yeah, I guess.
But strictly speaking, considering that the outcome from both disciplines carpentry and software development are on opposite sides of tangibility, a straight up comparison isn't really helpful, to both disciplines.