How to get Upwind jobs after its $400M Series C

What does Upwind's $400M Series C mean for hiring?

Upwind's $400 million Series C means the company is about to hire hard. It has said it plans to more than double its team, with hiring focused on AI research and go-to-market. The round was announced on October 28, 2026, led by Bessemer Venture Partners and TCV, and it values the cloud security startup at $3.8 billion. There was a twist, too. Reports on the deal say Datadog tried to buy Upwind but didn't offer a premium over that valuation, so the founders turned it down and took the money instead. For job seekers, that choice matters more than the headline number. A company that turns away a buyer is betting on building its own product, and building takes people.

The speed is what stands out. Upwind was founded in 2022. It raised $250 million at a $1.5 billion valuation at the start of 2026 and has more than doubled that valuation in about nine months. Total funding is now above $800 million. The company has roughly 600 employees across the US, Israel, Europe and Asia. Its headquarters is listed in San Francisco, while much of its research and engineering runs out of Tel Aviv. Doubling 600 people won't happen as a slow trickle of postings. It means dozens of openings at once and recruiters juggling hundreds of applicants per role. Screening will lean heavily on keyword filters and quick skims, because nobody has time to read every CV twice.

Upwind has also said where the money will go: AI sensors for endpoints, scanners for AI agents and skills, a rebuilt inventory graph that maps how cloud assets connect, and expansion into identity, data and AI security. Its AI Labs research unit, launched in September, and its purchase of the Israeli startup Aegis point the same way. Read together, that's a hiring roadmap. If your background includes identity and access management, data security, AI threat research or endpoint telemetry, you're more relevant to this company now than you were in the spring. The downside is that generic security CVs will get lost. At a fast-growing startup, the winning CVs use the posting's own language. A longer list of certifications won't do that job.

Which Upwind jobs are likely to open in Tel Aviv and the US?

Expect the biggest wave in Tel Aviv research and engineering and in US go-to-market roles, with security engineering spread across Upwind's global offices. The company's careers listings earlier in 2026 showed a clear pattern. Tel Aviv had the research-heavy titles: Cloud Security Researcher, Senior Vulnerability Researcher, Threat Security Researcher, Research Software Engineer and AI Engineer. It also had student positions such as Security Analyst and Cloud Monitoring Engineer. Security Engineer postings showed up in the US, Belfast, Singapore and Australia, which suggests regional security work sits close to customers. Openings change every week, so treat this as a map of role types, not a list of live jobs. Check the company's own careers page before you tailor anything.

The company's focus on AI research tells you which Tel Aviv roles will grow first. Upwind AI Labs studies threats to AI systems and AI-driven workflows, and the roadmap includes scanners for AI agents. That's research work: working out how agent frameworks call tools, finding prompt-injection routes into cloud permissions, and writing detections for abuse that didn't exist two years ago. On the US side, go-to-market means solutions engineers, sales engineers, account executives and customer success managers. They need to talk Kubernetes with a platform team in the morning and return on investment with a CISO after lunch. Pre-sales engineers with real hands-on security experience are some of the hardest hires for any cloud security vendor. Their CVs need to show both skill sets clearly.

Student positions are worth a mention, because Israeli security startups use them as a real hiring pipeline. One student Security Analyst role at Upwind asked for cloud networking, Linux and Windows knowledge, plus familiarity with Python, Bash, Docker and Kubernetes. The job centered on protecting Kubernetes and container environments and building detection mechanisms. If you're finishing a degree or just out of military service, that's a realistic way in. My advice goes against what many candidates do: pick one role type and apply to it well. If you send the same CV to Researcher, Analyst and Solutions Engineer listings at one company, it looks like you don't know what you want. The same recruiter may well see all three applications side by side.

What should a cloud security engineer resume show to get hired at Upwind?

A cloud security engineer resume aimed at Upwind needs three things: hands-on runtime security in Kubernetes and the cloud, the CNAPP vocabulary the job ads use, and numbers that prove your work changed something. Upwind describes itself as a runtime-powered CNAPP (cloud-native application protection platform). It's built on eBPF-based sensors, with agentless posture scanning, real-time threat detection and API security on top. Every one of those terms is a likely keyword. If you've worked with CSPM, CWPP, container image scanning, Kubernetes admission control, Falco-style runtime rules or eBPF tracing, list them in your skills section. Then name them again in the bullets where you used them. A parser rewards both: the skills list gives the keyword match, and the bullets give a recruiter context they can believe.

Next, show impact instead of activity. "Responsible for cloud security monitoring" tells a reviewer nothing. "Cut mean time to detect container escapes from six hours to twenty minutes by writing eBPF-based runtime rules across 1,400 nodes" shows exactly what you'll do on day one. Use your real numbers, never invented ones. If you can't share figures, show scale instead: clusters, cloud accounts, workloads, or alerts triaged per week. Upwind's whole pitch is that runtime context separates real risk from noise. So bullets showing you cut false positives, ranked vulnerabilities by real exploitability or closed misconfigured IAM paths speak directly to that pitch. For more on writing CVE evidence and tool names into bullets, see our guide to what belongs on an application security engineer resume.

Here's an opinion I'll stand behind: at a runtime security company, one concrete incident beats a wall of certifications. CKS, AWS Security Specialty and OSCP are useful tie-breakers and you should list them, but in one compact line, not at the top of page one. Open with a short profile that names your cloud (AWS, Azure or GCP), your Kubernetes platform (EKS, GKE or AKS), your languages (Python and Go come up often in this field) and the problem you solve best. Keep it to one or two pages in a single column, with no skill bars. If you're starting from scratch, our cybersecurity CV builder puts your certifications, your real SIEM and EDR stack and your incident work where reviewers look first, without breaching an NDA.

How do you tailor your CV to an Upwind job description and pass screening?

You pass screening by using the exact language of the specific posting, in a format an applicant tracking system can read, and by proving every required skill somewhere in your experience. Most tracking systems pull your CV apart into fields, and recruiters then search and filter by keyword. If the ad says "Kubernetes" and your CV says "container orchestration", a person might connect the two, but a filter won't. Acronyms work the same way: write "cloud-native application protection platform (CNAPP)" once, then use the short form. Skip two-column templates, text boxes, contact icons and skills shown as images. Those are the parts that most often come out scrambled or missing when a parser reads your file, and the recruiter never knows what you meant.

The routine takes about twenty minutes per application. Copy the full text of the job description, not just the title. Mark every hard skill, tool and responsibility, then check each one against your CV. Is it there? Is it in the posting's wording? Is a bullet backing it up? Add anything that's missing but true. Leave out anything you don't actually have, because interviewers at a research-heavy security company will spot it within minutes. This is where automated feedback saves real time. Paste the posting into HRLens's free CV analysis with your CV. You'll get a score out of 100 that includes an ATS compatibility rating, plus a list of skills the job asks for that your CV doesn't show yet.

Don't stop after the first pass. Each analysis also creates ATS-friendly rewrites of your CV in six templates that use the job's keywords, so you start from a clean draft instead of a blank page. The full fix list, the "why you might be rejected" breakdown and an estimate of interviews per ten applications come with the paid Full Analysis at $3.99. Whatever tool you use, read the final version aloud before you send it. Keyword-stuffed CVs pass the filter and then fail the human reader. Upwind's hiring managers are practitioners, and they'll notice when "eBPF" appears six times but never in a sentence about something you built. Aim to cover every requirement once, with proof, instead of repeating the same keyword.

Should you send a Hebrew, English or bilingual CV to Upwind?

Send an English CV to Upwind for almost every role, including jobs based in Tel Aviv. Israeli cybersecurity startups work in English: the job ads are in English, the product and its documentation are English-first, and your CV may be passed to a hiring manager in the US or Europe. A Hebrew CV can make sense for a student position you found on a Hebrew-language job board, or when a referral specifically asks for one. Treat that as the exception. Even then, keep technical terms in English. Nobody in Israeli hi-tech writes Kubernetes, eBPF or CSPM in Hebrew letters. A recruiter searching the tracking system for those words won't find you if you've transliterated them.

Military service is where Israeli candidates most often undersell themselves on an English CV. A line like "Served in Unit 8200, 2018–2021" means a lot to a Tel Aviv recruiter and almost nothing to a US hiring manager or a parser. Describe the experience, not just the unit name. Include the kind of systems you worked on, in as much detail as your clearance allows, along with team size, tools, languages and results you're allowed to share. "Led a team of five building Python detection tooling for large-scale network telemetry" works for both audiences. Check names and dates as well. Hebrew-to-English spellings vary, so use exactly the spelling on your LinkedIn profile, because recruiters will compare the two.

If you do need a Hebrew version, the file format matters as much as the wording. Right-to-left text exported from some design tools or word processors can come out in reverse order or with broken punctuation, and a strong CV turns into gibberish in a recruiter's search results. Build both versions from the same content so your dates, titles and numbers match. HRLens's AI CV builder writes Hebrew CVs in Hebrew and exports them right-to-left. The analysis also reads Hebrew files, including scanned images through OCR, so you can check each version before it goes out. Then apply early. In a hiring wave this size, a new opening gets the most attention in its first days, before the pile of applicants builds up.

Frequently asked questions