Principal Software Engineer

Shepherds platform-wide strategies, including naming, protocol standards, and design patterns, to ensure ongoing value creationEffective Communication: Communicates complex technical concepts effectively in both written and spoken forms, catering to both technical and non-technical audiences. Collaborates with stakeholders to build consensus when necessary, ensuring alignment on architectural decisionsOpportunity to be a part of a startup that is revolutionizing the legal industryBenefitsStart-up cultureOpen PTOGrowth opportunitiesMedical, dental, and vision, 401(k)Experience with high volume distributed technical architectures with a high cost of failure, i.e. focus on reliability and availabilityExperience with design, implementation, and operation of data-intensive, distributed systemsAbility to design and communicate external and internal architectural perspectives of well-encapsulated systems (e.g. Service Oriented Architecture, Docker-based Services, micro-services) using patterns and tools such as Architecture/Design Patterns and Sequence DiagramsPossesses an understanding of how to design and develop from a security perspectiveKnowledge of API / Data Model Design and Implementation, including how to scale out, make highly available, or map to storage systems15+ years of relevant experienceSkilled using Continuous Integration and Continuous Deployment (CI/CD) with an emphasis on automation tools like Terraform, Jenkins, CodePipelineExperience with leveraging common infrastructure services like Enterprise Message Bus platforms, configuration services, Toggle management systems, and observability systems like Logging and Distributing Tracing SystemsExperience with some amount of ‘Big Data’ technologies such as: ElasticSearch, NoSQL Stores, Kafka, Columnar Databases, DataFlow or Pipeline Systems, Graph DataStoresKnowledge about algorithm development for intensive pipeline processing systemsExperience with Domain Driven Design concepts and practices such as bounded contexts, event storming, specification by example, etcSkilled with designing and operating software in a Cloud Provider such as AWS, Azure, or GCPKnowledge of multiple software stacksPossesses an understanding of how to identify, select, and extend 3rd party components (Commercial or Open Source) that provide operational leverage but do not constrain product and engineering creativityThis role is based out of our London officeExperience designing, modifying, and operating multi-tenant systemsExperience using feature or release toggles as a code branching strategy #J-18808-Ljbffr