Re: Clojure resume tips?

On Apr 18, 2017 2:16 PM, "Jason Basanese" wrote: Thanks, I have been told this before. After hearing it a couple more times I am taking it much closer to heart. also check-out #jobs-discuss on the clojurians slack thing. this kind of question would be welcome there,

Re: Clojure resume tips?

Thanks, I have been told this before. After hearing it a couple more times I am taking it much closer to heart. On Sunday, March 26, 2017 at 7:28:08 PM UTC-4, Gregg Reynolds wrote: > > > > On Mar 23, 2017 12:10 PM, "Jason Basanese" > wrote: > > Attached is a fairly bad

Re: Clojure resume tips?

Hmm. I never really considered anyone would try to use them outside of just looking at the source code. You have made me second guess that. I definitely will consider adding ReadMes. Also thanks for the link. On Friday, March 24, 2017 at 12:36:36 AM UTC-4, James Gatannah wrote: > > To get back

Re: Clojure resume tips?

*He sent us a bill for an hour of consulting. *Wow, noted. Maybe I would be more hesitant to give questions directly related to the job if I ever found myself interviewing. On Friday, March 24, 2017 at 12:17:14 AM UTC-4, James Gatannah wrote: > > > > On Thursday, March 23, 2017 at 2:00:28 PM

Re: Clojure resume tips?

I might think that 30-40 hours for a sample is excessive. Honestly many candidates worry and or prepare for at least two hours for an interview. Then have around an hour round trip. They also might spend a full hour in an interview. With about four hours to replace or supplement an interview

Re: Clojure resume tips?

*Getting involved in collaborative open source development (i.e. contributing to established projects) is likely to increase your confidence, as well as that of a prospective employer.* This is a good point I see echoed in a few other posts. Thanks for the tip. In my case and I imagine in the

Re: Clojure resume tips?

I had never thought of a resume this way "The function of the resume is to motivate someone to look deeper" thanks. On Thursday, March 23, 2017 at 1:16:41 PM UTC-4, Gary Trakhman wrote: > > I'd put examples of interesting (hard, nontrivial) projects you worked on > during your time, not just

Re: Clojure resume tips?

Thanks for the response Luke. You make a lot of good points. Thomas Ptacek's article was eye opening. The suggestion to ask the hiring manager if they would like a sample of me doing company related work for them is a good one. The networking tip is one I hear time and time again, but the more

Re: Clojure resume tips?

On Mar 23, 2017 12:10 PM, "Jason Basanese" wrote: Attached is a fairly bad resume that I am using. Any tips on how I might change it to appeal to more places that are looking for functional developers? nobody ever gets hired on the strength of their resume. at best

Re: Clojure resume tips?

On Mar 23, 2017 2:00 PM, "Mark Engelberg" wrote: On Thu, Mar 23, 2017 at 11:24 AM, Luke Burton wrote: > > * So … if I was in your position, knowing what I know now, if I couldn't > find companies that had very progressive hiring practices, I would

Re: Clojure resume tips?

To get back on-target, I think you should highlight 1 or maybe 2 of your github repos and go flesh them out. I had high hopes for both click-time-fun and cljs-game, but wasn't sure what to try or where to start. Working demos are pretty magical, and, honestly, incredibly rare.

Re: Clojure resume tips?

On Thursday, March 23, 2017 at 2:00:28 PM UTC-5, puzzler wrote: > > On Thu, Mar 23, 2017 at 11:24 AM, Luke Burton > wrote: > > Insightful post about a lot of things related to hiring, but I have to > take exception with this very last point. Recently, a friend of mine >

Re: Clojure resume tips?

> On Mar 23, 2017, at 11:59 AM, Mark Engelberg wrote: > > On Thu, Mar 23, 2017 at 11:24 AM, Luke Burton > wrote: > > * So … if I was in your position, knowing what I know now, if I couldn't find > companies that had

Re: Clojure resume tips?

On Thu, Mar 23, 2017 at 11:24 AM, Luke Burton wrote: > > * So … if I was in your position, knowing what I know now, if I couldn't > find companies that had very progressive hiring practices, I would make my > resume stand out by leading in with an offer to spend a few hours

Re: Clojure resume tips?

> On Mar 23, 2017, at 10:10 AM, Jason Basanese wrote: > > Attached is a fairly bad resume that I am using. Any tips on how I might > change it to appeal to more places that are looking for functional developers? Couple of general tips … based on a few decades of

Re: Clojure resume tips?

Jason, If it were my resumé, I would consider including only the technologies I had interest in working with professionally. Getting involved in collaborative open source development (i.e. contributing to established projects) is likely to increase your confidence, as well as that of a

Re: Clojure resume tips?

I'd put examples of interesting (hard, nontrivial) projects you worked on during your time, not just keywords. The function of the resume is to motivate someone to look deeper instead of throwing it out. The function of the top of the resume is to hook someone to read the rest of it. What's