Software Engineer, Kairos Aerospace

• Significant Python experience
• The ability to learn quickly in a self-guided manner - much of what we do is solving new problems by integrating one or more pieces of new technology
• An intimate understanding of at least one of our primary domains - cloud data processing, machine learning, statistical signal analysis, GIS analysis and processing, DevOps / systems engineering, scientific data visualization, software engineering, and release / build engineering
• A desire to solve real-world problems over working on technical problems in isolation - none of our work fits in neat boxes. Instead, we have a team that is focused on the impact our work can have on the future of life on the planet and prioritizes real-world progress over problem-focus purity
• A belief in modern development practices - we do things like code reviews, unit testing, minimal-viable products, and fast development iteration. We eschew the zealous practice of any development-process religion, but we do pick and choose techniques that help us write better software

Desirable

• Everything that Insight M does is driven by software, from recording sensor data while flying at 3000', to ephemeral high-scale cloud-native data processing, to computer-aided GIS analysis, to using machine-learning to extract structured information from geopixels
• The software engineering team is involved in every step of our process, building the automation that allows Insight M to not only image things that humans have never seen before but to do it reliably, repeatably, inexpensively, and quickly. (Yes, you can have all four)
• We work primarily in Python, with a smattering of Bash, SQL, Terraform, and Typescript when it makes sense
• We work on single-board-computers, field laptops, in virtualized cloud environments, in containers, inside of web browsers, and even inside lab automation frameworks
• We practice compositional engineering, tying together disparate pieces of technology to create novel artifacts that solve real-world problems
• We practice continuous integration and deployment, automated testing, and have a lovely monorepo
• We expect something approximating a 40-hour workweek, but mostly we just care that your work gets done. No, really. (Full disclosure: we occasionally put in some extra hours during crunch periods, but that is the exception, not the norm)
• We do not track vacation time, nor do we have set hours to be in the office. Instead, we encourage taking real vacations, mental health days, leaving early to pick up the kids, working from home, time-shifting commutes, staying home when you're sick, ducking out to the gym - we believe work time should be flexible