Your Ideal Companies to Work at?

Robert Gold — Fri, 11 Oct 2019 16:18:47 +0000

Talented engineers are a hot commodity right now, especially in NYC. And since the job economy is doing so well, candidates still have so many opportunities to choose between.

We've been using a variety of ways to get in touch with engineers in our stack:

-Inclusive job posts (devoid of years of experience)
-Trusted 3rd Party Technical Recruiters
-Reaching out directly to you in any way imaginable! (it's called sourcing)

I imagine it must get tiring to hear from recruiter after recruiter all boasting about how great their opportunity is for you, and how you'd be a "perfect fit" on the team.

I'm actually curious to hear from you. From the tech stack or team, to the company's mission or interesting technical challenges... what do you look for in a company when you're on the job search?

Engineering Interviews: Your First Calls?

Robert Gold — Thu, 10 Oct 2019 21:51:20 +0000

As a new technical recruiter (in-house at a content intelligence company called Knotch), I find myself discussing technical concepts with candidates. (this is us: careers.knotch.it)

I don't code myself, and I can't help but feel like I should know so much more than I currently do. So, I bought a Coding for Dummies book that I'm using to get up to speed on the concepts of HTML/CSS/Javascript. Talking with our engineers at Knotch is also a huge help. But I can always do more. Our stack is Ruby on Rails, Javascript w/ES6, React/Redux, PostgreSQL, and data architecture in AWS.

Let me put it to the community:

When you're interviewing for an engineer role, how technical do you think your first screening call with the internal recruiter should be? Should they be well-versed in the languages and frameworks and concepts you're interviewing for?

DEV Community: Robert Gold

Your Ideal Companies to Work at?

Engineering Interviews: Your First Calls?