Senior Software Engineer (Backend)

VenueBook is revolutionizing the way people think about event booking. Our platform lets venues and bookers plan together, creating a smarter and better-connected experience for all. We simplify planning, so you can have more fun!

Have you been multitasking playing TwoDots, saving kittens and writing your own robot-controlling apps in your spare time, just to stave off boredom? Sounds like you’re ready for a challenge that impacts product and meaningfully puts you on the ground level of a great business. If so, we’d like to meet you. VenueBook is a rapidly growing start-up rolling out new products and tech at all times. Our team is thoughtful and bad*ss, because that’s what it takes to get the job done.

• Working on different features that combine multiple technologies in our stack, writing production quality code in Python, SQL
• (and perhaps some JavaScript- it’s inevitable these days)
• Involvement in the entire software lifecycle, from inception and architecture, to implementation, testing, and of course, continued maintenance
• Helping to collaborate on some of our toughest technical challenges: you'll be at the center of our scale-out
• Reviewing code to help ensure our codebase retains its production quality

What we are looking for:

• 4+ years working with Python and a Python web framework (e.g. Django, Flask, Tornado) OR
• 7+ years working with a common backend Web language (e.g. Ruby) and a web framework in that language (e.g. Rails)
• Familiarity with software collaboration tools (e.g. git) and working in a Unix-based environment
• Ability to grapple with the complexity of the challenge at hand, no matter how small or big it may be
• Have been a mentor to others and want to help elevate the team’s ability to solve problems
• Enjoy being in a hard working environment with a very social, fun-loving team!

What will set you apart:

• Understanding data types and different representations of data and the strengths and weaknesses of all of them
• Knowing the nuances of a modern web technology stack and why certain development decisions are made
• A healthy respect for the power and availability of data
• Methodical evaluation of when to build versus when to use someone else’s library
• The difference between strategic and tactical solutions to a problem, and what situations to apply each
• A strong process for evaluating when something is ready for production
• A love of learning, growing, and becoming better every day

How we get it done:

• We keep our data in PostgreSQL (9.4)
• Most of our server applications are written in Python (2.7)
• Our main framework is Django
• We have some micro-Django / Flask apps hanging out
• We have a lot of JavaScript
• We love React - thank you Team Facebook!
• jQuery, Backbone, gulp, and Browserify help us out a lot too
• Our team is pretty Sass-y (or SCSS-y)
• We cache with Redis (3.0)
• We deliver our content with nginx (1.8)
• We love Ubuntu 12.04 and 14.04

Do not apply if:

• You think the “relational model” of data doesn't work in modern times
• Everything should be written in JavaScript because it's the one language that works in your web browser
• Testing your code isn't important – that’s what real users are for
• You like to use the newest technology out there “just because”
• You won’t even evaluate the newest technology out there