Hacker News Reader

Comment by LrnByTeach | Hacker News Reader

> Interview Process:

It is nice to see interview process spelled out in exact steps, it speaks for company clarity culture and it will unwind cognitive load on the candidate ..

Google docs job desc is nice add-on to give job details instead of all pasting in job post

View on HN

It's also telling that a mid-level Engineering role makes you step through this many hoops for $80K/yr. Or that the refer to that as "market rate".

While also slipping "on-call support" in there too

For what it's worth: The on-call support role is a 1-week obligation that rotates between all of the engineers on the team. As our sixth engineer, each engineer would only be on-call once every 6 weeks.

The role itself consist of being the:

- primary PagerDuty contact for server and application alerts and errors,

- primary contact for our dedicated support team to ask questions and triage new issues,

- primary code reviewer

Note that we do have a dedicated support team that answers emails and calls from our customer base. The on-call engineer is not responsible for that.

They say "market-based". It sounds like $80K in Indianapolis or the equivalent in your city.

$80k/yr is market for a starter mid-level position in Indianapolis. However, most of the city's talent is C# and JavaScript.

ETA: that's probably the most rigorous interview process I've seen in Indy and seems a bit extra for anything other than a lead.

For us, $80k is regarded as the entry-level starting base. A mid-level that makes it through our process has a much higher starting base.

Reply on news.ycombinator.com