{"id":2499277,"url":"https://alion.io/job/easysend-senior-devops-engineer","title":"Senior DevOps Engineer","company":{"id":2788081,"name":"EasySend","domain":"easysend.io","url":"https://alion.io/company/easysend","size_band":"11-50","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Comeet","truth_index":null},"role":"DevOps","role_family":"DevOps","seniority":"senior","employment_type":"full_time","work_mode":"hybrid","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["Tel Aviv, Israel"],"countries":["IL"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":{"min_usd":72000,"max_usd":200000,"period":"year","method":"global_role_cell_scaled_by_country","sample_n":3074},"experience_years_min":6,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"AI Agents","optional":false},{"name":"Amazon EKS","optional":false},{"name":"ArgoCD","optional":false},{"name":"AWS","optional":false},{"name":"Calico","optional":false},{"name":"CI/CD","optional":false},{"name":"Cilium","optional":false},{"name":"CircleCI","optional":false},{"name":"Claude Code","optional":false},{"name":"Cloudflare","optional":false},{"name":"Cursor","optional":false},{"name":"DNS","optional":false},{"name":"GitHub Actions","optional":false},{"name":"GitOps","optional":false},{"name":"Grafana","optional":false},{"name":"Helm","optional":false},{"name":"IAM","optional":false},{"name":"Jenkins","optional":false},{"name":"Karpenter","optional":false},{"name":"KEDA","optional":false},{"name":"Kubernetes","optional":false},{"name":"LLM Guardrails","optional":false},{"name":"Loki","optional":false},{"name":"PagerDuty","optional":false},{"name":"Prometheus","optional":false},{"name":"Python","optional":false},{"name":"Self-Healing","optional":false},{"name":"Service Mesh","optional":false},{"name":"SIEM","optional":false},{"name":"SOPS","optional":false},{"name":"Temporal","optional":false},{"name":"Terraform","optional":false},{"name":"Go","optional":true}],"status":"live","first_seen_at":"2026-09-25T09:33:26Z","employer_posted_date":"2026-09-25","last_verified_at":"2026-10-17T01:04:31Z","board_verified":true,"closed_at":null,"days_open":21,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":21},"description":"Description\nEasySend is a no-code platform for building and optimizing digital customer journeys in insurance, banking, and financial services. Our platform turns paperwork-based processes into revenue-generating customer engagements for some of the largest financial institutions in Israel, the US, Europe, and APAC.\nBehind that surface, our infrastructure is split the way our customers are. Enterprise customers demand isolation and get it: a dedicated single-tenant environment each, down to their own compute, data stores, identity provider, and sometimes encryption keys we cannot access. Lower-tier customers run on shared multi-tenant infrastructure. More than fifty production environments across six AWS regions, all from one GitOps pipeline.\nThat split is what makes this role heavy. On the shared platform, a single change is instantly global; on the dedicated fleet, it must land correctly everywhere before anyone feels it. Every new customer adds load and cost in a straight line - your job is to break that line, making the platform carry its own weight through self-service, automation, and AI agents, not more hands. Nobody sits between you and the customer.\nResponsibilities\nBoth tenancy models, as one system. Terraform, Helm, and ArgoCD delivering to shared and dedicated environments alike. You own the pipeline and the guardrails on it: progressive rollout, blast-radius containment, and drift detection that catches a mistake before a customer does.\nEfficiency and cloud cost. Dedicated infrastructure per customer makes unit economics an engineering concern, not a quarterly finance exercise. You own attribution, right-sizing, spot strategy, and autoscaling that actually scales down - and you defend efficiency as a design constraint on every new deployment.\nTurning operations into product. Onboarding, version rollouts, and config changes are tickets today; they should be self-service and boring. You decide what gets automated, what goes back to the owning team, and what still needs an expert.\nScale under real load. Temporal, KEDA queue-based autoscaling, and Karpenter are live and still maturing. You own how the platform grows and shrinks against real traffic, and what that costs per customer.\nSecurity engineering for regulated customers. KMS-based key management, SIEM pipelines, WAF policy, certificate and secret lifecycle, per-customer SSO, vulnerability remediation, and turning penetration test findings into shipped fixes. Our customers are banks, insurers, and health funds. Their auditors are effectively part of our roadmap.\nAI-driven operations. Our infrastructure repositories are already built for agentic work, with an internal harness of shared skills and agents. You inherit it, extend it, and push it into places it does not reach yet: triage, rollout verification, cost anomaly investigation, log analysis, and the long tail of operational work that has never been worth a script.\nReliability of what you ship. You are on call for your own systems, paged through PagerDuty against alerts you own.\nRequirements\n6+ years in DevOps, including production ownership of Kubernetes at meaningful scale. EKS preferred.\nOperating a fleet, with infrastructure as code. You have run many similar-but-not-identical environments with Terraform, and felt what happens when a change has to reach all of them. You have designed modules other people build on, and you have recovered state when it went wrong.\nGitOps in production. You have operated ArgoCD, or an equivalent GitOps controller, running automated sync with pruning and self-healing enabled, and you understand exactly how much power that hands to a single commit.\nDeep AWS and Cloudflare as a production edge. You have run AWS at the account, network, and IAM level rather than consumed it, and you have operated Cloudflare in production: WAF policy, origin protection, DNS, and rate limiting.\nYou treat cloud cost as an engineering metric you own. You have measured it, attributed it, and brought it down - through right-sizing, spot, autoscaling, storage lifecycle, or architecture - and you can talk about what you saved and what it cost you in complexity or risk to save it.\nPython and Bash as an engineer, not a scripter. Much of the leverage in this role comes from tooling you write yourself.\nYou have served regulated enterprise customers. Financial services, insurance, or healthcare - environments where penetration tests, security questionnaires, encryption requirements, and customer-imposed controls shape what you are allowed to build. You know how to satisfy an auditor without freezing the platform.\nGenuine AI fluency in how you work. You use agentic coding tools (Claude Code, Cursor, or equivalent) as a core part of your engineering practice, and you have automated real operational work with them. You have a considered view on where to trust an agent in production and where not to, and you can defend it.\nCI/CD across a mixed estate. Jenkins, CircleCI, and GitHub Actions all run here. You have owned pipelines in more than one of them and have an opinion about what belongs where.\nOpen-source observability you have operated, not just read. Prometheus, Grafana, and Loki as systems you have run, scaled, and tuned.\nProactive ownership. You find the problem before it is assigned to you, and work you pick up does not come back. On a team this size, nobody is tracking your queue for you.\n\nStrongly preferred - any of these moves you up the stack:\nTemporal.io in production: worker scaling, queue backpressure, and operating it as infrastructure rather than consuming it as a library.\nEvent-driven autoscaling with KEDA, and node lifecycle management with Karpenter, tuned against real cost and latency targets.\nSecret management at fleet scale: SOPS, KMS, key rotation, and hold-your-own-key models where the customer holds the key material.\nMulti-region production operations, including data residency and per-region compliance obligations.\nBuilding internal developer platforms or self-service tooling that measurably reduced how often engineers had to ask for help.\nMigrating source-control or CI/CD estates, or consolidating fragmented build tooling onto a single modern platform.\nKubernetes network and workload security in depth: CNI policy with Cilium or Calico, service mesh, and enforcing isolation between tenants at the network layer.\nStartup instincts plus enterprise discipline. You have worked somewhere small enough that you owned the whole problem, and somewhere serious enough that \"move fast\" had a blast radius.","description_format":"text","description_chars":6557,"description_truncated":false,"requirements":{"experience_years_min":6,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[{"name":"Israel","iso":"IL","kind":"country"}],"hiring_excludes":[],"relocation_offered":false,"industries":["Artificial Intelligence","Cybersecurity","Human Resources"],"lifecycle":[{"event":"open","at":"2026-10-14T05:31:11Z"}],"visa":[],"liveness":{"score":65,"band":"ok","label":"Likely open","p_open":1,"p_active":0.726,"p_room":0.9,"age_days":20,"expected_fill_days":31,"reasons":["conf:2","win:mid"],"computed_at":"2026-10-16T05:45:00Z"},"pay":null,"html_url":"https://alion.io/job/easysend-senior-devops-engineer","json_url":"https://alion.io/job/easysend-senior-devops-engineer.json","meta":{"generated_at":"2026-10-17T02:27:29Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"crawler_verified","counted_by":"address","units_charged":1,"used_today":3409,"day_limit":null,"remaining_today":null,"minute_limit":300,"resets_at":"2026-10-18T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.02,"usd":0.002,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":2788081},"rest":"https://alion.io/mcp/rest/get_company?id=2788081"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Feasysend-senior-devops-engineer"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"live","price":{"credits":1,"usd":0.1},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Feasysend-senior-devops-engineer"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.02,"usd":0.002},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Feasysend-senior-devops-engineer"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/easysend-senior-devops-engineer\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Feasysend-senior-devops-engineer"}]}