Indeed | Full stack engineer (RoR or Java) | Onsite or remote | Austin TX | Full time
We are looking for senior Java and Ruby engineers to join our team full-time.
Our Assessments team has a simple mission: help candidates get the right job. We let people build a profile to demonstrate their knowledge, skills, and abilities using job assessments… we’re trying to make the resume a thing of the past. Our team is highly distributed geographically so this position is open to remote candidates anywhere in the US or Canada as well as in our offices in Austin and San Francisco.Our team is nimble and scrappy. We ship new capabilities often and quickly by explicitly asking ourselves the 80/20 question a.k.a. the Pareto Principle.
You will:
Build the core functionality of our assessments platform and own design and execution
Develop our API and integrations with external applicant tracking systems like Greenhouse and Jobvite
Interviewed builds job assessments that let candidates demonstrate their real world skills so that hiring managers don't have to rely on resumes, behavioral interviews, and personality tests -- which are inherently flawed.
We are looking for great remote engineers who have experience working with Rails or React.
We've been using Zube at Interviewed and really like it.
We'd been using Github Issues previously but found it hard to prioritize our tickets in a way that was natural for us. The ability to drag and drop reorder our backlog has really helped with that.
Also, the UI works well for quick updates during our morning standup.
You really need to add searching capabilities or categorize listings by country/state to avoid scrolling every post to find something in my area that interests me.
Listing any required years experience with a particular technology seems like a mistake.
A good engineer is a good engineer and shouldn't need N+ years experience with a language/framework/tool to make an impact on a good team that's willing to do a little training.
When I see something like "7+ years PHP experience", I wonder what it is they think they're using that as a proxy for and why they don't just mention it directly.
It's not like there's a standard progression in technologies where you learn certain things in years 5-7, etc.
I can see there's a difference between say 1 years and 3 years, but is there really a difference you can count on being true if someone used a tech for 5 years vs 3? 7 vs 3?
> I wonder what it is they think they're using that as a proxy for and why they don't just mention it directly.
A very smart developer who I respect once said something like: when you are young, you have lots of energy and want to learn/use the latest technology. As you get older and gain more experience, you start to see the patterns. It's not about the technology, there are repeated themes and solutions. But when you start realizing this and have accumulated 7 years of experience, you may be transitioning out and wanting to begin starting a family. So the people who might be most qualified might be wanting to leave the intensity of coding for the relative stability of management.
As someone once said - the entire premise of capitalism is based on overpaying the first few years and underpaying you for the next 20 or 30 years.
So perhaps 7 years of experience is a cludgy filter for the relative graybeards who understand that technology is just a tool, not an end.
More than 2 * more libraries used, 2 times more projects, seen the language evolve, worked with 2 * more people, etc. Domain knowledge is a massive help for people doing things. The 7 year person has likely used far more things than the 3 year person. However if the 3 year person knows how to use a gun, and the 7 year person only knows how to use a knife - then the 3 year person wins[1]. Of course, many times the gun turns out to be a water pistol - or the 7 year ninja can fart in their general direction[2], wait for a flinch... and then throw the knife!
Sure, but sometimes you may not have the time, inclination or ability to train someone on a technology.
Anyway, I view it more as "this is what experience we imagine the ideal candidate has" rather than "you literally need 4 full years of platform X experience to get hired"
Right, but you realize that the moment an outsourcing firm gets hold of that listing, those turn into requirements?
I almost didn't get called for a bog-standard programming contract because I lack a BS in Computer Science. You'd think 10 years as both front-end and back-end developer would trigger a light-bulb, but nope, not even a matchhead.
I totally agree, just make sure you list what technologies they will be using. Then indicate that the applicant must be really good at them or be willing to learn them fast.
Fair enough, but you can fail in something other than a bootstrapped startup and learn from it, all without risking your own personal stress, finances, etc.
Anything that reduces friction for a user to get started with your product has the potential to be a good thing.
But if your goal is to make money, and not just generate usage, I can see some possible problems with this approach. Not having a way to circle back with a user is bad.
Also, if someone truly needs a solution to the problem you are solving a signup form will usually not stand in their way.
It would be interesting to A/B test the entire user lifecycle to see if this approach has impact on the metrics that actually matter.
What is the Chilean government doing to bring over already established, innovative companies?
It seems that one good way to inject innovation is to introduce companies that can employ young, entrepreneurial Chileans and set examples they can follow in future ventures.
We are looking for senior Java and Ruby engineers to join our team full-time.
Our Assessments team has a simple mission: help candidates get the right job. We let people build a profile to demonstrate their knowledge, skills, and abilities using job assessments… we’re trying to make the resume a thing of the past. Our team is highly distributed geographically so this position is open to remote candidates anywhere in the US or Canada as well as in our offices in Austin and San Francisco.Our team is nimble and scrappy. We ship new capabilities often and quickly by explicitly asking ourselves the 80/20 question a.k.a. the Pareto Principle.
You will:
Build the core functionality of our assessments platform and own design and execution
Develop our API and integrations with external applicant tracking systems like Greenhouse and Jobvite
Scale to serve 100M+ job seekers
Please apply here:
https://www.indeed.jobs/career/JobDetail/Sr-Remote-Java-Engi...
https://www.indeed.jobs/career/JobDetail/Remote-Software-Eng...
Indeed provides a variety of benefits that help us focus on our mission of helping people get jobs.
View our bounty of perks: http://indeedhi.re/IndeedBenefits