Live data from Hacker News

Serving 250k developers with one support engineer

blog.railway.app

81–86 of 86 posts

Re: Serving 250k developers with one support engineer

#81
post #45

Earlier quoted context omitted.

Render.com?

I have to look into Render again at some point. I do remember when it first came out it had a lot of features missing. Most notably a redis solution.

We have fully-managed production-grade Redis now: https://render.com/docs/redis and we're also SOC 2 Type 2 compliant.

Re: Serving 250k developers with one support engineer

#83
post #41

Earlier quoted context omitted.

Yeah this. There's often a presumption like "I'm a very talented software engineer and everyone should want to hire me and thus companies shouldn't design a hiring process that I personally find annoying." Hiring is a matching process. If a company with an annoying hiring process is a bad match for you, that's fine.

As long as the whole process is transparent and fully disclosed upfront. Remember, the company has more information than the applicant.

In what sense does the company have more information? They have more information about the details of the job, sure, but the applicant has more details about themselves. Which is “more valuable” depends on the market I guess. But why do you say one party has strictly more information?

(This question is asked in good faith).

Re: Serving 250k developers with one support engineer

#84

Earlier quoted context omitted.

> This is such a hack response. Please be civil. Posting multiple job listings targeting different salary ranges isn’t a “hack response”. It’s literally how you hire properly without a crystal ball to predict exactly who will apply. Again, no company is going to drag candidates through interviews for jobs that don’t exist. I don’t understand why anything thinks that’s the case. Interviewing is work for the interviewe…

> no company is going to drag candidates through interviews for jobs that don’t exist This happens all the time . The team will have an internal candidate they want, but HR dept is worried about optics of fairness, so the team is forced to put on a show by interviewing people who have no chance of being hired.

I have heard this but as I’ve only worked at startups I’ve never seen it play out in real life. How common is it that it happens “all the time”? Only at bigcorps?

Re: Serving 250k developers with one support engineer

#85

What an impressive company. A good reminder that, even in a market with umpteen competitors, success comes down to execution. Hope they keep up the good work.

Railway does look impressive. However, as someone in the market for a Heroku alternative - I’d say there really aren’t any Heroku competitors. At least nothing directly comparable. The thing that keeps me (and I’m sure other small business owners) tied to Heroku is just how much they take care of for you. I literally never ever want to think about my infrastructure beyond initial setup. Heroku, to my knowledge, is th…

If this is the kind of experience you’re looking for I would check out Platform.sh. (Full admission, I work there)

You get a good level of abstraction for infrastructure (github.com/platformsh-templates for examples) that gets provisioned automatically, plus a built-in relationship between branches and envs that results in true staging environments for every pull request.

docs.platform.sh

Re: Serving 250k developers with one support engineer

#86

Earlier quoted context omitted.

> no company is going to drag candidates through interviews for jobs that don’t exist This happens all the time . The team will have an internal candidate they want, but HR dept is worried about optics of fairness, so the team is forced to put on a show by interviewing people who have no chance of being hired.

I have heard this but as I’ve only worked at startups I’ve never seen it play out in real life. How common is it that it happens “all the time”? Only at bigcorps?

It's an HR thing, so if not large enough to have HR bureaucracy probably not common.
Post reply on HN