Jules Elm — fictional resume
Entirely fictional source for reviewing a career pack. London. Updated March 2026.
Employment
Head of Engineering at Fictional Fieldwork Ltd, July 2022 to present. Leads a group of 18 engineers through three engineering managers; partners with product and operations. London.
Staff Engineer at Fictional Fieldwork Ltd, January 2018 to June 2022. Supported several product teams without line-management responsibility.
Senior Software Engineer at Fictional North Quay Systems, July 2014 to December 2017. Worked on service operations and shared platform tools.
Software Engineer at Fictional Civic Atlas, September 2010 to June 2014. Built data-import tools with a service-delivery team.
Education
BSc in Computer Science, Fictional Eastbank University, September 2006 to June 2010. No grade supplied.
Selected work
2012-04: Import failures were discovered after staff had started processing records. Make failures visible before processing and leave a recovery path for operators. Built validation checks and a rejected-record queue with the service-delivery team. Operators used the checks across 18 recurring data feeds.
2013-09: Routine recovery depended on an engineer remembering undocumented steps. Help the operations team own routine recovery safely. Paired with operators to write recovery runbooks and rehearse failure cases. Operations maintained the runbooks and performed routine recovery; no response-time baseline was recorded.
2016-03: Service teams could not distinguish a quiet queue from a stalled consumer. Expose queue age and ownership without replacing the messaging platform. Designed a queue-age dashboard and paired with service owners to set alert thresholds. Five services adopted the dashboard and ownership alerts.
2017-10: Teams had recovery instructions but had not practised making decisions together. Help service owners and support staff rehearse escalation decisions. Facilitated four incident exercises with service owners and support staff. The group clarified escalation owners and recorded gaps in recovery instructions; outage reduction was not measured.
In March 2019 I designed a deployment rehearsal format and co-built its runner with engineers. Two teams adopted rehearsals before deployment.
2021-02: Product and operations disagreed about replacing a shared service in one release. Make the migration tradeoffs explicit and agree a sequence the teams could support. Mapped failure boundaries with both groups and authored a staged separation proposal. The teams chose a staged separation and retained a rollback path; product teams implemented the changes.
2023-05: Four product teams requested different platform improvements from the same small group. Agree priorities and ownership within the available engineering capacity. Worked with engineering managers and product leads to compare support burden and migration effort. The group agreed a two-quarter platform adoption plan and named an owner for each migration; revenue impact was not measured.
2024-11: A supplier arrangement needed a confidential technical review. Give procurement a technical assessment without disclosing internal contract details. Coordinated engineering and procurement input and wrote the technical tradeoff assessment. Procurement used the assessment in its supplier review; commercial terms and the final decision remain private.
In February 2025 I hired and coached engineers while introducing peer design reviews. The engineering group adopted peer design reviews.
March 2016: built a service health dashboard adopted by five services.