CloudFrame builds Continuum, the markets most capable deterministic COBOL-to-Java transformation platform, with guaranteed functional equivalence between the original COBOL and the generated Java.
What is less well known is how it works. Continuum has never transformed COBOL to Java in a single step. Under the covers it has always gone COBOL to optimized COBOL first, and then pattern-to-pattern into Java. That intermediate optimization stage has been running quietly inside every transformation we have delivered.
We are now opening that stage up to customers directly. Optimize in Place gives a customer access to the optimized COBOL itself a low-risk automation path that improves the performance and efficiency of their existing COBOL, on their existing mainframe, without a platform change and without a rewrite. Continuum also generates full documentation of the program and the changes applied. This is a mature component being surfaced, not a recent product being invented. Our job now is to harden it for direct customer exposure.
2. The engagement
We need an experienced COBOL developer to build the test workloads we do not currently have. You will write deliberately inefficient COBOL the kind that genuinely exists in production at banks and insurers run it through Optimize, and tell us honestly whether the optimized COBOL that comes back is correct, measurably faster, and something a customers own development team would accept into their codebase.
You will validate the platforms generated documentation and its synthetic test data generation to the same standard. All three capabilities are linked: generated test data is what proves an optimization is equivalent, and the documentation is what gets the rewrite through a customers code review.
You are not being hired to demonstrate that the product works. You are being hired to find out where it doesnt, on our schedule and in our lab, rather than in a customers batch window.