At Anaplan we have an enormously powerful platform that enables users to collaboratively build models of their businesses. From budgeting and forecasting to supply planning and strategic policy management, the range of problems to which the Anaplan platform provides a connected planning solution is large and always growing.  As you might expect, at the core of this platform is a complex, conceptual model. When we make changes to our software, we need to be sure that we understand the impact of those changes and be able to verify that the changes made to the code match the changes we conceived in our conceptual model.

In software engineering generally, this sort of understanding and verification is often achieved using automated tests, but the sheer range and complexity of potential models that can be built with the Anaplan platform mean that this form of testing is not sufficient. To enable us to go beyond the standard testing paradigm, we produce a mathematical description of our conceptual model and use techniques known as formal methods to rigorously validate our requirements and verify our code. This role will require you to be in our York office a minimum of 2 days a week. 

Your Impact

You will join the team that is responsible for both creating this mathematical description, aka the specification, and creating the tools that leverage it to give the highest degree of confidence in the software we release. As such, you will have the opportunity to become involved in the deep analysis and mathematical modelling required to enhance the specification, and also the engineering work need to continue the development of our open-source frameworks.

• Identify and exemplify a list of distinct, unambiguous behaviours that describe a feature.
• Construct Acceptance Criteria scenarios to rigorously validate the behavioural requirements.
• Model the behaviours mathematically using a formal specification language.
• Guide and extend our frameworks to generate scenarios that mimic likely user behaviour.
• Use these scenarios to verify that the implementation satisfies the specification.
• Optimise balance between redundancy and coverage in scenarios.
• Identify means to increase confidence in quality yet maintain costs.

More About You

This is not a standard engineering job; you need to fully understand the system you’re building and the system you’re verifying. It’s necessary to be able to intelligently use the specification to drive the verification process and the focus will be as much on designing the frameworks as coding them. 

We’re looking for is someone with the enthusiasm and skills to imaginatively tackle the tasks described above. Some experience in any of the below will stand you in good stead....

• JVM languages—Kotlin, Java, Groovy 
• Functional programming paradigms and principles
• Set theory, predicate logic, and formal specification/verification
• Property-based testing
• Functional coverage analysis
• Related engineering tools—GitHub, Gradle, Artifactory, etc.