Hacker News Reader

Comment by MattRogish | Hacker News Reader

https://www.ReactiveOps.com | Sr Site Reliability Engineer (AWS/GKE Kubernetes) | Full-Time; 155-160k DoE; 0.01% equity | Remote, Right-to-work-in USA

ReactiveOps is a DevOps consulting and services company, focused on AWS/GKE. We setup, maintain, and operate Kubernetes clusters for our clients, setup CI/CD, migrate their apps into Kube, etc., in addition to day-to-day cloudOps works. We are in Slack with them and act like their "outsourced, in-house Ops team". Our goal is to exceed the capabilities and care of an in-house Ops organization. We are a completely distributed team of 16 highly motivated folks, and are 100% bootstrapped and profitable.

We're looking for AWS/GKE operators to join our growing team! You can see more details and how to apply here: http://pages.reactiveops.com/careers/site-reliability-engine...

View on HN

Just to make sure I understand, remote is available only for people who are in the US/have the right to work in the US?

Hi! Thank you for your question!

Due to $reasons, we can only accept applications from folks that currently possess a right to work in the United States (e.g. https://www.thebalance.com/how-to-get-a-permit-to-work-in-th...)

Thank you for answering. I'm not interested to work in the US at the moment. I just wanted to make sure the restriction exists as I understood it.

Time waste alert!

I spoke to you at length and then your cofounder at length. Then it turns out that you don't actually have any immediate need to fill the role but you "might" have a need in the next 30 to 90 days. I pretty much gathered that you basically subcontract.

I went through a very lengthy interview process with this company, and made it to the final stage. Had great conversations with everyone at every step and ultimately was turned away with no explanation whatsoever.

That being said, a lot of the folks I spoke with seemed pretty sharp. YMMV.

I don't think it had anything to do with you. If you notice they always say they're "hiring" on these threads. However they don't necessarily have any new "client" to subcontract out to someone. They don't seem to have any problem wasting people's time though.

Hi Michael,

Although we strive to hire everyone who reaches the final stages (it's super time consuming for everyone, you and the team!), ultimately we have to turn away people who are awesome but aren't a perfect fit (at our teeny-tiny size back in [time redacted] when you interviewed, we were even pickier than we are now; I wouldn't read too much into our decision to not move forward).

We've made a lot of changes in our process since you spoke with us and I hope we're more communicative - to the best of our ability - in our process. I wish you the best of luck in your future endeavors!

-- Matt

I would not suggest posting specific dates of when candidates were interviewing without a candidate's consent

Hi,

I'm sorry you felt your time was wasted; we do not aim to do that at any point in the process (it wastes our time, too! :D). We are a kubernetes consulting and DevOps-as-a-Service shop, and some amount of our demand's final materialization is unpredictable. We take pains to mention that in the beginning but, if we didn't, that's on us and I'll make sure we don't miss that again - thank you for bringing that to my attention.

I don't know your situation, but it's highly likely we had a significant influx of demand that suddenly softened, and we had to back-off on the hiring. Or, perhaps also likely, we hired someone that more closely matched the position and needed to pause the search (we have 3 people starting on Monday, Feb 5, for example; we've hit our quota of less experienced Kube experts and have re-focused on people with extensive cloud production kube experience).

As a profitable but bootstrapped firm that has (yet!) to lay off people due to underwork, we strongly bias against pre-emptive hiring.

I wish you the best of luck in your career, and if you are still looking, in your search.

-- Matt

>"I don't know your situation, but it's highly likely we had a significant influx of demand that suddenly softened, and we had to back-off on the hiring."

Except that I replied in response to a "who's hiring" thread and the interviews followed very close to my responding. So why would you even be posting that you are hiring if you had "demand that suddenly softened"?

Reply on news.ycombinator.com