do

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

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

Interviewed (YC S15) | Software Engineer | REMOTE (US, Canada, Brazil)

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.

Learn more about the position here: https://internal.interviewed.com/jobs/full-stack-engineer-hd...

Email: daniel@interviewed.com

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.

A QA test case management tool integrated with Github Issues.

http://imgur.com/a/0oqGO

Designed to be easy to navigate with the keyboard and replace the spreadsheets I normally use on projects.

If anyone out there needs something like this please shoot me an email. Planning on launching a V1 this weekend.

This is not really a valid use case for meetup.com, which is good for recurring, topical meetings.

Plus, its not free to start a new meetup.

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.

I would also add: how well do you handle rejection and failure?

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 currently looking at the smartphone app approach. The phone approach was easier prototype which is why we started there.

We started with the phone because it was easier to get a working prototype out the door and its truly a ubiquitous solution.

We are looking at building an iphone and android app. Its starting to seem like a more viable way to make the service profitable.

We are considering a monthly fee, but for the economics to work we will need to be making roughly that $1 per hour of usage to cover phone call and other costs.

We are still searching for the demographic that needs some sort of web content on the go, can't get it on their smartphone and is willing to pay for it.

Any ideas would be appreciated.