Engineering at WeaveGrid
The engineers at WeaveGrid have experience working in a wide variety of technical organizations – some excellent, some less so, but all of them contributing lessons for us as we create the norms, culture, and practices here. We have all come to understand that great software comes from software engineering teams whose members have developed good working relationships, who trust and respect each other, and who have the cultural and managerial support they need to be sustainably productive. Put simply, our vision is to create a technical organization at WeaveGrid that compares favorably with with the best software operations in tech.
Because we focus on building complete and well-rounded engineering teams, we have the opportunity to approach job descriptions a little bit differently. Using a college metaphor, we don't just care about your major, but also your elective classes and extracurriculars. And we understand that sometimes the hardest-won part of your past experience doesn't fit neatly into a job application or resumé.
Great software comes from software engineering teams that work well together, trust and respect each other, and that have the support they need to be sustainably productive. Even though we are an early stage company, operating in a sector not always lauded for its excellence in this area, we are committed to building and scaling a technical organization at WeaveGrid that compares favorably with with the best software operations in tech.
When you look at the application form below, you'll see that it asks you to describe yourself a little differently than you may be used to. Rest assured that there are no wrong answers for the multiple choice questions – while our needs may be more urgent in some areas than others, all of the options are relevant to our needs.
We're looking for engineers with the following technical focus areas:
- Distributed systems built with cloud-native architectural principles - job and message queues, decoupled services, load balancing, observability, reliability
- Database design, implementation, and optimization, definitely with SQL engines but also using NoSQL stores when appropriate
- Python-centric backend development, including familiarity with the Python3 standard library and common open-source packages
- Data science engineering using the pydata ecosystem, including experience (or, at the least, a strong desire to learn about) deploying and maintaining systems in production