Senior software engineer, eine Rolle, für die Altuon einstellt
Senior software engineer
The engineer who moves a ledger while the business keeps trading, and can prove on any given day that old and new agree.
The senior software engineer builds and migrates the core systems that everything else in an organisation depends on, while that organisation keeps operating. The role designs and implements the compatibility layers, the dual-running and the reconciliation that let a core be replaced one consumer at a time, writes the tests that specify what the system promises, and hands over a system the client's own team can run without us. It is an individual contributor role with a wide remit: the senior engineer owns components end to end, from the data model to the runbook, on engagements where a wrong step is visible to a regulator.
Auf diese Stelle bewerben
- Practice
- Software Engineering
- Region
- Alle Regionen
- Beschäftigung
- Full-time employment or a long-term engagement, by agreement.
- Standort
- Remote within Europe, the Middle East or North America, with travel to client sites in the engagement's region.
- Arbeitssprachen
- English; German, French or Arabic in addition where the engagement requires it.
Verantwortung
- 01Read the existing system as it is, not as its documentation describes it: the code, the schema, the batch jobs, the undocumented consumers and the people who know where it bends. Produce the dependency map the migration plan is built on, and keep it true as parts of it are found to be wrong.
- 02Build the compatibility layer that speaks the legacy system's existing contracts to every consumer while the implementation behind it changes. No consumer is asked to change before the new core is ready for it, and every cut-over has a rollback that has already been run in rehearsal.
- 03Design and run dual-running and reconciliation. The new core processes alongside the old, every record is compared every day, and each difference is explained or fixed until the count is zero and stays there. The reconciliation report is the document the client's auditor reads.
- 04Write the tests as the specification: contract tests from both sides of every integration, invariants written down and enforced, and a pipeline that refuses a change the tests do not accept. A behaviour without a test is not yet a behaviour we have promised.
- 05Build the integration layer, versioned APIs, event streams and adapters with contracts written down and enforced in the pipeline, so the teams that build on the core can move without asking us.
- 06Work inside the client's regulatory frame. Under HIPAA that means knowing which data is protected health information and designing the access control and audit trail the rule requires; under a financial supervisor's outsourcing expectations it means the client can demonstrate control over what we build and can exit from it. Design so the obligation is met by the architecture rather than by a policy document.
- 07Leave the client independent. Documentation written for the engineer who joins after we have gone, observability that shows what the system is doing in production, and a handover that ends with the client's team able to change the system and to say no to us.
Die ersten neunzig Tage
The first month is spent on one live migration, alongside the engagement's technical lead, reading the dependency map, the compatibility layer and the reconciliation reports before changing any of them. The aim is to learn why each cut-over was sequenced as it was, and to find the one that should be resequenced.
The second month is the first component owned end to end: a consumer moved onto the compatibility layer, or a reconciliation gap closed, designed, tested, rehearsed with its rollback and released under the engagement's gates, with the client's engineers involved from the design review. By its end the senior engineer is presenting the reconciliation position to the client's steering committee.
The third month is the first cut-over owned from plan to completion, with the technical lead in the room as a reviewer rather than the author. The rehearsal, the rollback, the reconciliation and the runbook are the senior engineer's own by the ninetieth day.
Was geprüft wird
- Migration judgement
- A design exercise on a realistic core replacement with named consumers, a regulator and no permitted downtime. We look for a sequence with a rehearsed way back at every step, not a target architecture with boxes.
- Reconciliation discipline
- A conversation about a migration where old and new disagreed and nobody noticed for a week. We want to hear how the difference would have been caught on the first day, and what you would have done with it.
- Engineering depth
- A review of code you have written and are proud of, and a review of code we have written that has a problem in it. Both conversations are about taste as much as correctness.
- Tests as specification
- A short exercise in writing the tests for a behaviour before the code exists. We look for tests a client's auditor could read as a promise.
- Regulatory literacy
- A discussion of what HIPAA or a financial supervisor's outsourcing expectations would require of a specific design. Knowing the obligation matters more than citing the section.
- Clarity under scrutiny
- Explaining a cut-over plan to a non-engineer who is allowed to interrupt. A chief operating officer will do this to you; we do it first.
Worauf wir achten
- Years of building and operating systems of record in production, including at least one migration carried out while the business kept trading and at least one you had to roll back.
- Depth in at least one mainstream, well-supported stack and enough breadth to read a legacy codebase written in another; the role reads more code than it writes in its first weeks.
- A habit of writing things down: tests, runbooks, decision records and the documentation a successor would actually use.
- Evidence of leaving a client or a team independent of you, and of being pleased about it.
- Comfort with the client's room. The role presents to heads of operations, auditors and the steering committee, and is judged by how well the plan survives their questions.
- Working English; German, French or Arabic in addition is valued in the regions where the firm works.
Offene Stellen
Für dieses Profil ist derzeit keine Stelle ausgeschrieben. Bewerbungen darauf werden das ganze Jahr gelesen.
We hire against these profiles as engagements require. Applications are read year-round.