The position and its scientific scope
What the advert asks for, where the project came from, why a laboratory in Jerusalem is attached to it, and what the group means by the two different candidate profiles it describes.
1.1 · The posting, factually
| Item | Detail |
|---|---|
| Title | PhD Student — DNA Break Signature in Cancers |
| Reference | Kennziffer 2026-0211 |
| Research programme | Functional and Structural Genomics |
| Group | Junior Research Group “Brain Mosaicism and Tumorigenesis”, headed by Dr. Pei-Chi Wei |
| Partner laboratory | Aqeilan Lab, Hebrew University of Jerusalem |
| Stated goal | Map replication-stress-mediated and naturally occurring double-strand breaks in cancer cells at nucleotide resolution |
| Model systems | Osteosarcoma, breast cancer and leukaemia cell lines, compared against in vivo tumour models |
| Methods named | LAM-HTGTS, Hi-RepliSeq, GRO-seq, DRIP-seq, next-generation sequencing, multi-omics integration, statistical modelling, generation of engineered cancer cell lines |
| Degree required | Master's (or soon-to-be-completed master's) in biology, bioinformatics or a related field — the advert names genetics, genomics, bioengineering and applied mathematics |
| Language | Fluent spoken and written English. No test score is specified. |
| Contract | Full-time, fixed term three years, extension possible |
| Deadline | 28 October 2026 |
| Documents | CV, cover letter, academic transcripts, contact details for two referees — through the portal only; email and postal applications are not accepted |
| Named contact | Dr. Pei-Chi Wei, telephone +49 6221 42-3251 |
It is a direct group recruitment, not the structured graduate programme. This post is advertised on the DKFZ jobs portal by the group itself, with its own reference number, its own deadline and the group leader's telephone number printed on it. The requirements list asks for fluent English and does not state a minimum TOEFL or IELTS score. That is a different route with different gatekeeping from the central International PhD Program, and for many applicants it is the more accessible of the two.
The same project has been advertised before. A posting with reference 2026-0144, deadline 30 July 2026 and a September 2026 start carried essentially the same project description, the same four assays and the same partner laboratory. This is the position re-advertised. A re-advertised post means the group has not yet found the person it wants — which makes a precisely targeted application worth more here than it would be against a fresh, crowded call.
1.2 · What the project is really about
Strip the advert down and one sentence remains: cancer genomes are rearranged in recurring patterns, and this project asks why those rearrangements happen in those particular places.
The conventional answer has been selection — a rearrangement persists because it helped the tumour grow. That is certainly part of the story, but it cannot be the whole of it, because some positions break far more often than chance allows even before any selection has had a chance to act. Something about those positions makes the DNA physically fragile.
The group's answer is that fragility is produced by traffic. A chromosome is read by two different machines that both travel along it: the replication machinery copying the DNA, and the transcription machinery copying genes into RNA. Where those two machines meet head-on, the DNA is at risk. Where they travel in the same direction, it is much safer. Break positions are therefore predictable from the local geometry of replication and transcription — and if they are predictable, they are also potentially druggable.
Picture a single-track railway line. Two kinds of train run on it: a slow, very long goods train (transcription of a long gene — this can take many hours) and a fast scheduled service (the replication fork).
If the fast train comes up behind the goods train and follows it in the same direction, the two can share the track with some delay and little drama. If the fast train comes around the bend towards it, they are on the same track facing each other, and something has to give.
The group's published finding is that DNA breaks accumulate at the places where this second situation is geometrically unavoidable — and that you can predict those places by measuring, separately, which way the replication forks run and which way the genes are transcribed. Your PhD would be measuring both, in cancer cells, and then testing whether the predicted collision sites are where the cancer genome actually breaks.
1.3 · Where the project came from
This is not a speculative proposal. It is the next step in a decade-long line of work, and knowing that line is the single most useful piece of interview preparation available to you.
| Year · venue | What it established | Why it matters for this project |
|---|---|---|
| 2016 · Cell | Long neural genes contain recurrent DNA break clusters (RDCs) in neural stem and progenitor cells. | The founding observation: breakage is not random, and the genes affected are long, transcribed and late-replicating. |
| 2020 · PNAS | RDC genes can be induced in neural progenitors differentiated from embryonic stem cells in culture. | Made the phenomenon tractable in a dish rather than only in embryos — the methodological move this project repeats for cancer lines. |
| 2024 · Nature Communications | The linear interaction between replication and transcription shapes break dynamics at RDCs. 152 RDCs defined and classified; breaks shift towards head-on orientation under replication stress. | The core framework. This paper is where the four assays and the head-on/co-directional statistic come from. Read it first and read it twice. |
| 2024 · Nature | Strand-resolved mutagenicity of DNA damage and repair (as co-author). | Establishes the group's involvement in strand-aware mutation analysis — the same logic applied to point mutations rather than breaks. |
| 2026 · Nature Communications | RDCs drive replication-stress-induced copy-number variants and genome diversification. Polymerase theta is required for the recurrent focal events. | Closes the loop from break to permanent structural change — the mechanistic bridge this project needs in order to talk about cancer genomes at all. |
| 2026 · bioRxiv | A genome-wide resource describing the replication environments of DNA breakage in human cancer cell lines. | The direct precursor. The human-cancer extension has already begun; the PhD would build on it. Find and read this preprint. |
What an RDC actually is
A recurrent DNA break cluster is a genomic interval, typically tens to hundreds of kilobases wide, in which independent cells repeatedly sustain double-strand breaks. They are found inside long, actively transcribed genes that replicate late.
Three features define the vulnerable locus, and all three are measurable:
- Length. The gene is so long that transcribing it once takes longer than the cell cycle allows, so transcription and replication are necessarily simultaneous.
- Late and slow replication. These regions are copied at the end of S phase and are poor in replication origins, so a small number of forks must travel a long way — and a fork that must travel far has more opportunity to meet trouble.
- Transcription that cannot be switched off. Deleting the promoter of an RDC gene abolishes the breaks. In the group's 2026 work, removing the promoter or enhancer of Ctnna2 or Nrg3 eliminated both the nascent transcription and the RDC, without advancing replication timing — which is close to a formal demonstration that the transcription, not merely the lateness, is causal.
In the 2024 paper the 152 RDCs were sorted by the geometry of the forks that converge on them: 87 were inward-moving, of which 63 overlapped a replication-timing transition region; 15 unidirectional; 6 outward-moving; 12 complex; and 32 could not be assigned. That classification is the project's intellectual unit of analysis. When the advert says “map and classify DSBs”, this is the kind of classification it means.
1.4 · Why a laboratory in Jerusalem is on the advert
The Aqeilan laboratory works on WWOX, and WWOX is the reason the collaboration makes sense. It has a double identity that sits precisely on this project's axis.
First, WWOX is the gene that occupies the common fragile site FRA16D. It is long, late-replicating and famously prone to breakage and deletion across many tumour types — in other words, it is itself one of the things that breaks.
Second, WWOX is a participant in the response to breakage. Work from that laboratory reported that WWOX regulates ATM activation and the DNA damage response, and separately that it modulates the ATR-mediated checkpoint; a broader analysis argued that tumour suppressor genes located within common fragile sites are active players in the damage response rather than passive victims of it.
Third, and this is the part that explains the tumour types named in the advert, the same laboratory reported that WWOX promotes osteosarcoma development through upregulation of Myc — a result that complicates the simple tumour-suppressor reading and makes osteosarcoma a natural model for them.
WWOX is both a thing that breaks and part of the machinery that decides what happens when things break.
Dr. Wei's group brings the ability to map and explain where breaks occur. The Aqeilan laboratory brings a fragile-site gene that is also a damage-response regulator, plus osteosarcoma and breast cancer models in which it matters. Put together, you can ask a question neither group could ask alone: does altering a damage-response regulator change the positions at which the genome breaks, and does that positional change explain the structural variants seen in those tumours?
If you are asked in interview why the two laboratories are working together, that is the answer.
1.5 · Why osteosarcoma, specifically
Osteosarcoma is an unusually good test case, and being able to say why signals that you understand the project rather than just its methods.
Osteosarcoma genomes are among the most structurally chaotic in human cancer. They carry very high numbers of structural variants, frequent chromothripsis, breakage-fusion-bridge cycles and complex amplifications, and comparatively few simple recurrent point-mutation drivers. For a project about break positions this is ideal: there is an enormous amount of rearrangement to explain, and relatively little of it can be explained by selection on individual favourable mutations.
It is also a predominantly adolescent and young-adult cancer with little therapeutic progress in decades, which is what makes the reverse-translational framing in the advert more than a formality.
Breast cancer provides the contrast: a far better characterised genome, well-described replication-stress biology, and established damage-response drug targets. Leukaemia provides a third, mechanistically distinct comparison, because lymphoid cells generate programmed breaks as part of normal development — which is, historically, the biology the LAM-HTGTS method was invented to study.
1.6 · The two candidate profiles
The advert describes two entry routes with different requirements, and it is worth reading carefully which column you are standing in, because it determines what you have to prove.
| Coming from biology | Coming from computation or mathematics | |
|---|---|---|
| Stated requirement | Master's in biology or a related field | Master's in bioinformatics, genetics, genomics, bioengineering or applied mathematics |
| The extra thing asked for | Intermediate R or Python, and prior experience analysing omics datasets — listed as advantageous | Good performance in university biology courses — listed as a requirement |
| What they are really worried about | That you will produce beautiful libraries and then need someone else to interpret them | That you will produce elegant statistics about a biological system you cannot reason about |
| What reassures them | Any analysis you did yourself, end to end, with code someone else could run | Evidence you can explain a mechanism, not just a method — and that you know what a control is for |
| The strongest position | Neither column alone. Someone who can run the analysis and argue about the biology is what a four-assay integration project actually needs, and that person is rare enough to be worth some flexibility on the degree title. | |
The advert lists the acceptable degree fields explicitly: biology, bioinformatics, genetics, genomics, bioengineering, applied mathematics. A pharmacy doctorate is not on that list, and an administrative first pass may simply not recognise it as a match — not through any judgement about you, but because the field name does not appear.
Two practical consequences. First, your transcript's recognition status matters: if your degree is formally rated as equivalent to a consecutive master's, that rating belongs in the application as a document, not as a claim in prose. Second, the advert prints the group leader's telephone number. That is an invitation, and a short, specific enquiry — whether a pharmacy doctorate with a computational thesis and demonstrable omics analysis would be considered eligible — is a legitimate use of it. The answer is genuinely useful either way, and asking a precise question is itself a signal about how you work.
Do not use that call to pitch yourself at length. Ask the eligibility question, listen, thank them. One minute.
This is worth being clear-eyed about, in both directions.
What genuinely transfers. The project's stated endpoint is reverse-translational therapy strategy, which means the final chapter of the thesis is pharmacology: ATR, CHK1, WEE1, PARP and polymerase theta inhibitors, their selectivity, their combination toxicity, their therapeutic windows. That is a vocabulary you already own and most molecular biology graduates do not. The group's own 2026 work used a polymerase theta inhibitor as its central mechanistic tool — a drug used as a scalpel. Someone who thinks naturally about dose, exposure, off-target activity and resistance is an asset in that chapter, not a passenger.
What does not transfer, and must be built. Three years of this project is sequencing-library work and interval arithmetic. No part of a pharmacy curriculum prepares you for a BED file, a mappability artefact or a permutation test on genomic regions. That gap is real, it is the thing the selection is screening for, and no cover letter sentence closes it. Only a piece of analysis you have actually done closes it — which is what Module 4 is for.
The honest framing. Not “my pharmacy degree is secretly perfect for this”. Rather: “I come from drug development, I have taught myself the genomics, here is an analysis I did on public break and replication-timing data, and here is why this project's final chapter is the one I most want to work on.” That is a defensible position. The alternative — hoping the field mismatch goes unnoticed — is not.
- The project's goal in one sentence, without using the word “multi-omics”. (§1.2)
- What a recurrent DNA break cluster is, and the three features that make a locus into one. (§1.3)
- Why deleting the promoter of an RDC gene abolishes its breaks, and what that experiment proves. (§1.3)
- Why the Aqeilan laboratory is on this project, in terms of WWOX's two roles. (§1.4)
- Why osteosarcoma is a better test case for this question than a genomically quiet tumour. (§1.5)
- Which of the two candidate columns you are applying in, and what you therefore have to demonstrate. (§1.6)
Terminology, built from the cell cycle up
Section 2.1 assumes no molecular biology at all. Sections 2.2 to 2.6 are the five concepts the posting names, in the order they build on each other. Nothing later in this guide uses a term that is not defined here.
2.1 · Level zero: the machinery that will later break
DNA is two strands wound together. Each strand runs in a direction, and the two run opposite to each other — written as 5′ to 3′ for one and 3′ to 5′ for the other. That sounds like pedantry and it is not: almost everything in this project is a question about direction, and direction only exists because the two strands are not interchangeable.
A cell that is going to divide passes through four stages, together called the cell cycle. In G1 it grows and prepares. In S phase it copies its entire DNA. In G2 it checks the work. In M phase it divides. Everything this project studies happens in S phase, or is a consequence of something that went wrong there.
How DNA is copied, and why that creates direction
The genome is far too long to copy from one end. Instead, copying starts at thousands of designated points called origins of replication. From each origin, copying proceeds in both directions at once, like a zip opening outwards from its middle. The moving point where the two strands are being separated and copied is a replication fork.
So at any moment in S phase, the genome contains thousands of forks, and each one is travelling either leftward or rightward along the chromosome coordinate. That left-or-right property is replication fork direction, and measuring it genome-wide is one of the four assays in Module 3.
Think of a long street being resurfaced. Work does not start at one end — crews start at many points along the street, and each crew works outward in both directions from where it started. Halfway between two crews, the two work fronts meet and the job is done there.
Origins are where the crews start. Forks are the moving work fronts. The place where two forks meet is a termination zone. And critically: whether the pavement outside your house is being resurfaced left-to-right or right-to-left depends entirely on which crew reaches you first.
Origins do not all fire at the same time. Some regions are copied in the first minutes of S phase and others at the very end — this is replication timing. Early regions tend to be gene-rich and chemically open; late regions tend to be gene-poor, tightly packed and attached to the nuclear envelope. Between an early region and a late region the timing slopes gradually across a wide interval called a timing transition region, or TTR. A TTR is typically crossed by a single fork travelling a long way with no origin to help it — which, as Figure 1 showed, is exactly where trouble concentrates.
How genes are read, and why that also creates direction
Transcription is the copying of one gene into RNA by the enzyme RNA polymerase. The polymerase uses one of the two DNA strands as its template, and which strand it uses determines which way along the chromosome it travels. A gene is therefore described as being on the plus strand or the minus strand, and that is its transcription direction.
Two directions now exist on the same piece of DNA: the direction the fork is travelling, and the direction the polymerase is travelling. The relationship between those two directions is the subject of this entire PhD.
What happens when DNA breaks, and the three ways cells fix it
A double-strand break (DSB) is both strands severed at the same place. It is the most dangerous form of DNA damage, because unlike a single-strand nick there is no intact strand left to use as a guide. Cells have three main ways of dealing with one, and which one acts determines what scar is left behind.
- Non-homologous end joining (NHEJ)
- The fast, always-available route: recognise the two ends, trim them, join them. Core components are Ku70/Ku80, DNA-PKcs, and the ligase complex LIG4–XRCC4–XLF. Usually accurate enough, but often gains or loses a few letters. Remember the name XRCC4 — it returns below in a way that explains the group's experimental design.
- Homologous recombination (HR)
- The accurate route: chew back one strand at each end, then use the intact sister copy of the chromosome as a template to rebuild what was lost. Needs MRE11–RAD50–NBS1 and CtIP for the initial chewing, RPA to coat the exposed single strand, and RAD51 to perform the search. It only works after the DNA has been copied, so it is restricted to S and G2 phase.
- Microhomology-mediated end joining (MMEJ, also alt-EJ or TMEJ)
- The improviser. It looks for a very short stretch of matching sequence — typically two to twenty letters — near both ends, lines those up, and joins, deleting whatever lay between. Its signature enzyme is DNA polymerase theta, encoded by
POLQ. The scar it leaves is characteristic: a deletion with a few letters of microhomology exactly at the junction. The group's 2026 work used a polymerase theta inhibitor and watched junctions shift away from roughly two base pairs of microhomology towards direct joining, which is how you demonstrate that this pathway was responsible.
The group's break-mapping experiments are frequently done in cells lacking both XRCC4 and p53. If you understand why, you understand how break mapping works.
Losing XRCC4 disables NHEJ. Breaks that would normally be sealed within minutes instead persist — which means there is time for them to be captured by the assay. Without this, most breaks are repaired before they can be detected, and the map is sparse.
But a cell full of unrepaired breaks normally activates p53 and kills itself. Losing p53 removes that response, so the cells survive long enough to be harvested.
So the genotype is not an accident of whatever line was lying around. It is a deliberate pair of modifications: one to make breaks persist, one to stop the cell dying of them. The corresponding caveat — and you should volunteer it before anyone asks — is that this is no longer a normal cell, so break frequencies measured in it are amplified relative to wild type, and anything concluded from it must be confirmed in wild-type cells. The 2026 paper does exactly that, and reports that polymerase theta inhibition behaves differently in the two backgrounds.
2.2 · Replication stress and replication–transcription conflicts
Replication stress is the slowing, stalling or collapse of replication forks. It is not one molecular event but a category, and its causes fall into four groups:
- Running out of materials — insufficient nucleotides to build new DNA, which is what happens when a cell is forced into S phase before it is ready.
- Obstacles on the track — chemical damage to the DNA, unusual secondary structures such as G-quadruplexes, tightly bound proteins, and RNA:DNA hybrids (§2.4).
- Too many origins firing, or too few — both are harmful. Excess firing exhausts the nucleotide supply and the pool of protective proteins; too few leaves long stretches dependent on a single distant fork.
- Topological strain — DNA is a twisted double helix, and any machine travelling along it generates over- and under-winding that must be released by topoisomerases.
A stalled fork exposes single-stranded DNA, which is coated by RPA, which recruits the kinase ATR, which activates CHK1. That signalling axis slows the cell cycle, suppresses further origin firing elsewhere and stabilises the fork. It is simultaneously the cell's defence against replication stress and — because cancer cells depend on it far more heavily than normal cells do — the most heavily drugged target in this field (§2.6).
If the fork cannot be rescued it may reverse, be cut, or simply be abandoned, leaving a region unreplicated as the cell enters mitosis. Unreplicated DNA pulled apart during division produces breaks, micronuclei and, over cycles, the large-scale rearrangements seen in tumour genomes.
Oncogene-induced replication stress
This is the reason the whole field exists. Activating an oncogene such as cyclin E (CCNE1) or MYC pushes cells into S phase early and fires too many origins at once. Nucleotide pools are exhausted, forks slow, and breaks accumulate — in the earliest stages of tumour development, before any treatment. The influential synthesis of this idea holds that replication stress is the engine generating the genomic instability on which tumour evolution then feeds, and that this is why loss of p53 is selected for so early and so universally: it removes the response that would otherwise eliminate the damaged cells.
Head-on versus co-directional
Now the central concept. A fork and a transcribing polymerase on the same stretch of DNA can be arranged two ways.
Co-directional: both travelling the same way. The fork catches up with the polymerase from behind. This causes delay and is not harmless, but it is survivable; the fork can displace the polymerase or wait.
Head-on: travelling towards each other. Three things make this much worse. The DNA between them accumulates positive supercoiling with nowhere to go, because both machines are pushing twist into the same shrinking interval. Any RNA:DNA hybrid in that interval is stabilised rather than displaced. And the fork is far more likely to reverse or collapse, producing a break.
Same direction is a traffic jam. Opposite directions is a head-on crash on a single-track line.
The group's 2024 paper turned this into a measurement. Because the break-mapping assay preserves the orientation of each captured broken end, each break can be labelled as pointing towards the centromere or towards the telomere — written Dcen and Dtel. A rightward-moving fork generates centromere-oriented ends; a leftward-moving fork generates telomere-oriented ends. Comparing break orientation against locally measured fork direction and gene direction therefore classifies each break as head-on or co-directional, and the proportions are reported as PHO and PCD. Fifty per cent means no preference. Under replication stress induced with aphidicolin, the reported head-on proportion rose to roughly sixty per cent while the co-directional proportion fell to roughly forty.
A shift from 50:50 to 60:40 sounds modest. Its importance is not its size but its direction and what it rules out.
If breaks were caused simply by late replication, or by being inside a long gene, or by high transcription, the orientation of the breaks would carry no information — you would expect 50:50 regardless. The fact that the ratio moves specifically towards head-on when you add replication stress means the geometry is causal, not just the location. That is a conclusion no amount of break density mapping alone could reach, and it is available only because the assay keeps orientation.
If you remember one quantitative result from the group's work, remember this one, and remember why the orientation information is what makes it possible.
| Agent | What it does | Typical use in this field |
|---|---|---|
| Aphidicolin | Inhibits DNA polymerases, slowing forks without stopping synthesis outright | The standard tool. The group used 0.2–0.6 µM for dose–response, and 0.5 µM for 96 h to induce copy-number change. Low doses are deliberate: the aim is chronic mild stress, not catastrophe. |
| Hydroxyurea | Depletes the nucleotide supply by inhibiting ribonucleotide reductase | Acute, severe stress; used for fork-restart and collapse studies rather than hotspot mapping. |
| Camptothecin | Traps topoisomerase I on DNA | Topological stress and transcription-associated damage. |
| Etoposide | Traps topoisomerase II, producing protein-linked breaks | Programmed and therapy-associated breakage, relevant to leukaemia models. |
| Oncogene induction | Forces premature S entry and excess origin firing | The physiologically faithful inducer; slower and less controllable than a drug. |
| ATR or WEE1 inhibition | Removes the brake that restrains origin firing and protects forks | Both an experimental inducer of stress and a candidate therapy — see §2.6. |
2.3 · Breaks, hotspots and translocations
A break hotspot is a genomic interval where breaks are recovered more often than the local background allows. The phrase hides a statistical decision: “more often than background” requires a background model, and the choice of that model determines which hotspots exist. The group's analyses smooth break density over intervals of roughly 25 to 50 kilobases, which is the scale at which this biology operates — a conflict zone is tens of kilobases wide, not tens of base pairs.
A translocation is the joining of two broken ends that came from different places in the genome. It requires three things: a break at locus A, a break at locus B, and the two loci being physically near each other inside the nucleus at that moment. That third requirement is why translocation frequency reports on nuclear architecture as well as on breakage, and why the historical name for this assay family refers to proximity-based break joining.
Not all breaks are accidents. Developing lymphocytes make them on purpose, cutting and rejoining their own antigen-receptor genes using the RAG1/RAG2 enzymes and, later, the enzyme AID. This is the biology the break-mapping method was originally built to study, which is worth knowing because it explains the leukaemia arm of this project: in lymphoid cells you have both programmed and accidental breakage in the same genome, and distinguishing them is a genuine analytical problem.
Fragile sites
Common fragile sites are chromosomal regions that break reproducibly when cells are treated with low-dose aphidicolin. Two are canonical: FRA3B, which contains the gene FHIT, and FRA16D, which contains WWOX — the gene that brings the Jerusalem collaboration into this project. Their properties will now sound familiar: very large transcribed genes, late replication, few origins, and sequences with a tendency to adopt awkward secondary structures. They are the human-cancer counterpart of the recurrent break clusters the group mapped in mouse neural progenitors, which is precisely why the framework should transfer.
A separate class, early replicating fragile sites, breaks under the opposite conditions — in early S phase, at highly transcribed gene-dense regions — which is a useful reminder that late replication is not a universal requirement for fragility.
2.4 · R-loops
An R-loop is a three-stranded structure. Normally, after RNA polymerase has read the DNA, the two DNA strands close behind it and the new RNA leaves. Sometimes the RNA instead folds back and re-anneals to its template strand, forming an RNA:DNA hybrid and leaving the other DNA strand hanging as exposed single-stranded DNA.
They are promoted by G-rich sequence on the displaced strand, by the under-winding left behind a polymerase, by high transcription, and by anything that stops the new RNA being packaged and exported promptly — defective splicing or RNA-processing machinery is a classic cause. They are removed by the enzymes RNase H1 and H2, which digest the RNA within a hybrid, and by helicases such as senataxin that unwind it.
R-loops are not simply damage. They have normal functions at promoters and transcription terminators, in antibody class switching, and at mitochondrial replication origins. The problem is when they persist in the wrong place — above all in the interval between a converging fork and an oncoming polymerase, where they are stabilised rather than displaced and become a physical block that turns a stalled fork into a broken one.
Measurement is by immunoprecipitation with the S9.6 antibody, which recognises RNA:DNA hybrids — the DRIP-seq assay of Module 3.
The antibody is not clean. S9.6 also binds double-stranded RNA. Any DRIP signal therefore requires a control in which the sample is pre-treated with RNase H: genuine hybrid signal disappears, artefact does not. A DRIP result presented without that control is not evidence. Confirming with an orthogonal method — a catalytically dead RNase H1 as a probe, for instance — is better still.
R-loops are not the explanation for most break clusters. This is the specific, checkable fact that separates someone who read the group's 2024 paper from someone who read its abstract. In that work, roughly two-thirds of the recurrent break clusters had no detectable R-loops at all; about a third had between one and nine, and only four had more than ten.
So R-loops are one mechanism contributing at a minority of loci — not the general cause of recurrent breakage. If you are asked about R-loops in interview and you answer that they are what makes these regions fragile, you will have contradicted the group's own data. The correct answer is that head-on geometry is the general feature and R-loops are an aggravating factor at a subset of sites; establishing which subset, and why those, is an open question — and a very good one to say you would like to work on.
2.5 · Copy-number alterations and structural variants
A structural variant is any rearrangement of the genome larger than about fifty base pairs. A copy-number alteration is the subset of those that changes how many copies of a region are present. The distinction matters because it maps onto what breaks can do: an inversion or a balanced translocation moves DNA without changing its amount, while a deletion or duplication changes the amount.
| Class | What happened | Signal used to detect it |
|---|---|---|
| Deletion | A segment is lost | Reduced read depth; read pairs spanning further apart than expected |
| Duplication | A segment is present more than once | Increased read depth; read pairs closer or inverted in orientation |
| Inversion | A segment is flipped | Read pairs in the wrong relative orientation; depth unchanged |
| Translocation | Two different chromosomes joined | Read pairs mapping to two chromosomes; split reads crossing the junction |
| Chromothripsis | A region shattered and reassembled near-randomly | Many breakpoints clustered on one or few chromosomes, with copy number oscillating between just two or three states |
| Breakage–fusion–bridge | Telomere loss leads to chromosome fusion, a bridge at division, and a new break each cycle | Fold-back inversions and stepwise amplification towards a chromosome end |
| Extrachromosomal DNA | A segment circularises and replicates outside the chromosomes | Very high, variable copy number; circular junction reads; unequal inheritance between cells |
Two methods from the group's 2026 paper are worth knowing by name because they answer questions bulk sequencing cannot. Strand-seq is single-cell sequencing that keeps track of which parental strand each read came from, which makes inversions and individual breakpoints directly visible one cell at a time. In that work it showed that 118 of 302 breakpoints in cells with reduced copy number mapped to known break clusters — a per-cell link between the break map and the resulting structural change. And the under-replication index quantifies how much of a region failed to finish replicating, which is the measurement that connects replication stress to the downstream rearrangement.
For this project's tumour types the relevant fact is that osteosarcoma genomes are dominated by exactly the complex classes in the lower half of that table — chromothripsis, breakage–fusion–bridge, extrachromosomal amplification — rather than by simple recurrent point mutations.
2.6 · Reverse-translational targeting of the damage response
Classical translational research runs from laboratory to clinic. Reverse translation runs the other way: it starts from an observation in human patients or patient material, goes back into the laboratory to find the mechanism, and uses that mechanism to propose a treatment. The advert's phrasing — help develop reverse-translational therapy strategies for osteosarcoma and breast cancer — means exactly this. The observation is that these tumour genomes are rearranged in particular patterns; the laboratory work is to find out what produces those patterns; the therapeutic proposal follows from the mechanism.
The logic that makes it a therapy is synthetic lethality: two defects that are each survivable alone but lethal together. If a cancer already depends heavily on one route for coping with replication stress, blocking that route kills it while leaving normal cells, which were not relying on it, comparatively unharmed.
| Target | Its normal job | Why blocking it is selective | Example agents |
|---|---|---|---|
| ATR | Senses single-stranded DNA at stalled forks and triggers the response | Cells with high intrinsic replication stress cannot survive without it; normal cells rarely need it | Ceralasertib, berzosertib, elimusertib |
| CHK1 | Executes ATR's orders — pauses the cycle, restrains origin firing | Same principle, one step downstream | Prexasertib |
| WEE1 | Holds the cell back from mitosis until replication is finished | Forces cells with unreplicated DNA into division; strongly linked to cyclin E amplification | Adavosertib, azenosertib |
| PARP | Detects single-strand damage and assists repair | Lethal when homologous recombination is already broken, as in BRCA-mutant tumours | Olaparib, talazoparib |
| Polymerase theta | Performs microhomology-mediated end joining | The backup route for cells that cannot use homologous recombination — and the enzyme that turns these breaks into focal deletions | Novobiocin, ART558, ART4215 |
| DNA-PK | Core kinase of non-homologous end joining | Removes the fast repair route; also a radiosensitiser | Peposertib |
Polymerase theta is where the group's own mechanism meets the drug cabinet, and it is the cleanest illustration of what reverse translation means here.
The 2026 paper did not use a polymerase theta inhibitor as a candidate treatment. It used one as a mechanistic tool: inhibit the enzyme, and the recurrent focal copy-number changes disappear, while the junctions that remain lose their microhomology signature. That establishes causation — this pathway is what converts these breaks into these rearrangements.
The therapeutic inference then follows by itself. A tumour whose genome evolution depends on polymerase theta is a tumour that may be dependent on polymerase theta, and that dependency is already druggable. The chain runs: map the breaks, explain their positions, identify the pathway that fixes them wrongly, inhibit it, and check whether the tumour needs it more than normal tissue does.
That chain is the thesis. Modules 3 to 5 are the techniques for each link in it.
2.7 · The whole vocabulary, collected
| Term | What it means | Picture to hold |
|---|---|---|
| Cell cycle | G1 (grow) → S (copy the DNA) → G2 (check) → M (divide). | Four shifts in a factory day. |
| Origin of replication | A designated point where DNA copying starts; thousands exist per genome. | Where a road crew starts work. |
| Replication fork | The moving point where DNA is being unwound and copied; travels outward from an origin. | The advancing work front. |
| Fork direction | Whether a given fork is travelling leftward or rightward along the chromosome. | Which way the crew is heading. |
| Termination zone | Where two forks travelling towards each other meet. | Where two crews shake hands. |
| Replication timing | When in S phase a region is copied — early or late. | The works schedule. |
| TTRtiming transition region | A broad interval where timing slopes from early to late, usually crossed by one long-travelling fork. | The long stretch with no crew of its own. |
| Transcription direction | Which way along the chromosome a gene is read, set by which strand is the template. | The one-way sign on the gene. |
| Nascent transcription | Transcription happening right now, as opposed to accumulated RNA from earlier. | Traffic currently on the road, not cars parked overnight. |
| DSBdouble-strand break | Both DNA strands severed at the same point. | A rope cut through, not frayed. |
| NHEJ | Fast repair that trims and rejoins the ends; leaves small scars. Needs XRCC4 and LIG4. | Taping the rope back together. |
| HRhomologous recombination | Accurate repair copying from the intact sister chromosome; S and G2 only. | Rebuilding from the blueprint. |
| MMEJ / polymerase theta | Repair that aligns a few matching letters near the ends and deletes what lies between. | Splicing the rope by overlapping two frayed bits — shorter rope. |
| Microhomology | The two to twenty matching letters found at an MMEJ junction; the pathway's fingerprint. | The overlap mark left by the splice. |
| Replication stress | Forks slowing, stalling or collapsing, from any cause. | The resurfacing job falling behind schedule. |
| ATR → CHK1 | The signalling pair that senses stalled forks and slows the cell down. | The site foreman calling a halt. |
| Head-on conflict | Fork and transcribing polymerase travelling towards each other. | Two trains, one track, facing. |
| Co-directional conflict | Fork and polymerase travelling the same way. | Fast train stuck behind a slow one. |
| P_HO / P_CD | The proportion of breaks in head-on versus co-directional orientation. 50% means geometry is irrelevant. | The score line of the whole project. |
| Dcen / Dtel | A captured broken end pointing towards the centromere or towards the telomere. | Which way the cut end was facing. |
| RDCrecurrent DNA break cluster | An interval that repeatedly breaks across independent cells; found in long, late-replicating, transcribed genes. | The pothole that always reappears. |
| Common fragile site | A region that breaks reproducibly under low-dose aphidicolin — FRA3B/FHIT, FRA16D/WWOX. | The bridge that always cracks in frost. |
| Bait / prey | The deliberately induced break used as an anchor, and the unknown breaks found joined to it. | A tagged fish-hook and whatever bites. |
| R-loop | RNA re-annealed to its DNA template, leaving the other DNA strand exposed. | A zip caught on its own thread. |
| S9.6 | The antibody used to pull down RNA:DNA hybrids; also binds double-stranded RNA, so needs an RNase H control. | A magnet that also picks up the wrong metal. |
| RNase H | Enzyme that digests the RNA inside a hybrid; used both in cells and as the negative control. | The tool that removes the caught thread. |
| CNA / SV | A change in how many copies of a region exist / any rearrangement over ~50 bp. | Pages duplicated or lost / pages reordered. |
| Chromothripsis | A chromosome region shattered and reassembled nearly at random. | A vase smashed and glued back wrong. |
| Strand-seq | Single-cell sequencing that preserves parental strand identity, revealing inversions and per-cell breakpoints. | Reading each cell's own copy, with the margin notes intact. |
| Aphidicolin | A polymerase inhibitor used at low dose to slow forks and induce controlled replication stress. | Mild, deliberate sand in the gears. |
| Synthetic lethality | Two defects each survivable alone, fatal together. | Losing one engine, then the other. |
| Reverse translation | Starting from a human observation, going back to the laboratory for mechanism, returning with a treatment idea. | Working backwards from the crime scene. |
- Why a fork has a direction at all, and where that direction comes from. (§2.1)
- Why the group's cells lack both XRCC4 and p53, and what caveat that creates. (§2.1 key box)
- Why head-on conflicts are more damaging than co-directional ones — three reasons. (§2.2)
- Why a 60:40 head-on ratio is more informative than a much larger difference in break density. (§2.2 key box)
- What fraction of recurrent break clusters have no detectable R-loops, and what follows from that. (§2.4 pitfall)
- How a transient break becomes a permanent focal deletion, and which enzyme does it. (§2.1, Figure 2D)
- What reverse translation means, using polymerase theta as the example. (§2.6)
The four assays, and the pipeline behind them
Each of the four measures exactly one layer of Figure 1. For each: the physical trick that makes it possible, the protocol, the control without which the result means nothing, the shape of the output file, and the specific way it misleads people.
3.1 · Words for this module
| Term | What it means | Picture to hold |
|---|---|---|
| ImmunoprecipitationIP | Using an antibody to fish one specific kind of molecule out of a mixture, then washing everything else away. | A magnet pulled through gravel to collect the iron. |
| Pull-down | The same operation described informally; the antibody is attached to beads that can be physically collected. | The magnet, with a handle. |
| Biotin / streptavidin | A chemical tag and the protein that binds it almost irreversibly; the standard way to grab a specific DNA strand. | Velcro: one side on your molecule, the other on the bead. |
| Sonication | Breaking DNA into fragments with ultrasound; breaks land at effectively random positions. | Smashing a long rod with a hammer — the pieces are never the same twice. |
| Restriction digestion | Cutting DNA with enzymes that cut only at fixed sequences; every sample is cut in the same places. | Tearing along pre-printed perforations. |
| Adapter | A short known DNA sequence ligated onto an unknown fragment so a primer has somewhere to bind. | A standard plug fitted to a bare wire. |
| Linear amplification | Copying from a template with one primer only, so each cycle adds one copy rather than doubling. Used when you know only one side of your target. | Hand-copying a page repeatedly, instead of photocopying the photocopies. |
| Nested PCR | A second amplification using primers sitting just inside the first pair, to remove products that were amplified by accident. | A second, stricter sieve. |
| Bait | A deliberately made break at a known position, used as an anchor you can design primers against. | A labelled hook. |
| Prey | An unknown break elsewhere in the genome, discovered because it was joined to the bait. | Whatever bit the hook. |
| Junction | The exact point where bait sequence stops and prey sequence begins, within one sequencing read. | The seam between two fabrics. |
| Run-on | Letting already-engaged polymerases continue transcribing in isolated nuclei, while preventing any new ones from starting. | Letting the cars already on the road finish their journey, with the on-ramps closed. |
| Sarkosyl | The detergent that blocks new transcription initiation and releases paused polymerases, making the run-on measure only what was already engaged. | The barrier placed across the on-ramp. |
| BrdU / Br-UTP | Modified building blocks incorporated into new DNA or new RNA, so that only newly made molecules carry a tag an antibody can recognise. | Marking today's output with fluorescent paint. |
| FACS sorting | Measuring each cell individually and physically separating them into groups — here, by how much DNA they contain. | Sorting coins by weight into bins. |
| Spike-in | A known quantity of foreign DNA or RNA added to every sample, so signals can be compared between samples in absolute terms. | A ruler included in every photograph. |
| Mappability | Whether a short read from a given region can be placed uniquely in the genome. Repetitive regions have low mappability. | A page of text that appears identically in fifty books. |
| Blacklist | A published list of regions that produce spurious signal in every experiment and are excluded by convention. | Known-faulty sensors, switched off. |
| MAPQ | A score expressing how confident the aligner is that a read is in the right place. | The confidence rating on an identification. |
| Deduplication | Removing reads that are copies of one original molecule rather than independent observations. | Counting people, not their photographs. |
3.2 · LAM-HTGTS — where the genome breaks, with direction
The measurement problem is severe. A double-strand break is transient, it occurs at an unknown position, and it occurs in a small fraction of cells. You cannot design a primer against a position you do not know.
The solution is indirect and rather elegant. You make one break yourself, at a position you choose — the bait. The cell's repair machinery will occasionally join that bait end to some other broken end elsewhere in the genome — a prey. Because you know the bait's sequence exactly, you can anchor on it and read outward into whatever got attached. Each such molecule reports the position of one genuine break, discovered without knowing in advance where to look.
You want to know which rooms in a huge building have holes in the wall, but the holes appear and get patched too quickly to find by searching.
So you knock a hole of your own in one room you have chosen, and paint its edges a distinctive colour. Occasionally, when the building's repair crew patches two holes, they join your painted hole to a hole in another room. Now you can find your paint, follow it through, and arrive in a room you did not know had a hole — and you know which room it was.
Two consequences fall straight out of the analogy, and both are real limitations. You only ever find holes that happened to get joined to your hole, so rooms near yours are over-represented. And the method tells you a hole existed in that room, not how many times it has happened there, unless you are careful about counting.
Why linear amplification
Ordinary PCR needs two primers, one on each side of the target. Here only one side is known. So the first amplification uses a single primer that sits in the bait and carries a biotin tag, and it is run for many cycles of simple extension: each cycle copies once from the genomic template, running from the bait across the junction and out into the unknown prey. The products are single-stranded, each carries biotin at its known end, and they can therefore be captured on streptavidin beads while everything else is washed away. Only then is an adapter ligated to the unknown end, giving the second primer a landing site, and a nested PCR produces a sequenceable library.
You cannot amplify between two points when you only know one of them. So you copy outward from the one you know, grab those copies by their tag, and only afterwards attach a handle to the far end.
- Induce the bait break A sequence-specific nuclease — Cas9 with a defined guide, or the meganuclease I-SceI at an engineered site — cuts at the chosen position. The group's 2026 work placed baits on chromosomes 6, 8 and 12.
- Harvest and fragment the genomic DNA Sonication is used, and the randomness is deliberate: because every molecule breaks at a different place, two sequencing reads sharing both the same junction and the same fragment end must be copies of one original molecule, whereas the same junction with different fragment ends represents two independent events. This is the basis of honest counting.
- Linear amplification from the bait Many cycles of extension with the single biotinylated bait primer.
- Capture on streptavidin beads Everything without the tag is washed away.
- Ligate an adapter to the unknown end A single-stranded adapter is joined to the free prey-side end.
- Remove uncut bait Most copies of the bait locus in the cell population were never cut, or were cut and perfectly rejoined, and they would otherwise flood the library. A blocking digestion removes them. Skipping or under-performing this step is the single most common reason a library returns almost nothing useful.
- Nested PCR and sequencing A bait-internal primer plus an adapter primer, then paired-end sequencing.
- Call junctions For each read, find where bait sequence ends and prey begins, align the prey portion, and record its chromosome, position, orientation, fragment end, and the sequence present at the junction itself — which is where any microhomology shows up.
The orientation is the point of the whole exercise. Because the assay reads from a fixed anchor outward, the strand and direction of the prey sequence are preserved, so each recovered end can be classified as centromere-oriented or telomere-oriented. That is what makes the head-on versus co-directional analysis possible at all, and it is why the advert describes the method as direction-resolved.
Proximity bias. Recovery of a prey break depends on that locus being physically near the bait in the nucleus. Junction counts therefore fall off steeply with genomic distance from the bait and are much higher on the bait's own chromosome. A map built from one bait is not a map of genome-wide breakage; it is a map of breakage as seen from that bait. Using several baits on different chromosomes, as the group does, is the mitigation — and comparing treated with untreated using the same bait is what makes the comparison valid.
Bait-proximal junctions are not prey. The large majority of recovered junctions sit within a few kilobases of the bait, from the bait end being resected and rejoined locally. These must be excluded by a defined window, and the window must be stated, because where you draw it changes your numbers.
Absence of junctions is not absence of breakage. Repetitive and low-mappability regions cannot yield uniquely placed prey sequence. They will look quiet. Before interpreting a quiet region, check whether it is quiet or merely unmappable.
3.3 · Hi-RepliSeq — when each region is copied, and which way the fork runs
The principle is a stopwatch built from a cell sorter. Newly made DNA is tagged as it is synthesised; cells are then separated according to how far through S phase they have progressed; and the tagged DNA from each group is sequenced. Regions appearing in the earliest group replicate early; regions appearing only in the last group replicate late.
- Pulse-label new DNA Cells are given BrdU, a modified building block, for a short window. Only DNA made during that window carries the tag.
- Sort cells by position in S phase Cells are fixed, their total DNA content is stained and measured, and they are sorted by that content — a cell early in S has barely more DNA than a G1 cell, one late in S has nearly twice as much. High-resolution Repli-seq takes sixteen fractions, S1 to S16, rather than the two of the original method, and that resolution is what makes the next steps possible.
- Pull down the tagged DNA from each fraction An anti-BrdU antibody recovers only newly synthesised DNA, separately for each of the sixteen fractions.
- Sequence each fraction and build the matrix Sixteen libraries are mapped and counted in genomic bins, giving a matrix of sixteen rows by however many bins the genome is divided into. Displayed as a heatmap, it is the recognisable Repli-seq picture.
- Extract the features From that matrix: replication timing per bin; initiation zones, where signal first appears in a narrow region and then spreads outward in both directions; termination zones, where two spreading regions converge and replication finishes last; and timing transition regions, the broad slopes between early and late domains.
- Derive fork direction The DNA between an initiation zone and the nearest termination zone must have been copied by a fork travelling from the former towards the latter. Connecting each initiation zone to its neighbouring termination zones therefore assigns a direction to each interval. The group used a convolutional neural network to assist this calling, and accepted a direction only where both replication-stressed technical replicates agreed.
This measurement is made across many thousands of cells. Individual cells do not all fire the same origins; origin choice is substantially stochastic. So an interval labelled rightward means that in most cells, most of the time, it was copied rightward — not that it is always copied rightward in every cell.
That caveat matters whenever you want to claim a mechanism in a single cell, and it is why the group's single-cell work used Strand-seq rather than inferring from population timing. It is also why fork direction should be called conservatively: requiring agreement between replicates before accepting a direction, as the group does, is not excess caution but the minimum.
The orthogonal method worth being able to name is OK-seq, which sequences Okazaki fragments and reads fork directionality more directly, from the strand on which discontinuous synthesis occurred. If asked how you would verify a direction call, that is the answer.
3.4 · GRO-seq — transcription as it is happening, with a direction
Ordinary RNA sequencing measures the RNA that has accumulated in a cell. For this project that is the wrong quantity twice over. A stable RNA can still be abundant hours after its transcription stopped, so abundance does not report current activity; and many library preparations discard strand information entirely, so the direction — the thing the whole project turns on — is lost.
GRO-seq measures only polymerases that are engaged on DNA at the moment the cells are harvested, and keeps the strand.
- Isolate nuclei The cell membrane is removed but the nucleus is left intact, with polymerases still sitting on the DNA where they were.
- Run-on with the on-ramps closed Sarkosyl is added, which prevents any new polymerase from starting and releases paused ones into elongation. Then a modified nucleotide, Br-UTP, is supplied along with the ordinary ones. Every polymerase that was already engaged extends its transcript and incorporates the tag; nothing that was not already engaged contributes at all.
- Fragment and immunoprecipitate The RNA is fragmented and the tagged portions are pulled down with an anti-BrdU antibody, which recognises the incorporated Br-U.
- Strand-specific library and sequencing The library must preserve which strand the RNA came from. A non-stranded protocol here destroys the experiment's entire purpose.
The variants worth knowing by name: PRO-seq resolves the polymerase position to roughly a single nucleotide rather than a fragment; TT-seq labels nascent RNA metabolically in living cells without isolating nuclei; NET-seq sequences the RNA still held within the polymerase.
It is tempting to skip this assay and read gene direction from a gene annotation file. For long genes that is a real error source, for three reasons. Long genes frequently contain internal alternative promoters, so different segments may be transcribed by different units. Promoters produce divergent transcription in both directions, so signal near a gene start is not a clean indicator of the gene's own direction. And annotation describes which transcripts exist in some cell somewhere, not which are active in your cells.
Since the quantity being tested is the relationship between two measured directions, taking one of them from a file rather than from the sample imports an unknown error into the central result. Measure it.
3.5 · DRIP-seq — where RNA is annealed to DNA
The structure being measured is an RNA:DNA hybrid, and the tool is the S9.6 antibody, which binds that structure. The assay is therefore conceptually the simplest of the four: fragment the DNA, pull down with S9.6, sequence what came along.
- Extract genomic DNA gently Harsh handling destroys the structures you are trying to measure.
- Fragment Classically a cocktail of restriction enzymes, which cut at fixed positions and so limit resolution to the fragment size; sonication gives finer resolution but risks disrupting hybrids. The choice is a genuine trade-off and should be stated in any methods section.
- Split the sample and treat one half with RNase H This is the control the assay lives or dies by. RNase H digests the RNA within a hybrid specifically. Signal that disappears was a hybrid; signal that survives was something else.
- Immunoprecipitate with S9.6, build libraries, sequence The group normalised to fifty million reads per sample for comparability.
- Call peaks against the RNase H-treated sample Not against input alone.
For strand information there is DRIPc-seq, which converts the recovered RNA to cDNA and so reports which strand the hybridised RNA came from — necessary if you want to ask whether the hybrid lies in the path of an oncoming fork. The group reported that roughly one per cent of the genome carried coding-strand-specific hybrids. Alternative approaches worth naming are R-ChIP, which uses a catalytically dead RNase H1 as a probe inside living cells, and MapR, which fuses a nuclease to RNase H1 and needs no antibody at all.
3.6 · The four side by side
| LAM-HTGTS | Hi-RepliSeq | GRO-seq | DRIP-seq | |
|---|---|---|---|---|
| Measures | Positions and orientations of double-strand breaks | When each region replicates, and which way the fork runs | Where polymerases are actively transcribing, and in which direction | Where RNA is annealed to DNA |
| Physical trick | Anchor on a break you made yourself; read outward into the one you did not | Tag new DNA, then sort cells by how far through S phase they are | Let engaged polymerases run on while blocking new starts | An antibody that recognises the hybrid structure |
| Output | A list of individual junction events with coordinates and direction | A 16-row matrix per genomic bin; derived timing and direction tracks | Stranded signal along the genome | Signal along the genome; peaks |
| Resolution | Nucleotide, at the junction | Tens of kilobases | Nucleotide-scale (PRO-seq) to short fragment | Restriction fragment, unless sonicated |
| The control it cannot do without | Bait-proximal exclusion window, plus duplicate removal using fragment ends | Both stressed and unstressed conditions; replicate agreement on direction | A strand-specific library — and nuclei that were genuinely intact | RNase H-treated parallel sample |
| Characteristic artefact | Apparent breakage concentrated near the bait; silence in unmappable regions | Direction calls treated as true of single cells | Annotation substituted for measurement; divergent promoter signal misread | Signal from double-stranded RNA mistaken for hybrid |
| Layer of Figure 1 | The break-density curve | The timing profile and the fork arrows | The transcription arrow | The aggravating factor at a minority of loci |
| Layer | Primary assay | Independent method | What the cross-check buys you |
|---|---|---|---|
| Break positions | LAM-HTGTS | END-seq, BLISS or sBLISS | Breaks detected without needing a bait, so free of proximity bias — at the cost of losing the joining information. |
| Fork direction | Hi-RepliSeq | OK-seq | Direction read from Okazaki-fragment strand rather than inferred from timing geometry. |
| Nascent transcription | GRO-seq | PRO-seq, TT-seq | Finer polymerase positioning, or labelling in intact living cells. |
| R-loops | DRIP-seq | R-ChIP, MapR, DRIPc-seq | Removes dependence on the S9.6 antibody and adds strand information. |
| Resulting rearrangements | Whole-genome sequencing | Strand-seq; long-read sequencing | Per-cell breakpoints and inversions; resolution of complex junctions bulk short reads cannot phase. |
3.7 · The sequence-processing chain
All four assays end as sequencing reads, and three of them then follow a largely common path. LAM-HTGTS is the exception: because its information is a junction within a read rather than a read position, it needs a dedicated junction-calling step rather than a standard alignment-and-coverage workflow.
| Stage | Purpose | Common tools | Failure to watch for |
|---|---|---|---|
| Read QC | Check quality, adapter content, duplication | FastQC, MultiQC | Proceeding past an obviously failed run because the pipeline did not error. |
| Trimming | Remove adapters and low-quality tails | fastp, cutadapt, Trim Galore | Over-trimming short reads into unmappability. |
| Alignment | Place reads on the genome | BWA-MEM or bowtie2 for DNA; STAR or HISAT2 for RNA | Wrong genome build, or an RNA aligner used on DNA and vice versa. |
| Filtering | Keep confidently placed reads | samtools view -q, ENCODE blacklist | No MAPQ filter, so repeats generate phantom signal. |
| Deduplication | Count molecules, not copies | Picard MarkDuplicates; for LAM-HTGTS, junction plus fragment end | Deduplicating by position alone in an assay where position is shared by design. |
| Signal generation | Turn reads into a comparable track | deeptools bamCoverage → bigWig | Comparing samples normalised differently, or not normalised at all. |
| Region calling | Define peaks, hotspots or zones | MACS2 for peaks; kernel smoothing at 25–50 kb for break clusters | A background model that does not fit the assay's own biases. |
| Integration | Combine layers on shared coordinates | bedtools, GenomicRanges, pyranges | Coordinate-system mismatches — the subject of Module 5. |
| Statistics | Decide whether an overlap is more than chance | regioneR, GAT, permutation | A naive test that ignores region length, mappability and timing. |
The posting says you would generate engineered cancer cell lines together with a technician. Reading the four assays above tells you what those lines are for, and it is worth being able to say so.
Three kinds of engineering are implied by the methods. Bait insertion, because LAM-HTGTS needs a defined cut site, and comparing cancer types requires equivalent baits in each line. Repair-pathway modification, because breaks must persist to be captured — the mouse work used XRCC4 and p53 loss, and some equivalent accommodation will be needed in human cancer lines, which already carry their own repair defects. And targeted deletion of regulatory elements, which is how the group demonstrated that transcription is causal: remove a promoter, watch the break cluster disappear.
If you are asked what you would want to build first, a defensible answer is a matched set — the same bait, in the same genomic context, in an osteosarcoma line and a breast cancer line — because without matched baits, differences between cancer types cannot be separated from differences between bait positions.
- Why LAM-HTGTS needs a bait at all, and what the bait costs you in interpretation. (§3.2)
- Why the DNA is sonicated rather than cut with enzymes, and how that enables honest counting. (§3.2)
- Why sixteen S-phase fractions rather than two, and what the extra resolution is spent on. (§3.3)
- How fork direction is derived from a timing matrix, and why it is a population statement. (§3.3)
- Why GRO-seq rather than RNA-seq, giving both reasons. (§3.4)
- What the RNase H control proves, and why a DRIP result without it is not evidence. (§3.5)
- One independent method for each of the four layers. (Table 3.3)
Learning roadmap, Level 0 to intermediate
Two separate jobs with two separate deadlines. The twelve days before the application closes are about producing evidence. The twelve weeks after it are about being able to defend that evidence in a room.
4.1 · The two deadlines
The application closes on 28 October 2026. Everything before that date has one purpose: to put something in the application that a group leader cannot get from a transcript. Everything after it has a different purpose: to be able to talk about replication stress with someone who has spent ten years on it.
Confusing these two jobs is the standard failure. A curriculum that starts with the cell cycle and reaches multi-omics integration in month four is the right curriculum and the wrong schedule, because by month four the decision has been made. So the sprint comes first, and it is deliberately narrow.
You cannot acquire three years of genomics in twelve days and nobody expects you to. What you can do is produce one small, complete, reproducible analysis of public data that touches this project's subject matter, and put a link to it in your CV. That single artefact does something no sentence in a cover letter can do: it demonstrates that you can obtain genomic data, handle coordinates correctly, produce a figure, and write down what you did so somebody else could repeat it.
It does not need to be novel. It does not need to be large. It needs to exist, run, and be honest about its limitations.
| Days | Task | Hours | Done when |
|---|---|---|---|
| 1–2 | Read the group's 2024 Nature Communications paper properly — figures first, then methods, then results. Write a one-page summary in your own words: what was measured, what was found, what remains open. | 6–8 | You can explain the head-on versus co-directional result to someone without using the word “multi-omics”. |
| 2–3 | Make the telephone call about eligibility. Prepare one sentence of self-description and one precise question; nothing more. | 1 | You know whether your degree field is acceptable, and you have stopped wondering. |
| 3–6 | Working environment: command line basics, conda, samtools, bedtools, and either R with GenomicRanges or Python with pyranges. Pick one language and stay in it. |
10–12 | You can download a BED file, intersect it with another, and explain why the coordinate systems differ. |
| 6–10 | The analysis project. Take a public replication-timing dataset and a public gene annotation; compute whether long genes replicate later than short ones; then test whether a published set of common fragile sites falls in late-replicating regions more often than matched random regions do. Permutation test, not a chi-square. | 16–20 | A repository exists with a README, a script that runs start to finish, two figures, and a limitations paragraph. |
| 10–11 | Rewrite the CV as a research CV: education with thesis title and supervisor first, then any laboratory techniques by name, then computational skills, then the project link. The care-home position goes at the bottom in one line. | 4 | The most relevant thing about you is visible in the first third of page one. |
| 11–12 | Cover letter. One page. First paragraph addresses the degree-field question directly and without apology; second says what you have done; third says what specifically about this project you want, naming the mechanism not the institute. | 4 | Nothing in it would apply equally to a different advert. |
| 12 | Submit through the portal. Confirm your two referees have what they need and know the deadline. | 1 | Submitted, with time to spare for a portal that misbehaves. |
The task in days 6–10 is not arbitrary. It is the smallest possible exercise that touches every skill this project needs:
- It uses replication timing, the project's central measurement, so the subject matter is right.
- It requires interval arithmetic between two coordinate systems, which is where beginners make errors and where the error is invisible.
- It asks a question with a known answer — long genes do replicate later, fragile sites are late — so you can tell whether you did it correctly. Starting with an open question gives you no way to check yourself.
- It forces a proper null model, because comparing fragile sites against random genomic positions without matching for length and mappability gives a confidently wrong answer. Getting this right is the single clearest signal of analytical maturity you can send.
And it gives you something to say when asked what you have worked on, which otherwise is the question that ends the interview early.
4.2 · The twelve weeks after submission
If the application succeeds you will be asked to discuss this science with people who know it well, probably six to twelve weeks later. The phases below are the curriculum; the hours are realistic for someone working alongside other commitments.
Biological and computational foundations
Everything here is prerequisite. Skipping it makes Phase 2 incomprehensible rather than merely difficult.
- Cell cycle and checkpoints — G1/S control, the role of CDKs, what a checkpoint physically does.
- DNA replication machinery — origin licensing and firing, the replisome, leading and lagging strand synthesis, why the lagging strand is discontinuous. The last point matters because OK-seq depends on it.
- Repair pathways — NHEJ, homologous recombination, MMEJ with polymerase theta, single-strand annealing. For each: when in the cell cycle, which proteins, what scar.
- Alternative lengthening of telomeres — the recombination-based telomere maintenance route, because it is a recurring feature of osteosarcoma and sits on the same recombination machinery.
- Command line and one language — file navigation, pipes, shell scripting; then R with the tidyverse and
GenomicRanges, or Python with pandas andpyranges. - Version control — enough git to keep an analysis reproducible and publish it.
Replication stress and the origin of break hotspots
The conceptual core. By the end of this phase you should be able to argue about mechanism, not recite it.
- Oncogene-induced replication stress — how cyclin E or MYC overexpression produces fork collapse; nucleotide pool exhaustion; the early-tumorigenesis model and why p53 loss follows.
- The ATR–CHK1 axis — sensing, signalling, fork protection, origin suppression. Then where each inhibitor class acts.
- Transcription–replication conflicts — head-on versus co-directional; supercoiling; why head-on stabilises hybrids.
- Common fragile sites — the competing explanations (gene length and transcription duration, origin paucity, sequence-driven secondary structure) and the evidence for each. Being able to say that these explanations are not fully resolved is better than picking one.
- R-loops — formation, physiological roles, resolution enzymes, and the specific limits of what DRIP data can show.
- The group's own papers, in order: 2016, 2020, 2024, 2026, plus the 2026 preprint on human cancer lines.
Assay literacy and handling real sequencing data
The transition from reading about methods to knowing what their files look like.
- Formats — FASTQ, SAM/BAM, BED, bigWig, VCF, GTF. For each: what it holds, whether coordinates start at zero or one, and whether it needs an index.
- The standard chain — QC, trimming, alignment, filtering, deduplication, coverage track, peak calling. Run it on a small public dataset end to end.
- Library construction logic — for each of the four assays, what the library physically contains and therefore what a read represents. This is what lets you predict an artefact rather than discover it.
- Background and noise — mappability, blacklists, input normalisation, why peak callers need an appropriate background model.
- Repli-seq specifically — obtain a public high-resolution Repli-seq dataset, reproduce a timing profile, identify initiation and termination zones by eye, then by rule.
Multi-omics integration — the thing the job actually is
Everything converges here. This is the work of the PhD, in miniature.
- Aligning layers measured at different resolutions — nucleotide-resolution junctions against 50-kilobase timing bins. Choosing a common bin size, and justifying it.
- Classifying head-on and co-directional intervals from a fork-direction track plus a stranded transcription track. Implement it yourself; it is roughly thirty lines of code and the logic is the project.
- Permutation-based enrichment — building a null model that matches region length, mappability, replication timing and expression. Learn
regioneRorGATproperly. - Confounder control — why late replication, gene length, expression level and chromatin state are all correlated with each other, and what that does to a naive test.
- Visualisation — stacked genome-browser-style tracks over a single locus, readable by someone else.
- Structural variant interpretation — how breakpoints are called from short reads, what chromothripsis and breakage–fusion–bridge look like in copy-number data, and what Strand-seq adds.
| Topic | Where | Note |
|---|---|---|
| Molecular biology foundations | Molecular Biology of the Gene or Molecular Biology of the Cell, replication and repair chapters | Read two chapters properly rather than skimming ten. |
| DNA repair in depth | Recent reviews on replication stress and on end-joining pathway choice | Reviews from the last three years; the field moved after polymerase theta became druggable. |
| The group's own work | Cell 2016; PNAS 2020; Nature Communications 2024 and 2026; the 2026 bioRxiv preprint | All open access or available as preprint. The 2024 paper is the one to know cold. |
| Command line and workflows | The Carpentries shell and git lessons; Biostar Handbook | Free, short, and aimed exactly at this gap. |
| Genomic ranges in R | GenomicRanges and regioneR vignettes; the Bioconductor workflow pages | Vignettes are better written than most tutorials. |
| Genomic ranges in Python | pyranges documentation; pysam and deeptools guides | Choose this route only if you are already comfortable in Python. |
| Public data | GEO, ENCODE, the 4D Nucleome portal, SRA | ENCODE has processed Repli-seq and transcription tracks ready to use — start there rather than with raw reads. |
| Statistics for intervals | regioneR vignette; the GAT paper | This is the one topic where getting it wrong is invisible and fatal. |
Learning two languages at once. R and Python both work for this. Doing both at the start means being incompetent in two languages instead of adequate in one. Pick the one your project needs and ignore the other for three months.
Reading instead of running. It is possible to read about BED files for a week and still mis-handle a coordinate. The phases are built around deliverables for this reason. If a week produced no file that runs, that week did not happen.
Starting with raw reads. Downloading a terabyte of FASTQ and building an alignment pipeline from nothing will consume the whole twelve weeks and teach you about cluster queues rather than about replication. Start from processed tracks, work backwards to raw data only once the biology is clear.
- End of sprint: is there a link in your CV to something that runs? (§4.1)
- End of Phase 0: can you draw the three repair pathways and their scars from memory? (Phase 0)
- End of Phase 1: can you name one real weakness in the 2024 paper? (Phase 1)
- End of Phase 2: have you produced a replication-timing profile from data rather than looked at one? (Phase 2)
- End of Phase 3: does your enrichment test have a null model you can defend out loud? (Phase 3)
Practical workflows in R and Python
The file formats and the one trap each of them sets, the packages that matter, and a worked integration that goes from break coordinates to a defensible enrichment statistic — including the null model, which is the part that is usually wrong.
5.1 · File formats, and the coordinate problem
Almost every error made by a beginner in this field is a coordinate error, and the reason is that two conventions coexist and neither announces itself.
BED files count from zero and exclude the end. A feature written as chr1 100 110 covers the eleventh through twentieth bases, and its length is simply 110 − 100 = 10.
GTF, GFF, VCF and SAM count from one and include the end. The same ten bases are written as chr1 101 110, and the length is 110 − 101 + 1 = 10.
One format starts counting at zero, the other at one. Mixing them shifts everything by a single base — which is invisible on a plot, survives every sanity check, and quietly corrupts any analysis that cares about exact positions. For junction-level work, it corrupts the result.
Never convert coordinates by hand. Use a library that knows the convention of the file it is reading — rtracklayer::import() in R, pyranges.read_bed() and read_gtf() in Python — and let it normalise internally. Both convert to a one-based internal representation on import and convert back on export.
When you must write arithmetic yourself, test it on a feature whose answer you know: take a single base, round-trip it through your code, and check that it comes back as the same base. That test takes two minutes and has saved entire projects.
| Format | Holds | Coordinates | The trap |
|---|---|---|---|
FASTQ | Raw reads with per-base quality | — | Paired files must stay in the same order; silently mismatched pairs produce nonsense alignments. |
SAM / BAM | Aligned reads, with flags, MAPQ and CIGAR | 1-based | Must be coordinate-sorted and indexed before most tools will use it. Unfiltered MAPQ lets repeats generate signal. |
BED | Intervals, optionally with name, score and strand | 0-based, end-exclusive | The zero-based start. Also: many tools silently require it sorted. |
bedGraph | Intervals with one value each | 0-based | Plain text and enormous; fine for small tracks, painful genome-wide. |
bigWig | Binned continuous signal, indexed and compressed | 0-based | It is already summarised. You cannot recover reads from it, and the bin size it was made with constrains every later analysis. |
GTF / GFF | Gene, transcript and exon annotation, with strand | 1-based, end-inclusive | The one-based start, plus the fact that one gene has many transcripts — decide which you mean. |
VCF | Variants, including structural variants | 1-based | Structural variants are described by INFO fields and mate records, not by a simple position; parse them properly. |
| Junction tableLAM-HTGTS output | One row per junction: chromosome, position, orientation, fragment end, junction sequence | Assay-specific | Not a standard format. Read its own documentation; do not assume BED semantics. |
| Job | Command line | R | Python |
|---|---|---|---|
| Read and filter alignments | samtools | Rsamtools | pysam |
| Interval arithmetic | bedtools | GenomicRanges, plyranges | pyranges |
| Import and export tracks | bigWigToBedGraph | rtracklayer | pyBigWig |
| Coverage and matrices | deeptools | GenomicAlignments | deeptools API |
| Annotation handling | awk on GTF | GenomicFeatures, txdbmaker | pyranges.read_gtf |
| Enrichment with a null model | bedtools shuffle, GAT | regioneR | custom permutation |
| Data wrangling and plots | — | tidyverse, ggplot2 | pandas, matplotlib |
| Track visualisation | IGV, UCSC browser | Gviz, karyoploteR | pyGenomeTracks |
5.2 · A worked integration
The task: given break hotspots, a replication fork-direction track, a stranded transcription track and gene annotation, classify the genome into head-on and co-directional compartments, count breaks in each, and test whether the difference is more than chance allows.
Step 1 — prepare the inputs on the command line
# Everything sorted the same way, or bedtools will lie to you quietly.
sort -k1,1 -k2,2n dsb_junctions.bed > dsb.sorted.bed
# Transcription start sites out of a GTF.
# GTF is 1-based inclusive; BED is 0-based exclusive -> subtract 1 from the start.
# For a minus-strand gene the TSS is at the END coordinate, not the start.
awk 'BEGIN{FS=OFS="\t"} $3=="gene" {
tss = ($7=="+") ? $4-1 : $5-1
match($0, /gene_name "[^"]+"/)
name = substr($0, RSTART+11, RLENGTH-12)
print $1, tss, tss+1, name, ".", $7
}' gencode.gtf \
| sort -k1,1 -k2,2n > tss.bed
# Distance from each break to the nearest TSS (-d appends the distance).
bedtools closest -a dsb.sorted.bed -b tss.bed -d > dsb_to_tss.tsv
# Which breaks sit in late-replicating domains.
bedtools intersect -a dsb.sorted.bed -b rt_late_domains.bed -u > dsb_late.bed
# A background set matched for chromosome and restricted to mappable sequence.
# -chrom keeps each region on its own chromosome; -incl confines it to mappable space.
bedtools shuffle -i dsb.sorted.bed -g hg38.chrom.sizes \
-incl mappable_k50.bed -chrom -seed 1 > dsb_shuffled.bed
Step 2 — classify the compartments in R
This is the heart of the project, and it is about thirty lines. The logic is a single truth table: a gene on the plus strand is transcribed towards higher coordinates, so a rightward fork is co-directional with it and a leftward fork is head-on. For a minus-strand gene, the reverse.
library(GenomicRanges)
library(rtracklayer)
library(regioneR)
## ---- inputs -------------------------------------------------------------
dsb <- import("dsb.sorted.bed") # break positions
genes <- import("gencode.gtf")
genes <- genes[genes$type == "gene" & width(genes) > 1e5] # long genes only
fork <- import("fork_direction.bedGraph") # score > 0 = rightward
fork$dir <- ifelse(fork$score > 0, "R", "L")
gro <- import("gro_seq_plus.bigWig") # measured, not annotated
## ---- build conflict compartments ---------------------------------------
## Intersect gene bodies with fork-direction segments, keeping both labels.
hits <- findOverlaps(genes, fork)
comp <- pintersect(genes[queryHits(hits)], fork[subjectHits(hits)])
comp$tx_dir <- as.character(strand(genes))[queryHits(hits)]
comp$fork_dir <- fork$dir[subjectHits(hits)]
## The truth table, in one expression.
comp$conflict <- ifelse(
(comp$tx_dir == "+" & comp$fork_dir == "L") |
(comp$tx_dir == "-" & comp$fork_dir == "R"),
"head_on", "co_directional"
)
## ---- count breaks per compartment class --------------------------------
ov <- findOverlaps(dsb, comp)
tab <- table(comp$conflict[subjectHits(ov)])
p_ho <- tab[["head_on"]] / sum(tab)
p_cd <- tab[["co_directional"]] / sum(tab)
message(sprintf("P_HO = %.3f P_CD = %.3f", p_ho, p_cd))
## 0.50 / 0.50 would mean geometry carries no information.
Step 3 — the same thing in Python
import pyranges as pr
import numpy as np
dsb = pr.read_bed("dsb.sorted.bed")
genes = pr.read_gtf("gencode.gtf")
genes = genes[(genes.Feature == "gene")]
genes = genes[(genes.End - genes.Start) > 100_000]
fork = pr.read_bed("fork_direction.bed") # Score > 0 = rightward
# join carries both sets of columns into one frame
comp = genes.join(fork, suffix="_fork")
df = comp.df
df["fork_dir"] = np.where(df["Score_fork"] > 0, "R", "L")
df["conflict"] = np.where(
((df["Strand"] == "+") & (df["fork_dir"] == "L")) |
((df["Strand"] == "-") & (df["fork_dir"] == "R")),
"head_on", "co_directional",
)
comp = pr.PyRanges(df)
counts = dsb.join(comp).df["conflict"].value_counts()
p_ho = counts["head_on"] / counts.sum()
print(f"P_HO = {p_ho:.3f}")
Step 4 — the statistic, with a null model that survives scrutiny
Here is where most analyses fail, and it is worth understanding exactly why rather than copying the code.
Suppose you compare your break hotspots against late-replicating domains with a simple two-by-two test and obtain an overwhelming p-value. That number is almost certainly meaningless, because your break hotspots are not a random sample of genomic positions. They are long, they sit in genes, those genes are expressed, expressed long genes replicate late, and all four properties are correlated with one another. A test that ignores this will declare enrichment for whichever of the correlated properties you happen to ask about.
The fix is a null model built by resampling from a universe of regions that share the properties you are not interested in, so that only the property you are testing is allowed to vary.
## Build a universe: mappable, gene-body, length-matched, timing-matched bins.
universe <- import("candidate_regions_matched.bed")
pt <- permTest(
A = dsb,
B = late_domains,
universe = universe,
randomize.function = resampleRegions, # draw FROM the universe,
# do not scatter at random
evaluate.function = numOverlaps,
ntimes = 1000,
genome = "hg38",
mc.set.seed = FALSE
)
plot(pt) # observed value against the permuted distribution
pt$numOverlaps$pval
The distinction between randomizeRegions and resampleRegions is the whole point. The first scatters your regions anywhere in the genome, which tests a question nobody asked — your regions are obviously unlike random genomic positions. The second draws them from a pool of plausible alternatives, which tests whether late replication specifically distinguishes the real breaks from comparable regions that did not break.
| Confounder | Why it matters | If you ignore it |
|---|---|---|
| Region length | Longer regions overlap more of everything | Every long feature appears enriched for every other feature. |
| Mappability | Unmappable sequence yields no reads and therefore no breaks | Breaks appear depleted from repeats — a property of the assay, reported as biology. |
| Replication timing | Correlated with gene length, expression and chromatin state | You cannot tell which of four correlated properties your result is about. |
| Expression level | Transcription both causes breakage and marks open chromatin | Any transcription-linked claim becomes circular. |
| GC content | Affects library efficiency and coverage uniformity | Coverage artefacts masquerade as positional signal. |
| Distance from the bait | LAM-HTGTS recovery decays steeply with genomic distance from the bait, and is far higher on the bait's own chromosome | The worst one. Anything near the bait looks like a hotspot. A null model for this assay must match distance from the bait, or the result reports nuclear proximity and nothing else. |
| Copy number | Cancer genomes are aneuploid; amplified regions give more reads | Amplifications look like break hotspots. In cancer lines this is not optional — correct for local copy number. |
If you define break clusters by scanning for regions of high break density, and then test whether break clusters have significantly more breaks than the genome average, you have proved only that you can follow your own definition. The test is guaranteed to pass.
This sounds too obvious to be worth saying, but it reappears in disguise constantly. Defining compartments using a transcription track and then testing whether breaks associate with transcription is the same error wearing different clothes, if the compartment definition already used break positions. The discipline is to keep the data that defines regions separate from the data that tests them — different replicates, different conditions, or a held-out chromosome set.
Reading the advert alongside the group's 2026 preprint on human cancer lines, the first real analytical task is almost certainly a comparison: are the head-on compartments the same between cancer types, and do their break densities differ?
That is harder than it sounds, for a reason worth being able to articulate. Cancer cell lines are aneuploid and carry their own copy-number landscape, so a region present in four copies yields more reads than one present in two, in every assay. Replication timing itself is also remodelled in cancer. So a difference in break density between an osteosarcoma line and a breast line could reflect different conflict geometry — the interesting answer — or simply different copy number and different timing programmes.
Separating those requires copy-number normalisation, matched baits, and timing measured in each line rather than borrowed from a reference. If you can say that in an interview, you have demonstrated the thing the advert is screening for: that you understand what makes the computational part of this project difficult, rather than just which tools it uses.
- The coordinate convention of BED versus GTF, and how to avoid converting by hand. (§5.1)
- The four-row truth table that classifies a region as head-on or co-directional. (§5.2 step 2)
- Why
resampleRegionsanswers a useful question andrandomizeRegionsusually does not. (§5.2 step 4) - Why distance from the bait must be matched in any LAM-HTGTS null model. (Table 5.3)
- What the circularity trap is, and how to avoid it with held-out data. (§5.2 pitfall)
- Why copy number must be normalised before comparing break density between cancer lines. (DKFZ box)
Interview and assessment preparation
Five conceptual questions and three analytical scenarios, answered at the depth the group's own papers would expect. Then the pitch, the questions worth asking them, and how to handle the one question you cannot avoid.
6.1 · What the conversation will be
| Direct group interview | Structured programme panel | |
|---|---|---|
| How you got there | Applied to this advert through the jobs portal, which is the route in Module 1 | Applied to the central graduate programme, which recruits across many groups |
| Who is in the room | Dr. Wei, probably with one or two group members | A panel of scientists, mostly from other fields |
| Typical shape | Conversation about your background, then about the project, then your questions | A short pitch of your own recent research, then discussion of a paper you were given |
| What it rewards | Specific knowledge of this project and honest awareness of your own gaps | General scientific reasoning, and the ability to explain clearly outside your own field |
| Preparation that pays | The group's 2024 paper, cold. A real opinion about it. | A rehearsed three-minute account of your own thesis, and practice reading papers critically |
Prepare for the first and the second comes largely free, because the hard part of both is being able to say something substantive about a specific piece of science. Below, the questions.
6.2 · Five conceptual questions
Why do long genes break more often than short ones?
Three properties coincide in these genes and it is their combination that matters, not any one alone.
Duration. Transcribing a gene of a megabase or more at the observed elongation rate takes many hours — comparable to or longer than the whole cell cycle in a rapidly dividing cell. So unlike a short gene, which can be transcribed in a gap between replication events, a very long gene is necessarily being read while it is being copied.
Origin paucity and late timing. The interiors of these genes are poor in replication origins and replicate at the end of S phase. Few origins means the region depends on forks arriving from outside, which must travel a long distance. A fork that travels far has more opportunity to encounter an obstacle, and arrives later, when there is less time left to recover.
Converging geometry. If forks arrive from both sides, then whichever direction the gene is transcribed in, one of those two forks is running against transcription. The head-on encounter is not a matter of chance; convergence makes it structural. This is why the largest class among the 152 mapped clusters was the inward-moving one, and why most of those overlapped replication-timing transition regions.
The evidence that transcription is causal rather than merely correlated is the promoter-deletion experiment: removing the promoter or enhancer of an RDC gene abolished the nascent transcription and the break cluster together, while replication timing did not advance — at one locus it was actually delayed. That separates the two variables about as cleanly as the system allows.
What makes this answer good rather than adequate: saying that the three explanations for fragility — length, origin paucity and sequence-driven secondary structure — are still debated, and that the group's contribution is to show that orientation discriminates between them in a way that density alone cannot.
Why is a head-on conflict more damaging than a co-directional one, and how would you demonstrate that genome-wide?
Mechanism, three parts. When a fork and a polymerase converge, the DNA between them accumulates positive supercoiling that has nowhere to escape, because both machines are pushing twist into a shrinking interval; topoisomerases become rate-limiting. Any RNA:DNA hybrid in that interval is pushed against the fork rather than displaced ahead of it, so it is stabilised into a physical block. And the fork is far more likely to reverse or collapse rather than pass, which is what converts a stalled fork into a double-strand break. In the co-directional arrangement the fork approaches from behind, twist is released ahead of both machines, and the fork can displace or wait out the polymerase.
The demonstration. This is the part that distinguishes a good answer. Break density alone is useless here, because a head-on and a co-directional region can have identical break counts and you would never know which geometry produced them. What you need is the direction of each break.
So: map breaks with an assay that preserves orientation, which is what the linear-amplification step in LAM-HTGTS buys you — each recovered end is classifiable as centromere- or telomere-oriented. Measure fork direction independently, by connecting initiation to termination zones in a high-resolution replication-timing matrix. Measure transcription direction independently, by stranded nascent transcription rather than from annotation. Then classify each break and compute the proportion lying in head-on orientation.
The prediction is specific and falsifiable: if the geometry is causal, inducing replication stress should shift that proportion towards head-on while leaving the underlying gene set unchanged. That is what was observed — the head-on proportion rose to roughly sixty per cent under aphidicolin, against roughly forty for co-directional, where fifty per cent is the no-preference expectation.
And the control to volunteer: the shift must be shown within the same loci, in the same cells, with and without stress. A comparison between different loci would confound geometry with everything else that differs between them.
Are R-loops a cause of this breakage or a consequence of it?
The honest answer begins with the group's own data, and this is the fact worth carrying into the room: in the 2024 work, roughly two-thirds of the recurrent break clusters had no detectable R-loops; about one-third had between one and nine; only four had more than ten.
That distribution rules out the easy story. If R-loops were what makes these regions fragile, they would be present at the fragile regions. They are mostly absent. So the general mechanism is the head-on geometry, and R-loops are an additional burden at a subset of sites — likely those with the sequence composition that favours hybrid formation, such as GC-skewed, G-rich stretches.
On causality. The correlational data cannot settle direction, because breakage and hybrid formation share upstream causes: both are promoted by high transcription, both by fork stalling. The experiments that would settle it are interventional. Overexpressing RNase H1 removes hybrids: if breaks at a locus fall, hybrids were contributing causally. Depleting a resolution factor such as senataxin increases hybrids: if breaks rise at the same loci, the direction is confirmed. Both should be done with the strand-resolved version of the hybrid assay, so you can ask whether the hybrid lies specifically in the path of the oncoming fork — which is the prediction the head-on model makes and a non-oriented assay cannot test.
And the methodological caveat that should come unprompted: the S9.6 antibody also binds double-stranded RNA, so every hybrid measurement requires a parallel RNase H-treated sample, and ideally confirmation by an antibody-independent method. A DRIP peak without that control is not evidence of a hybrid.
How does a transient double-strand break become a permanent copy-number change?
A break has several possible fates, and only some of them leave a permanent mark. Fast rejoining by non-homologous end joining restores the sequence with at most a small scar. Repair from the sister chromatid restores it exactly. But if the ends are instead joined using a short stretch of matching sequence found nearby, everything between those two stretches is lost — and that is a focal deletion, inherited by every descendant of that cell.
The group established this chain rather than assuming it. Inhibiting polymerase theta with ART558 in the repair-deficient background abolished the recurrent focal copy-number changes; the junctions that remained lost their microhomology signature, shifting from roughly two base pairs of microhomology towards direct joining. That is a causal demonstration that this specific pathway converts these specific breaks into these specific rearrangements.
Single-cell evidence completes it. Using Strand-seq, 118 of 302 breakpoints found in cells that had lost copy number mapped to known break clusters — so the link is visible one cell at a time, not only as a population average. And the bulk copy-number changes were enriched in late-replicating regions of constant timing, consistent with the replication environment that defines the clusters in the first place.
The nuance worth adding: polymerase theta inhibition behaved differently in wild-type cells, where recurrent copy-number changes did not change and junction recovery actually rose — plausibly because the pathway competes with intact non-homologous end joining. That is the kind of detail that shows you read the paper rather than its abstract, and it is also a genuine complication for anyone hoping the inhibitor is a simple therapeutic.
Osteosarcoma genomes contain thousands of rearrangements. How would you tell which breaks initiated the process from which are consequences of it?
This is the conceptual heart of the whole position, and it is worth naming the problem precisely. A sequenced tumour genome is a palimpsest: the final state after many cycles of breakage, repair, selection and further breakage. Mutational and structural signatures derived from it are mixtures of initiating processes and downstream consequences, and once a genome has been through chromothripsis or breakage–fusion–bridge cycles, local rearrangement density tells you more about those catastrophes than about intrinsic fragility.
The strategy therefore has to be orthogonal. Three strands.
Measure breakage directly, in cells that are alive now. Break mapping reports where the genome is being broken currently, before selection has filtered anything. Loci that are both frequently broken in the assay and frequently rearranged in patient genomes are candidate initiating sites; loci rearranged in patients but never broken in the assay are more likely consequences or selected passengers.
Explain the positions mechanistically. If a frequently broken locus sits in a head-on compartment, replicates late and is under-replicated, there is a mechanism for why it breaks, independent of its presence in any tumour. Mechanism is what converts a correlation into an argument about initiation.
Perturb and predict. This is the strongest test available. If the model is right, changing the replication or transcription environment should move break positions predictably — and the promoter-deletion experiments show this is achievable. A model that predicts where breaks will appear after an intervention is doing more than describing a pattern.
And the honest limitation to state: cell lines have already been selected, for decades, for the ability to grow in culture, and their genomes are not the genome of the tumour the patient had. Comparison against in vivo tumour models — which the advert explicitly includes — exists to address exactly this, and the comparison is a real part of the work rather than a formality.
6.3 · Three analytical scenarios
A set of LAM-HTGTS FASTQ files lands on your desk. Walk me through what you do, and what you expect to go wrong.
The steps. Read quality and adapter content first, because a failed run should be caught before it consumes a day. Then the step that differs from a normal pipeline: the information here is a junction inside a read, not the position of the read, so each read must be split at the point where bait sequence stops and the rest begins, and only the downstream portion is aligned. Reads whose bait portion does not match cleanly are discarded.
Then the three filters that matter. First, remove everything that is still germline bait — uncut or perfectly rejoined bait vastly outnumbers real junctions, and if the blocking digestion underperformed at the bench, the library will be mostly this. Second, exclude a defined window around the bait, because the majority of genuine junctions are local resection-and-rejoin events and they are not what the experiment is about; the window size must be stated because it changes the numbers. Third, deduplicate on junction position plus fragment end together: identical junction and identical end means one original molecule amplified twice, identical junction with different ends means two independent breaks at the same place. Deduplicating on position alone would delete the real signal, since recurrence at a position is exactly what is being measured.
Then normalisation, before any comparison between samples: total usable junctions, or junctions relative to bait-proximal events, so that library efficiency differences do not masquerade as biology.
What I would expect to go wrong. Most junctions piling up within a few kilobases of the bait — normal, and handled by the exclusion window. A library dominated by germline bait — a bench problem, not an analysis problem, and worth saying so rather than trying to rescue computationally. Apparent hotspots that turn out to be unmappable regions or, in a cancer line, amplified regions. And a steep decay of junction recovery with distance from the bait, which is real biology about nuclear proximity but will be mistaken for breakage if the null model does not account for it.
You find that break hotspots are strongly enriched near transcription start sites. How do you convince me that is not an artefact?
First, list what could produce this without any biology. Promoter regions are open chromatin, which is more accessible to fragmentation and often better covered. They are GC-rich, which affects library efficiency. They are gene-dense and early-replicating, and both correlate with other things. In a cancer line they may be amplified. And if they happen to lie closer to the bait, recovery is higher for reasons of nuclear proximity alone. Any of these can generate apparent enrichment.
Then address each. Restrict to mappable sequence and apply the blacklist. Match the background set for length, GC content and local copy number. Crucially, resample the background from regions that share the properties you are not testing — other transcription start sites with comparable expression, say — rather than scattering regions anywhere in the genome, which tests only whether promoters differ from random DNA, a question with a known and uninteresting answer. And match distance from the bait, which for this assay is the dominant confounder.
Then test a prediction an artefact cannot make. This is the strongest move available and it uses the assay's own strength. If the enrichment reflects transcription–replication conflict, the breaks should show an orientation preference relative to local fork direction. A coverage or accessibility artefact has no reason to be oriented at all: it would produce centromere- and telomere-oriented ends in equal numbers. So if the enrichment is accompanied by a significant orientation bias that flips with local fork direction, it is not a coverage artefact. If orientation is 50:50, I would treat the finding as technical until shown otherwise.
Finally, replicate it with a different bait on a different chromosome, and ideally with a bait-free break-mapping method such as END-seq, which has entirely different biases.
Your break data is at nucleotide resolution and your replication timing is in fifty-kilobase bins. How do you combine them without fooling yourself?
The direction of travel matters. The temptation is to smooth the timing track up to fine resolution so it can be joined to individual junctions. That invents precision the measurement does not have: a fifty-kilobase bin is one number describing fifty thousand bases, and spreading it across them creates values that were never measured. The correct direction is to bring the fine layer down — count junctions per bin — and accept that the analysis operates at the coarser scale.
Choosing the bin size. Two constraints. Biologically, a conflict zone is tens of kilobases across, so bins far smaller than that would split single mechanistic units while bins much larger would average distinct zones together; the group's use of twenty-five to fifty kilobase smoothing sits in that range for good reason. Statistically, bins must be large enough that most contain a usable number of junctions — with sparse data, very fine bins give mostly zeros and a few ones, and any test on that is driven by noise. Where the two constraints disagree, the data density usually wins, and the limitation should be stated.
Then demonstrate robustness. Repeat the analysis at two or three bin sizes. A conclusion that holds at twenty-five and fifty and one hundred kilobases is a conclusion; one that appears only at a single bin size is a bin-size artefact, and finding that out yourself is much better than having it found for you.
And the trap to name explicitly. If break positions were used to define the regions, those same positions cannot then be used to test whether the regions are enriched for breaks — the test is guaranteed to pass and measures nothing. Region definition and hypothesis testing must use separate data: different replicates, different conditions, or held-out chromosomes. I would define compartments from the replication and transcription layers only, which are measured independently of breakage, and keep the break data purely as the tested quantity.
6.4 · The three-minute account of your own work
Whichever format applies, you will be asked what you have done. The structure that works is fixed and short:
- The question, in one sentence Not the field, not the background — the actual question your work addressed.
- Why it mattered One sentence. What was not known, or what could not be done before.
- What you did Your methods, in the first person singular where that is accurate. If the work was computational, say what the input and output were.
- What you found The result, including its size or direction. A number is better than an adjective.
- What was wrong with it Do not skip this. One genuine limitation, and what you would do differently. Candidates who present flawless work are either not believed or not trusted to notice problems. A stated weakness is the strongest part of the account.
- The bridge One sentence connecting it to this project. For a thesis on computational drug discovery, the honest bridge is the final chapter of this project — the move from a mechanism to a druggable dependency — not a forced claim of methodological overlap.
6.5 · Questions worth asking them
The questions you ask are assessed, and generic ones are a missed opportunity. Each of these demonstrates something specific about what you have understood.
- “Which bait positions are you planning to use in the human lines, and how are you handling the proximity bias when comparing cancer types?” — shows you understand the assay's central limitation and that comparisons require matched baits.
- “Cancer lines already carry their own repair defects. Does that help break capture, or does it make the backgrounds non-comparable?” — shows you have thought about why the mouse work used an engineered repair-deficient background, and that transferring the approach is not trivial.
- “Is the human cancer-line resource from the preprint the starting point, or would this project generate its own break maps?” — shows you have read beyond the published papers, and asks a real question about what year one looks like.
- “Since replication timing is itself remodelled in cancer, would timing be measured in each line rather than taken from a reference?” — a genuinely sharp methodological question.
- “How is the work split between bench and analysis, and would I be doing both?” — practical, legitimate, and it matters to you.
- “What would make you consider the project successful after three years?” — tells you how they think, and whether the project is scoped.
6.6 · The question you cannot avoid
Somebody will ask why a pharmacist is applying for a genome-instability PhD. There are three ways to answer and only one of them works.
Do not minimise it. “Pharmacy is really quite close to molecular biology” is not true, and claiming it invites a question you cannot answer. Do not over-apologise either — a candidate who treats their own degree as a liability has already conceded the point.
The answer that works is a plain sequence of facts with a direction. You came from drug development, including a thesis on computational approaches to discovering drugs. You became interested in where the targets come from rather than how they are screened, which led you to DNA-damage-response pharmacology, which led you to this project — where the endpoint is a damage-response dependency specific to a tumour type. You taught yourself the genomics you were missing, and here is the analysis you built, which you can talk about in detail. The gap you still have is wet-lab sequencing library experience, and you would expect the first year to be largely about closing it.
It gives a coherent reason for the trajectory, which is what the question is really asking. Nobody minds an unusual background; they mind an unexplained one, because an unexplained one suggests the candidate is applying everywhere.
It also puts a concrete artefact in the conversation — the analysis — which moves the discussion from what your degree says to what you can do. And it names your own gap before they have to, which is the single most reliable way to be trusted about everything else you claim.
One more thing in your favour, worth knowing but not worth announcing: this project's final chapter is pharmacology. Selectivity, therapeutic window, resistance, combination toxicity. In a group whose published mechanism already runs through a drug used as a scalpel, somebody who thinks that way is useful. Let that emerge from how you discuss the work rather than from a claim about your degree.
Do not claim familiarity you do not have. If you have never run a sequencing library, say so. The follow-up question in this field is always technical and specific, and being caught out on the first one costs you the rest of the conversation.
Do not present the group's results back to them as news. Reference their work precisely — “your 2024 paper showed the head-on proportion shifts to about sixty per cent under aphidicolin” — and then say something of your own about it. A summary with no opinion attached reads as revision rather than interest.
Do not invent an opinion to seem critical. If asked for a weakness in the paper, the two safe and real ones are that the repair-deficient background amplifies break frequencies and may distort the pathway balance, and that fork direction derived from population timing cannot speak to single cells. Both are limitations the authors themselves address, which is why raising them is a discussion rather than an accusation.
- Can you explain why long genes break, in ninety seconds, without notes? (Q1)
- Can you say why orientation data is required to prove the head-on model? (Q2)
- Do you remember what fraction of break clusters lack R-loops, and why that matters? (Q3)
- Can you trace a break to a focal deletion and name the enzyme and its fingerprint? (Q4)
- Can you state the distinction between where a genome broke and where it ended up rearranged? (Q5)
- Can you name the dominant confounder of the break-mapping assay, unprompted? (Scenario 2)
- Have you rehearsed your three minutes out loud, including the limitation? (§6.4)
Sources this guide was built from
- DKFZ job posting, PhD Student — DNA Break Signature in Cancers, Kennziffer 2026-0211 — jobs.dkfz.de/de/jobs/168906, and the earlier round, Kennziffer 2026-0144 — jobs.dkfz.de/en/jobs/168718
- Junior Research Group Brain Mosaicism and Tumorigenesis, group page — dkfz.de/en/brain-mosaicism-and-tumorigenesis
- Wei et al., Linear interaction between replication and transcription shapes DNA break dynamics at recurrent DNA break clusters, Nature Communications 2024 — nature.com/articles/s41467-024-47934-w
- Recurrent DNA break clusters drive replication-stress-induced copy number variants and genome diversification, Nature Communications 2026 — nature.com/articles/s41467-026-71790-5, and the preprint — biorxiv.org/content/10.1101/2025.09.01.673480v1
- Wei et al., Long neural genes harbor recurrent DNA break clusters in neural stem/progenitor cells, Cell 2016 — sciencedirect.com/science/article/pii/S0092867416300629
- Induction of recurrent break cluster genes in neural progenitor cells differentiated from embryonic stem cells in culture, PNAS 2020 — pnas.org/doi/abs/10.1073/pnas.1922299117
- Hu et al., Detecting DNA double-stranded breaks in mammalian genomes by linear amplification-mediated high-throughput genome-wide translocation sequencing, Nature Protocols 2016 — nature.com/articles/nprot.2016.043
- High-resolution Repli-Seq defines the temporal choreography of initiation, elongation and termination of replication in mammalian cells, Genome Biology 2020 — genomebiology.biomedcentral.com/articles/10.1186/s13059-020-01983-8
- Abu-Odeh et al., WWOX, the common fragile site FRA16D gene product, regulates ATM activation and the DNA damage response, PNAS 2014 — pnas.org/doi/10.1073/pnas.1409252111
- Tumor suppressor genes within common fragile sites are active players in the DNA damage response, PLoS Genetics 2016 — journals.plos.org/plosgenetics
- WWOX promotes osteosarcoma development via upregulation of Myc, Cell Death & Disease — nature.com/articles/s41419-023-06378-8
- DNA replication timing reveals genome-wide features of transcription and fragility, Nature Communications 2025 — nature.com/articles/s41467-025-59991-w
This is a study guide, not a protocol and not careers advice from the institution concerned. Quantitative parameters — drug concentrations, bin sizes, fraction counts, read depths — are quoted from the published work cited above to make the reasoning concrete, and must be checked against the primary methods before use. Details of the posting, including its deadline and requirements, were read on 16 October 2026 and can change; verify them on the DKFZ portal before relying on them.
Compiled 16 October 2026 · designed for A4 printing via the browser's print-to-PDF function.