Meera spent her first three years after college running help-desk queues, and she kept noticing one thing: the people who got interesting international offers all seemed to own a visible, specific skill. For her, that skill turned out to be a corner of security work that some teams call DetectionOps. This story follows how she approached it as a career project, and what any reader considering a technical career, at home or abroad, can learn from the way she built evidence of her ability. It is general career information; for anything concerning visas or work authorisation, always consult official government sources and qualified advisers.
Finding a skill with a clear shape
Meera began by reading the Ops Atlas entry on DetectionOps, which frames detection engineering as software delivery for alert logic: each rule starts as a requirement drawn from threat knowledge, becomes code, gets tested and reviewed, ships by pipeline, and is watched, adjusted and finally switched off. The Atlas is frank that the name is an overlapping label rather than an official standard, so she also searched for detection engineering and detection-as-code, which is how most job descriptions phrase it.
That honesty shaped her plan. Instead of putting a trendy word on her profile, she decided to list demonstrable habits: writing rules in a repository, writing tests, explaining trade-offs. Recruiters in any country can read those.
Building the foundations at home
Her first month was modest. She set up a free Git repository, wrote a handful of rules for a home lab, and added an automatic syntax check. The Atlas notes that a small lab needs very little: version control, a couple of scripts, a runner and an API connection. She kept notes in a plain document called “decisions”, where each entry recorded what she changed and why.
By month two she had learned that a rule without a test is only an opinion. She wrote pairs, one event the rule must catch and one lookalike it must ignore, and she learned to base them on a written requirement instead of the query itself, to avoid tests that pass by default.
Learning to speak in numbers
Interviewers, Meera later said, cared less about any particular tool than about whether she could describe outcomes with figures. She had studied the Atlas’s illustrative month, then reproduced the arithmetic on her own lab data: precision per rule, the share of rules with tests, and the minutes an analyst burns on each genuine finding. That habit of counting translates across roles, borders and industries.
She also practised being sceptical of tidy percentages. When she saw a vendor-style claim of ninety percent framework coverage, she remembered the Atlas’s distinction between a mapping and measured coverage, and in interviews she said she would ask which behaviours had been emulated and when. Interviewers often respond well to that kind of question because it shows you understand what evidence means.
The mistakes she made on purpose, and learned from
Meera deliberately made a few errors in her lab so she could explain them later. She edited a rule directly on the monitoring console and watched the next automated deployment overwrite it, which taught her why every change belongs in the repository. She imported a large public rule set and counted how many alerts it produced against her small lab, which taught her that a community library is a reading shelf, not a configuration. She added a filter to quiet a noisy rule and then wrote a test describing what the filter now ignored, giving it an owner and an expiry date.
Each mistake became a short paragraph in her notes and, later, a talking point. Hiring managers tend to trust candidates who can describe a failure precisely and explain what the process changed afterwards. It shows judgement, and it costs nothing but a little honesty.
The skills list she ended up with
- Reading and writing rules in at least one query language and one portable format.
- Using Git, code review and automated checks as daily tools.
- Writing paired tests and recording accepted blind spots.
- Pinning and managing toolchain versions, after seeing how mismatched releases can break builds.
- Reporting four or five metrics honestly, including precision and validated coverage.
- Communicating with colleagues in incident handling and data engineering about misses and missing logs.
Industry surveys helped her explain why the role matters. A 2025 survey of 264 practitioners found only forty-five percent could reliably measure how well their detection worked, and seven in ten blamed limited time or resources. Meera framed that as an opportunity: employers need people who make measurement cheap and routine.
Presenting the evidence
When she assembled a portfolio, she resisted the urge to show a long list of rules. She showed a short repository with a readable history, a one-page note on a rule’s requirement and blind spots, test results, and a monthly metric summary. Anyone reviewing it could follow the whole lifecycle in ten minutes. The Atlas’s five-level maturity ladder gave her a vocabulary: her lab sat at the versioned and tested levels, and she was honest that she had not yet reached validated coverage at team scale.
That candour mattered. She described a thirty, sixty and ninety day plan she would follow in a new role: export rules and add checks, then write tests for the noisiest rules, then trial shadow mode and a first emulation. A concrete plan, even a modest one, says more about readiness than a list of buzzwords.
A note on moving between countries
Meera eventually considered opportunities abroad. Rules for work authorisation differ by country and change often, so she treated official sources as the only reliable guide and never relied on forum summaries. Readers researching that side may find it useful to browse structured overviews such as this employment residence visa page for Sri Lanka or this one for a professional residence category, which show the kind of requirement headings an official process tends to list. These are informational examples, not recommendations or advice for anyone’s situation.
What her story suggests for you
The lesson is not that everyone should chase one trendy discipline. It is that a clear, evidence-backed skill travels. Choose something with a visible lifecycle, practise it in a safe environment, measure your results, and keep a record of your decisions. If the label changes, as labels do, the habits stay useful.
Start small this week: create a repository, write one rule and its two tests, and note what you would change next. Then repeat. Meera’s first offer arrived long after the third repetition.