mirror-github-bspeice/speice.io
1
0
Fork 0
mirror of https://github.com/bspeice/speice.io synced 2025-11-03 18:10:32 -05:00
Code Issues Releases Wiki Activity

2018-12-04-what-small-business-really-means

Browse Source
This commit is contained in:
Bradlee Speice
2024-11-09 17:08:29 -05:00
parent 5c212fb3b3
commit 7580df1dd4
2 changed files with 70 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
blog/2018-12-04-what-small-business-really-means/_article.md Normal file
View File

@ -0,0 +1,34 @@
---
layout: post
title: 'More "What Companies Really Mean"'
description: 'when they ask "Why should we hire you?"'
category:
tags: []
---
I recently stumbled across a phenomenal small article entitled
[What Startups Really Mean By "Why Should We Hire You?"](https://angel.co/blog/what-startups-really-mean-by-why-should-we-hire-you).
Having been interviewed by smaller companies (though not exactly startups), the questions and
subtexts are the same. There's often a question behind the question that you're actually trying to
answer, and I wish I spotted the nuance earlier in my career.
Let me also make note of one more question/euphemism I've come across:
# How do you feel about Production Support?
**Translation**: _We're a fairly small team, and when things break on an evening/weekend/Christmas
Day, can we call on you to be there?_
I've met decidedly few people in my life who truly enjoy the "ops" side of "devops". They're
incredibly good at taking an impossible problem, pre-existing knowledge of arcane arts, and turning
that into a functioning system at the end. And if they all left for lunch, we probably wouldn't make
it out the door before the zombie apocalypse.
Larger organizations (in my experience, 500+ person organizations) have the luxury of hiring people
who either enjoy that, or play along nicely enough that our systems keep working.
Small teams have no such luck. If you're interviewing at a small company, especially as a "data
scientist" or other somesuch position, be aware that systems can and do spontaneously combust at the
most inopportune moments.
**Terrible-but-popular answers include**: _It's a part of the job, and I'm happy to contribute._

36
blog/2018-12-04-what-small-business-really-means/index.mdx Normal file
View File

@ -0,0 +1,36 @@
---
slug: 2018/12/what-small-business-really-means
title: More "what companies really mean"
date: 2018-12-04 12:00:00
authors: [bspeice]
tags: []
---
I recently stumbled across a phenomenal small article entitled
[What Startups Really Mean By "Why Should We Hire You?"](https://angel.co/blog/what-startups-really-mean-by-why-should-we-hire-you).
Having been interviewed by smaller companies (though not exactly startups), the questions and
subtexts are the same. There's often a question behind the question that you're actually trying to
answer, and I wish I spotted the nuance earlier in my career.
Let me also make note of one more question/euphemism I've come across:
<!-- truncate -->
## How do you feel about production support?
**Translation**: _We're a fairly small team, and when things break on an evening/weekend/Christmas
Day, can we call on you to be there?_
I've met decidedly few people in my life who truly enjoy the "ops" side of "devops". They're
incredibly good at taking an impossible problem, pre-existing knowledge of arcane arts, and turning
that into a functioning system at the end. And if they all left for lunch, we probably wouldn't make
it out the door before the zombie apocalypse.
Larger organizations (in my experience, 500+ person organizations) have the luxury of hiring people
who either enjoy that, or play along nicely enough that our systems keep working.
Small teams have no such luck. If you're interviewing at a small company, especially as a "data
scientist" or other somesuch position, be aware that systems can and do spontaneously combust at the
most inopportune moments.
**Terrible-but-popular answers include**: _It's a part of the job, and I'm happy to contribute._