PacerPro · Jul 12th 2017
An explanation of the job title and a full job description can be found here:
I'm looking for my next "senior" engineer. (I'd like to hire a pair, but, you know, budget.)
> "What makes for an interesting candidate?"
It's not a degree, or n years of experience. PacerPro's founders are practicing lawyers. They know their stuff. I probably have the fewest number of degrees compared to everyone else in the company. I'm looking at the following qualities: You understand our business, or, if you don't, you have a genuine curiosity and ability to learn it. You are able to have conversations with our customers and stakeholders. You know how to research a problem. You know when to ask for help. You can think beyond the current story and consider ROI. You've shipped a real product before that you can show me. You have hands-on experience with our technology stack. I hear that "full stack" has become a dirty word, but we all do pretty much everything around here. Expect to handle Zendesk tickets from lawyers about one day out of the week. I'm not expecting you to be an expert in everything, but competence or the ability to spin up without too much inertia is a requirement. You are an eternal student and teacher. You want to bring us all to the next level, as do we for you. You want to work using our methodologies. We are an Agile shop in a mostly XP style; we have a daily stand-up (and evening round-up), pair-programming is our default stance; we need a good reason not to pair. Test-Driven-Development is how we grow code. Clear, understandable code is more valuable than clever tricks. We do code reviews on pull requests. Our backlog is in Pivotal Tracker, groomed by myself and the product manager, Arthur Law. We have automated continuous integration tests. We have continuous code quality testing. We can deploy at any time with one command line: rake production deploy.