Legacy Technology · Hire specialists
Hire Pro*C developers who can work on your code from week one
Pro*C still runs batch, billing and claims systems across banking, insurance, healthcare and retail. The developers who know it well are hard to find. We find them, test them on your kind of code, and keep a backup briefed.
- UK contract with Dreams Technologies Hub Private Limited (VAT registered)
- Engineers delivered from our own Coimbatore office, India
- Shortlist within 5 working days
- Building software since 2013
Where Pro*C work comes from
Pro*C embeds SQL in C programs that talk to Oracle. It was the standard way to build high-volume batch and transaction code on Unix from the 1990s onwards, and much of that code is still in production. We see Pro*C requests in:
- Banking and pensions batch: interest runs, statements, payments files.
- Insurance and benefits administration: policy, claims and member processing.
- Healthcare claims and eligibility platforms.
- Retail point-of-sale back-ends and stock systems.
- Telecom billing, rating and mediation.
- Life-sciences and laboratory systems on Oracle.
What our Pro*C developers do
- Fix production defects and batch failures, including core dumps and ORA- errors.
- Add features and regulatory changes to existing Pro*C programs.
- Tune slow jobs: array fetches and inserts, bind variables, cursor handling.
- Upgrade Oracle client versions and rebuild with new precompiler settings.
- Port Pro*C from AIX, HP-UX or Solaris to Linux.
- Document undocumented code and build regression tests around it.
Profiles we supply
| Profile | Experience | Typical work |
|---|---|---|
| Pro*C developer | 5–8 years | Defect fixes, enhancements, batch support |
| Senior Pro*C and PL/SQL engineer | 8–15 years | Performance tuning, design changes, Oracle upgrades |
| Pro*C and Tuxedo engineer | 8+ years | Transaction services in C/Pro*C under Oracle Tuxedo |
| Legacy technical lead | 12+ years | Code recovery, documentation, migration planning, leading a small team |
What we test in the technical interview
Every candidate is interviewed by one of our own senior engineers. We test the exact things your system depends on:
- Host and indicator variables, VARCHAR handling and NULLs.
- Cursors, array fetch and array insert, and when to use each.
- Dynamic SQL methods 1 to 4.
- Error handling with SQLCA, WHENEVER and ORACA.
- Precompiler options such as MODE, CODE, PARSE and SQLCHECK, and makefiles that call proc.
- Debugging core dumps with gdb or dbx on your Unix flavour.
- PL/SQL, Korn or Bash shell, and your scheduler.
Three ways to work with us
Dedicated specialist
A named engineer joins your team on a monthly time-and-materials basis. Best when you have live systems, an urgent gap and your own technical lead.
See support podsFixed-scope assessment
Two to three weeks, fixed fee. We map the code, the platform and the people risk, then give you options with effort ranges. Best when nobody fully understands the system any more.
See the assessmentMigration project
Fixed price once the assessment is done. We port, test, run in parallel and cut over. Best when you have decided to leave the platform.
See migrationsRelated services
Why teams come to us for scarce skills
Finding thin talent pools is our core skill
Large service firms rarely staff a single Pro*C or HP-UX role quickly. We keep a vetted network of engineers who have these skills and want this work.
Screened by people who have done the work
Our own senior engineers run the technical interview. Candidates are tested on the platform you run, not on general programming.
UK contract, India delivery
You contract with our UK company. The work is delivered from our own office in Coimbatore with working hours that overlap the UK day.
AI-assisted code understanding
Our team works with Claude Code to read, document and test old codebases faster. Every finding is checked by an engineer before it reaches you.
Continuity built in
Every engagement keeps a runbook and code notes from week one, and a second engineer is briefed on your system. Losing one person does not mean losing the knowledge.
We also run the migration
When you are ready to leave the platform, the same team that kept it running plans and delivers the move.
Tell us what you’re running
Send us the stack and the problem. We’ll reply within one working day and, if it’s a staffing request, send a shortlist within five.
FAQ
Frequently asked questions
How quickly can you provide a Pro*C developer?
We aim to send a shortlist within five working days of a clear brief. Start dates depend on notice periods, typically two to three weeks after you choose.
Do your developers also know Pro*COBOL?
Some do. Tell us if your estate mixes Pro*C and Pro*COBOL and we will screen for both.
Which Oracle versions do you cover?
From older 9i and 10g client code through to 19c. We regularly help clients upgrade the client libraries their Pro*C programs link against.
Our Pro*C code has no documentation. Can you still help?
Yes. That is the usual situation. Our engineers read the code, write plain-English notes and build tests around the critical paths, using AI tools to speed up the reading.
Should we rewrite Pro*C in Java or Python?
Sometimes, but often not. Well-written Pro*C is fast and stable. Our assessment compares keeping, upgrading, porting and rewriting, with effort and risk for each.