Forward Deployed Engineer

We need to output HTML fragment with sections: About the role (already present but we shouldn't repeat job title; we can include About the role heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We have content: About Kalepa (company description) - we can include as a section? Not listed but we can include as a paragraph maybe under About Kalepa? The instruction says we can include sections only when posting has real specific content. We have About Kalepa content, we could put that as a

maybe preceded by

About Kalepa

but not in list of allowed headings? The list includes About the role, Responsibilities, etc. It says e.g., not limited to? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings; we could also use other headings if needed? Probably stick to those. The About Kalepa could be placed under About the role? Actually About the role is separate. The posting includes "About Kalepa:" then "About the role:" then details. So we could have

About Kalepa

but not in the list; but maybe allowed as it's a section heading. The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests those are typical. Safer to include About Kalepa as a

without heading? But we need to preserve all substantive information. Could wrap in

About Kalepa

then paragraphs. We also have Salary range: $185k – $255k USD* - that's Pay info. So we need a Pay section with that info. Also benefits listed: Competitive salary, equity, benefits etc. So Benefits section. We have responsibilities: embed directly with customers, integrate software, ensure value, propose technical approach, build, adapt, etc. That's Responsibilities. Requirements: 4+ years software engineering experience, experience with external-facing APIs, ownership, communication, experimentation, fundamentals, Python, serverless, relational databases, PostgreSQL, etc. Also bonus: LLMs/generative AI, distributed systems. Qualifications maybe same as requirements; but we can combine. Skills: maybe list Python, serverless, PostgreSQL, etc. We need to avoid filler like "commensurate with experience". Not present. We must remove boilerplate: The note about salary range estimate etc is maybe minor metadata; we could fold into a short

or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. The salary range estimate note is minor metadata; we could include as a

under Pay section. We must not include application instructions, EEO, etc. Not present. We must output only HTML fragment. Let's craft:

About Kalepa

Insurance is a $7T global industry built on professional labor: underwriting, claims, pricing, operations, and distribution. Kalepa is building AI that can perform that work. We create professional-grade AI systems for insurers: software that can read, reason, decide, and act inside real workflows and operate over long-time horizons. Kalepa begins by augmenting professionals with the tools to succeed at their jobs. That earns us the right to learn from real decisions, capture decision traces, and automate what can be automated successfully over time. Our products are already in production with leading insurers, driving measurable outcomes and expanding across functions. The opportunity is far broader than any single workflow: to build the AI operating system for decision-making across insurance. For people who want to work on AI that matters, in a sector where correctness, trust, and real-world impact count, Kalepa is just getting started. Kalepa is backed by leading investors such as IA Ventures and Inspired Capital, and our team brings experience from Facebook, Palantir, Google, Amazon, McKinsey, Mastercard, and Uber. Our Values (This is important): Many organizations have a dusty list of corporate values that no one ever follows. Kalepa is not one of those companies. Our values are designed to unlock the potential of our employees. Success at Kalepa is bred from five core principles: Hustle and Determination - We hire people who take full ownership of their craft and relentlessly pursue excellence with speed and determination. We choose the hard problems and do not give up. This is the foundation of how we work and how we win.Deliver Customer Impact - We're obsessed with customer impact. Every feature, every line of code, every decision is measured against one question: does this help insurers make better decisions? If it doesn't drive speed, accuracy, or profitability for our customers, we don't build it.Meritocracy - We're building something exceptional, and that requires exceptional people and ideas. We have a high bar but we reward excellence with rapid growth. If you're the best at what you do, you'll thrive here.Transparency - We value honest, transparent communication over politics. We challenge ideas, not people. We say what needs to be said, even when it's hard. This is how we solve problems fast and find the truth.Experiment Relentlessly - Many of the problems we face have never been solved before. We tackle them by testing quickly, measuring rigorously, and iterating until we find the path forward. Speed of learning is our advantage. In addition to our NY office, we have remote employees speaking 10+ languages across the globe. But we invest in bringing our people together both for regional meetups and global offsites (2021 - Playa Del Carmen | 2022 - Rome | 2023 - Buenos Aires | 2024 - Lisbon | 2025 - Cartagena). Kalepa's culture isn't for everyone, and that's ok. But for the people who are a fit, they can't imagine working elsewhere.

About the role

Salary range: $185k – $255k USD*

We are seeking Forward Deployed Engineers who excel at solving hard, ambiguous problems, enjoy working directly with customers, and want to see the real-world impact of their code fast. As part of the engineering team, you'll embed directly with our customers to integrate Kalepa's software into their systems and ensure they're getting full value from the platform. This is a high-impact, customer-facing role that combines relationship building, hands-on software development, analytics, and strategy to drive key results for some of the largest insurers in the world. You'll have a global team of engineers, product managers, and customer success behind you, but you're the one accountable for turning each client's problem into a working solution: proposing the technical approach, building it, and adapting as their systems and data demand, with alignment from the broader team along the way. We're a small team where individual contributions have an outsized impact on both our technology and our business. You'll be right at home if you:

• Have 4+ years of software engineering experience, ideally with time spent working directly with customers.
• Experience building and using external-facing APIs or designing integrations with 3rd party systems.
• Take full ownership of your work and drive projects to completion with minimal oversight.
• Communicate proactively, surfacing blockers, asking the right questions, keeping stakeholders in the loop.
• Thrive on experimentation: you're comfortable testing ideas, measuring results, and iterating quickly on problems no one has solved before.
• Have strong fundamentals in system design, debugging, and problem-solving.
• Know Python (our main stack), though we're open to strong candidates from other OO backgrounds.
• Have experience with serverless technologies (Lambda, EC2), asynchronous workflows, and cloud environments.
• Have strong knowledge of relational databases and their performance tuning, ideally PostgreSQL.
• Are comfortable with relational databases, ideally PostgreSQL.
• Bonus: experience with LLMs/generative AI, distributed systems.

Responsibilities

• Embed directly with customers to integrate Kalepa's software into their systems.
• Ensure customers get full value from the platform.
• Propose technical approach, build solutions, and adapt as client systems and data evolve.
• Align with broader team on approach and progress.
• Combine relationship building, hands‑on software development, analytics, and strategy to drive key results for large insurers.

Requirements

• 4+ years of software engineering experience (customer‑facing preferred).
• Experience building/using external‑facing APIs or designing 3rd‑party integrations.
• Strong ownership mindset and ability to drive projects with minimal oversight.
• Proactive communication skills.
• Comfort with experimentation, rapid iteration, and measuring results.
• Solid fundamentals in system design, debugging, and problem‑solving.
• Proficiency in Python (main stack); openness to strong OO backgrounds.
• Experience with serverless technologies (Lambda, EC2), asynchronous workflows, cloud environments.
• Strong knowledge of relational databases and performance tuning, ideally PostgreSQL.

Skills

• Python
• Serverless (AWS Lambda, EC2)
• Asynchronous workflows
• Cloud environments
• Relational databases (PostgreSQL)
• API design / integration
• System design & debugging
• Experimentation & iteration
• LLMs/generative AI (bonus)
• Distributed systems (bonus)

Benefits

• Competitive salary (based on experience level)
• Significant equity options package
• Work with an ambitious, smart, global, and fun team to transform a $7T global industry
• Excellent benefits: 100% covered medical, 100% covered vision and dental, and others
• 20 days of PTO a year
• Global team offsites
• Healthy living/gym stipend
• Mobile phone bill stipend
• Continuing education credits
• 401(k) plan with employer contribution (regardless of employee contribution)

Pay

Salary range: $185k – $255k USD* (final compensation determined during offer stage based on experience, interview performance, and geographic location).

We have duplicated salary info; we could keep only Pay section. But About the role also had salary range line; we could keep that as a short paragraph. However we must avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the salary range mention somewhere. It's okay to have it in both About the role and Pay sections, but that duplicates. Might be okay but could be considered redundant. Better to keep it only in Pay section and remove from About the role. But About the role originally had "Salary range: $185k – $255k USD*". If we remove it, we lose that detail