Resume example for tech jobs in Israel, annotated

A resume example for tech jobs in Israel is one page with four sections: contact details, a three-line summary, experience in reverse chronological order, and a technologies section in exact product names. Every experience line opens with a past-tense verb and ends with a measurable result. The annotated example below is a backend developer with four years.

Dana Cohen is invented. No such person, and her employers are described rather than named — deliberately, so the example cannot be copied and sent as is. The structure and the reasoning are the real parts.

There is no file to download and no template here. Templates arrive on a recruiter's screen looking like the forty others that came in that week, which is the only reason this page is text you can select rather than a document you can fill in.

Resume example: a backend developer with four years

Contact details

Dana Cohen
Backend Engineer
Tel Aviv, Israel · 054-0000000 · dana.cohen@example.com
linkedin.com/in/dana-cohen · github.com/dana-cohen

Why it looks like this. The job title sits under the name because that is the string a recruiter types into the search box. Contact details live in the body of the document, not in a header — Greenhouse, the applicant tracking system many Israeli tech companies run, lists contact details inside a header, footer or text box as one of the things that break its parser (updated 2 March 2026, checked 2 September 2026). City and country, not a street address. No photo, no ID number, no date of birth, no marital status.

Summary

Backend engineer, four years, Python and Go, on services handling high traffic in fintech. Led the split of a monolithic payments service into three services; median response time dropped from 800ms to 210ms. Two years working directly with a product team, including defining client-facing APIs.

Why it looks like this. Three lines, not a paragraph, and one real number inside them. The CV guide from Gotfriends, one of the larger recruitment agencies in Israeli tech (published 22 August 2022, checked 2 September 2026), recommends opening with five or six bullets covering field, years, stack and achievements. Same information, different shape. What is banned either way: "highly motivated", "team player", "passionate about technology". Unverifiable claims, sitting in the only lines that get read for certain.

Experience

Backend Engineer · fintech startup, ~60 people · 2024–present

Split a monolithic payments service into three services; median response time dropped from 800ms to 210ms.
Built one integration layer for three payment providers; onboarding a new provider went from two weeks to two days.
Raised automated test coverage on the service from 34% to 81%; no billing regression has reached production since.

Software Engineer · enterprise software company, ~300 people · 2022–2024

Wrote the notifications service that sends ~2M messages a day; replaced a scheduled run with a job queue and cut wait time from 11 minutes to under one.
Led a migration of 40 tables to PostgreSQL with no downtime.
Onboarded two new engineers through their first two months.

Why it looks like this. Every line opens with a past-tense verb — split, built, wrote — and never with "responsible for". "Responsible for payments infrastructure" describes a job description; "split a monolithic payments service into three" describes what happened because you were there. One number per line, and where there is no honest number, scope instead ("two engineers"). Never invent the number. A line without one beats a number you have to explain in the interview.

Three bullets per role, not seven. The fourth and fifth are always weaker than the first three, and they pull the eye down the page instead of forward.

Education

B.Sc. Computer Science, Ben-Gurion University of the Negev, 2019–2022
Final project: a Hebrew autocomplete engine for search, in the NLP lab.

Why it looks like this. At four years of experience, education drops below experience. The final project survives only because it is technical and relevant. GPA comes out unless it is excellent and you are still in your first year or two.

Military service

IDF, technology unit · 2016–2019
Software testing and automation in a team of four; built a test harness running across three systems in parallel.

Why it looks like this. One line with content in it, not a unit number on its own. For a resume read outside Israel this section works differently, and we wrote about presenting Israeli military service to a non-Israeli reader separately.

Technologies

Languages: Python, Go, TypeScript
Infrastructure: Docker, Kubernetes, AWS (ECS, RDS, S3)
Data: PostgreSQL, Redis, Kafka
Tooling: Git, GitHub Actions, Datadog

Why it looks like this. Exact names, not categories. PostgreSQL rather than "databases", Kubernetes rather than "container orchestration" — the recruiter is searching for the string that appears in the ad, and the ad is written in product names. Four labelled lines scan faster than one long comma run. And one rule: do not list a technology you could not talk about for ten minutes. The guide from Log-On, a hi-tech recruitment firm in Ramat Gan (published 11 November 2025, checked 2 September 2026, in Hebrew) puts it in the same words.

Resume structure: the order of the sections, and why

Contact, summary, experience, education, military service, technologies, languages — and in tech the technologies section sometimes climbs above education, because it is the part that gets searched.

One rule sits behind the order: whatever is most relevant to this specific job goes up. Three cases where the order changes:

New graduate or career changer — education and bootcamp move above experience.
Your most recent role is not relevant to the job — a "Relevant experience" section before "Additional experience", each in reverse chronological order.
Freelance across several clients — one heading line ("Freelance, backend development, 2023–2025") with two or three projects under it, rather than seven four-month jobs.

What does not go in at all: "References available on request", a career objective, a page-long course list, and hobbies — unless the hobby is genuinely the job (an open-source project, a security competition).

Resume format: what happens before a person opens the file

The file is read twice: once by software that breaks it into fields, and once by a person. The first read is the one that fails silently.

Applicant tracking systems do not "reject" resumes. They parse, tag and make the pile searchable. A file whose parse breaks does not disappear — it simply does not come up in the search the recruiter just typed, and from your side those two outcomes look identical.

This is one of the few points here with vendor documentation behind it rather than opinion. Greenhouse publishes what breaks its own parser (updated 2 March 2026, checked 2 September 2026): graphics, images and word art; a resume uploaded as an image; tables; headers and footers; contact details inside a header or text box; two-column layouts; and files over 2.5MB. The formats it does read are doc, docx, pdf, rtf and txt.

What follows from that:

A PDF exported from a text editor, not a scan or a screenshot. Two-second check: open it and try to select a line. If it does not highlight, it is a picture.
One column. The handsome template with the dark sidebar is exactly the case the documentation warns about.
No tables and no icons, including in the skills list.
No photo.
A filename a human can read: Dana Cohen - Backend Engineer.pdf, not CV FINAL v3.pdf.

On the number that circulates: the claim that 75% of resumes are rejected by automated systems has no source you can reach, and we wrote about that separately.

Before and after: three bullets tailored to one job ad

The example above is the base version. Now say Dana applies to an invented ad asking for Go, event-driven systems, Kubernetes in production, and third-party integration work.

Three of her lines, before and after. No fact changed — only the wording, the order and the emphasis.

Before: Split a monolithic payments service into three services; median response time dropped from 800ms to 210ms.
After: Split a monolithic payments service into three Go services running on Kubernetes in production; median response time dropped from 800ms to 210ms.

Before: Built one integration layer for three payment providers; onboarding a new provider went from two weeks to two days.
After: Led third-party integration with three external payment providers behind a single interface; onboarding a new provider went from two weeks to two days.

Before: Wrote the notifications service that sends ~2M messages a day; replaced a scheduled run with a job queue and cut wait time from 11 minutes to under one.
After: Rebuilt the notifications service as an event-driven system on a message queue (Kafka), at ~2M messages a day; wait time dropped from 11 minutes to under one.

The difference is three words per line, all of which were true before. That is the whole of tailoring: describing what you already did in the words the ad used. What it is not: adding a technology you have never touched. If Dana never used Kafka, the third line stays as it was.

Manager resume: what changes in the example

A manager's lines stop describing what you built and start describing what happened to the team and the product.

The technologies section drops down the page and shortens. It stays — an engineering manager who cannot name the stack is a problem — but it is not the headline.
Every experience line carries scope: how many people, how many teams, what budget, which system you owned. "Managed a team of six, two of them senior, on a service used by 40 enterprise customers."
One line about people. Hiring, mentoring, attrition. "Hired four engineers in eighteen months; one left" beats any description of management style.

Systems analyst resume: what changes in the example

An analyst is hired for what they understood, not what they built.

The summary names a domain, not a stack. Insurance, fintech, health, logistics — domain is what shortens ramp-up, and it is what is being searched for.
Lines start with an analysis verb: mapped, specified, defined, translated a business requirement into a spec. And they end with what came out of it.
The technologies section becomes tools and methods: SQL, BPMN, Jira, Confluence, BI tooling, methodology. SQL at the level where you can actually write a query is a real asset here — say so explicitly.

QA resume with no experience: what fills the gap

With no employment history, the section that takes its place is projects.

Write the course like a job: program name, hours, and what was actually built. "Software testing course, 400 hours; final project: an automated suite covering 12 flows on an e-commerce site."
Two or three real projects with links. A site you tested and filed bugs on, a test plan you wrote, a Selenium or Playwright suite on GitHub. One link beats ten lines of description.
Earlier work is not deleted — it is translated. Support desk, waiting tables, a command role: precision, working to a procedure, writing reports, tolerance for repetition. Testers use all of those. Write them as a line with scope, not as a personality trait.
What not to write: "strong attention to detail". Everyone writes it, and in this role of all roles it reads as a claim standing in for evidence.

New graduate resume: what a fresh B.Sc. does

A new graduate with no employment history flips the order: education moves up, right after the summary.

The degree gets detail, not one line. Relevant coursework (not all of it), a final project in one sentence saying what was built and in what, and substantial course projects.
GPA goes in if it is above roughly 85, and comes out after two years in the market either way.
A job held during the degree goes in, even outside tech. Someone who worked and studied at once has said something about themselves without writing it.
A student role, internship or a course project with a real client is worth more than everything else combined, and moves above the degree the moment it exists.

What already exists, and what each of them does better

We read what was already out there before writing this. All of it checked 2 September 2026. Two of the three below are in Hebrew only.

Source	What it does better than this page	Where it stops
The AllJobs CV centre	A complete example as text on the page, free, from the site where the jobs actually are	An example with no annotations — it shows what it looks like, not why
The Coral Technologies guide (published 10 November 2024)	Six examples for six different roles — full stack, DevOps, data, mobile, security, backend	Does not touch tailoring to a specific ad, or the format the parser reads
Jobseeker (updated 18 June 2025)	Clean consistent layout without fighting Word, and a builder that produces the file for you	The examples are paid templates, some of them two-column — exactly what the documentation above warns against

What to do now

Open your resume next to the example and compare section against section. The first gap is almost always the summary.
Rewrite five experience lines — past-tense verb at the front, a number or a scope at the end. Five, not all of them.
Replace categories with product names in the technologies section.
Export a PDF, open it and try to select a line. If it does not highlight, start again from a text file.
Take one real ad and do the before-and-after on three lines. Fifteen minutes, and you know whether your document is flexible or frozen.

Step five is the one that repeats. It costs about a quarter of an hour per job, and after four jobs most people stop and go back to sending the same file — and we wrote about why even a tailored file is not enough. Step five is why we built Tagishoti: it takes the resume you already have and tailors it to each job separately, out of what is written in it. It does not invent experience, skills or achievements that were not there, and it does not write you a resume from scratch — that still needs you, or a human writer.