Senior Software Engineer

Date - JobBoardly X Webflow Template
Posted on:
 
July 31, 2025

Job description

About the Role

As a Senior Software Engineer at Factor House - you’ll get to work across our two main products - Kpow and Flex whilst also playing a key role in building new products to add to our product tool belt.

This role will require you to go deep into the weeds where you’ll help build and improve the systems behind our real-time data tools. You’ll work closely with the team to design features that solve real problems, help shape how we plan and release, and talk directly to customers to understand what they need. Most of your work will be in Clojure, but what matters most is how you approach problems rather than which language you use.

Responsibilities

Who we’re looking for

  • Worked directly on a core product, owning features from idea to release
  • You’ve built backend systems in Clojure and are familiar with the JVM, Jetty12, Quartz, AWS SDK, and Kafka/Flink client libraries
  • Experience with with ClojureScript and React 19, and you’re comfortable with re-frame or similar tools for managing state (like Redux or Zustand)
  • You know your way around the JavaScript/React ecosystem and have used tools like StorybookJS, xyflow, and TailwindCSS
  • Experience with modern infrastructure tools such as AWS, MSK, Glue schema registry, ECR, ECS, EKS, and Fargate, and are confident with Docker (Kubernetes and Helm charts are a nice to have but not required!)
  • You’ve spent time and have a keen interest with data streaming solutions such as Kafka, Kafka Streams, Kafka Connect, ksqlDB, Flink, Iceberg
  • Familiarity with serialisation formats like Avro and Protobuf

Job requirements

What you’ll be doing

  • Collaborating closely with your team to shape new features or improvements that tackle real problems for Factor House customers
  • Help shape and improve how we plan, test, and roll out releases
  • Getting your hands dirty by designing and building features that balance speed and quality. Shipping fast matters, but it still needs to solve the problem
  • Taking ownership of key parts of our stack. Maintaining what’s already there while exploring smarter, cleaner, or more scalable ways to solve new challenges
  • Giving clear, thoughtful feedback on pull requests or taking the time to respond to feedback on your own code
  • Jumping on calls with customers understand their pain points and making their problems your own, so you can design thoughtful solutions that delight engineers
  • Influencing product and design decisions about our products
  • Pairing with other engineers to work through complex problems, sharing your knowledge across the stack, and leaning on each other to get great solutions over the lineme