Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Serving 250k developers with one support engineer

blog.railway.app

Post reply on HN
Print view View original

41–50 of 86 posts

Re: Serving 250k developers with one support engineer

#41

Post by pooper »

stanleydrew wrote: post #40
zitterbewegung wrote: post #37

Earlier quoted context omitted.

Playing devil's advocate if you don't want to do the take home test then they just filtered you out and actually is serving their desires on who they want to hire.

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.

Re: Serving 250k developers with one support engineer

#42

Post by anothernewdude »

ipaddr wrote: post #22

I checked out the open positions. There were more positions open than total employees. Are those real positions you are looking to fill or always open positions that rarely result in an actual job? I asked this because the interview process has this step where you ask the candidates to do a project and than go over it with someone. One of these little projects is design our api or build a github issue viewer frontend…

I only do the projects when they're paid.

Re: Serving 250k developers with one support engineer

#44

Post by Foobar8568 »

swatcoder wrote: post #6

Congratulations on achieving this milestone and probably keeping your customers very satisfied along the way, but I eagerly look forward to the future where everyone is so sick of virtual assistants, bots, and knowledge bases that a low ratio is what gets celebrated as a growth milestone rather than a high ratio. Automated triage is great for digital companies that want to scale cheaply, but not so great for the peop…

My client bought in the marketing slides of an Indian company that there was response within x hours of raising an incident, not actually solving but response. It's basically a "hi, we started the triage see you", in another one, DocuSign to not name, with the premium support, we are basically redirected to their help page even after 2 or 3 exchanges for clarification. Support is just awful everywhere. Hell, our management is asking the same with our L1-L2 ones for internal customer.

Re: Serving 250k developers with one support engineer

#45

Post by ankit70 »

ryanSrich wrote: post #23
nitsuaeekcm wrote: post #16

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…

Render.com?

Re: Serving 250k developers with one support engineer

#47

Post by moomoo11 »

glenngillen wrote: post #25
ipaddr wrote: post #22

I checked out the open positions. There were more positions open than total employees. Are those real positions you are looking to fill or always open positions that rarely result in an actual job? I asked this because the interview process has this step where you ask the candidates to do a project and than go over it with someone. One of these little projects is design our api or build a github issue viewer frontend…

I can’t speak for the Railway team, but I am hiring at an early stage startup myself. There is absolutely no way we’d extend offers for all of the roles we have open if a candidate arrived for all of them next week. Growing that much so quickly would be a disastrous onboarding experience for most of the new hires and potentially risk our ability to build a consistent culture with the team. So we’ll hire whichever can…

How did you find your core/initial team? Thanks

Re: Serving 250k developers with one support engineer

#48

Post by theonething »

fancyremarker wrote: post #21
theonething wrote: post #17

Can anyone comment on the security implications of using a service like this, render.com, fly.io, etc vs. rolling your own infra on AWS EC2 and friends?

It's possible for a PaaS to improve your security posture by implementing many of the security controls you'd otherwise be responsible for yourself. Every PaaS provider has a Shared Responsibility Model, like this one from AWS [0], and a good PaaS can eat up much of what would otherwise be your responsibility as an AWS customer: network architecture, secure configuration, IAM, system access (and auditing), intrusion…

Thank you. Aptible looks promising.

I have a question about endpoints. It seems like you guys charge per endpoint. I don't quite understand this. So if I'm developing an api only application, every api endpoint I develop in my application will be charged? And for Aptible to keep track, would I have to register each endpoint I develop?

If my application was just serving dynamic html pages, I wouldn't be charged per url of my application right? So why would I be charged per api endpoint?

EDIT:

Another question. Do you guys offer any SSO solutions? If not, if I used say Auth0 for authentication, are there any issues with integrating with Aptible?

Post reply on HN