Software Engineer (Crop)

Palomar

16d•$60,000 - $100,000•Remote

About The Position

We are looking for a Software Engineer to take ownership of the systems that power our crop insurance claims platform. You'll design, develop, and maintain features used daily by claims adjusters, underwriters, and operations staff — translating complex insurance policies and regulatory requirements into reliable, well-tested code. What sets this role apart is its focus on MPCI and private product claims, which operate within a detailed and frequently updated regulatory environment. The ideal candidate brings real domain knowledge: how claims are processed end to end, the roles of PASS and NCIS, why data and calculation errors carry serious downstream consequences, and how to trace operational issues back to their root in policy, data, or logic. That expertise means you can work independently, move fast, and build precise solutions — without needing to ramp up on industry fundamentals.

Requirements

3+ years of professional software engineering experience in a production environment.
Proficient in Node.js and JavaScript/TypeScript for back-end development.
Proficient in Vue.js, HTML, and CSS for front-end development.
Experience designing and building RESTful APIs and working across the full stack.
Able to write unit and integration tests and participate meaningfully in code review.
Knowledge of common security vulnerabilities (OWASP Top 10) and how to mitigate them in application code.
Ability to work through large bodies of technical and regulatory documentation and translate them accurately into code.
3+ years in a claims, compliance, underwriting, or product/IT role at an Approved Insurance Provider (AIP), reinsurer, or RMA-adjacent organization.
Experience working directly with RMA or NCIS data submission systems.
Personally investigated and resolved PASS errors and NCIS discrepancies in a production environment; can walk through a specific example end-to-end (transaction → root cause → fix).
Solid understanding of the full crop insurance cycle — from policy application and issuance through loss reporting and claim settlement — across both MPCI and private products, including the regulatory differences between them.
Has worked claims through at least two full reinsurance years, including end-of-year processing (EOY) and the data submission cycle to RMA.
Ability to read and apply FCIC/RMA regulatory materials independently — Loss Adjustment Manual (LAM), Crop Insurance Handbook (CIH), Special Provisions of Insurance (SPOI), Coverage and Rates handbooks, applicable Crop Provisions, and FAD/PM bulletins — without requiring domain hand-holding.

Nice To Haves

Build strong relationships through transparency, trust, and respect for each other.
Work in an agile environment, with a resilient mindset to find creative solutions to challenges.
Collaborate and celebrate diverse perspectives, promoting inclusivity and equality.
Do the right thing with strong conviction and integrity.
Be bold and innovative to help make an impact.
Demonstrable track record of working autonomously and driving progress
Be intellectually curious, think creatively, and pragmatic

Responsibilities

Develop the claims platform. Build and maintain full-stack features for our claims processing platform using Node.js, TypeScript, Vue.js, HTML, and CSS — covering everything from back-end business logic and API design to the front-end interfaces that claims teams use day to day.
Translate regulatory requirements into code. Read and interpret government publications, FCIC/RMA handbooks, Loss Adjustment Manuals, and third-party procedural documentation. Translate that material into accurate technical requirements, data models, and application logic — and use it to validate or debug existing behavior.
Investigate and resolve PASS and NCIS errors. When PASS errors or NCIS discrepancies surface in production, investigate the transaction, identify the root cause — data, integration, logic, or a misapplied regulatory rule — and implement a tested fix. This is a support and engineering function performed alongside operations staff, not a claims adjustment function.
Collaborate with stakeholders. Work closely with claims adjusters, underwriters, and operations staff to understand their workflows, surface requirements, and ensure that what gets built solves the right problem.
Test, review, and secure. Write unit and integration tests for your own code, participate in code review, and maintain quality standards across the codebase. Apply security best practices — including mitigations for common vulnerabilities — throughout development.
Travel periodically. Travel periodically to field offices or industry events as needed to support operations teams or engage with stakeholders.