HN Explorer

Ask HN: How to respond to a job offer you're not sure if you're qualified for?

5 points by pyromine ↗ HN
I'm a 17 year old freshmen computer science student who has a passion for education, and I just so happened to run in to the CEO of a coder bootcamp at a conference a couple of weeks ago. I went to talk to with him the other day just because I wanted to hear more of his views on education, and while I was talking to him he asked me about my availability and pitched an idea to me that he would like me working with them on.

I'd be helping develop an internal educational tool for the bootcamp, he talked about how he could have any developer work on it and it would come out okay, but because he believes we share a similar vision in to the educational world it would be much better to have me help with them.

Now this is a dream job essentially for me, and it was just a year ago that I was actually considering attending a (different) coding bootcamp, with the only stopping factor was my parents unwillingness to financially support me.

While I don't have a written job offer yet, the conversation made in abundantly clear that he would like me to join the team, but I'm afraid what if I don't currently have the skills needed to perform well enough. I'm pretty sure I'd be able to learn everything needed to perform in the position, but it's possible that I won't be ready immediately. Does anyone have any suggestion in how to respond to an opportunity like this?

7 comments

[ 2.5 ms ] story [ 78.5 ms ] thread
anigbrowl
Just go for it and figure it out on the way. At 17 you're not really qualified for anything but you are at a peak of learning ability. If the guy likes you let him take you under his wing and teach you valuable stuff about the workplace. Just stick by the rule of never-ever bullshit - if you don't know something, say so and outline your strategy for finding out (if you have one) or ask for advice(if you don't). Enjoy.
logn
If you end up failing it's only the CEOs fault for either (1) not mentoring you correctly or (2) thinking of this idea in the first place. And I think he'd probably feel the same way. Take the offer and hope for the best. Just be honest with yourself and everyone else throughout the project but don't let that turn to fear or excessive doubt.
mrcold
No matter how much you prepare, you will never be ready for everything. Most of things you learn arise from real problems you encounter on the job. So don't try to figure out if you're prepared. Analyze it from an opportunity perspective. Opportunity is knocking. Are you going to answer or are you going to ignore it? My advice is to jump on every opportunity. Because they never come in groups.

With that aside, sounds like the CEO wants you to build his app for free. I may be wrong. But the wording is pretty standard. "Common vision" and "any developer can do it, but I like you" are usually red flags. You want to hear things like "Here is what we want to do, what are your thoughts about it?". You want to be involved. Not a disposable code monkey taking orders and instructions.

pyromine
Actually one of the first things he said was obviously we'd compensate you.

Also the common vision element came from we spent the majority of the time just discussing education. As well, your comment of wanting to be asked for input is actually exactly how the conversation went.

codeonfire
Does this job pay? If so it sounds like a better deal than stacking books in the library or being a barista. If not, I'd pass. For volunteer work it's better to get involved with some department research that might lead to a funded RA-ship someday.