Forward Deployed Software Engineer

Convr

Get hot jobs first on Telegram

New positions appear faster in our channel

Location: United States
Job Type: full-time
Work Format: 🌍 Remote
Salary: Not specified
Posted: November 1, 2026

Job Description

About Convr: Convr is an AI underwriting, data, and intelligent document automation workbench built for commercial P&C insurers. We help carriers, MGAs, and brokers accelerate premium growth, improve risk insights, and drive operational efficiency.

Founded in 2016, Convr transforms outdated, manual processes into structured, decision-ready workflows. Our modular platform manages underwriting from submission through quote with a purpose-built AI decisioning context engine – grounded in a commercial insurance ontology – ensuring complete data and smarter decisions, faster, while enabling a frictionless experience and superior performance.

As we scale, we’re building a team shaping the future of commercial underwriting. Join us in modernizing commercial insurance with modern AI.

Role Overview: We are looking for a Forward Deployed Software Engineer (FDSE) who thrives at the intersection of high-level architecture and deep-stack technical execution. This isn't a "one-off" integration role. You are a hybrid of a software engineer, product strategist, and technical consultant. You will embed with our most strategic customers to solve their most complex problems. However, your mission is dual-purpose: while you deliver immediate value to the customer, you are simultaneously acting as a product scout. You will identify patterns in customer needs and translate those into scalable, core features for our SaaS platform.

What You'll be Doing:

Lead the design and implementation of new features in our core SaaS product. You aren't just building for one user; you are building for the platform.
Work across the entire stack, from optimizing database queries and API endpoints to crafting intuitive UI/UX.
Architect production-ready integrations and workflows. You will lead technical workshops with stakeholders to define "future state" solutions.
Write high-quality, type-safe, and maintainable code in TypeScript, leveraging modern React and Next.js patterns for performance and scalability.
Prevent "bespoke bloat." Identify universal customer needs and collaborate with product and engineering teams to bake those into the core technical direction.
Contribute to CI/CD, testing, and performance monitoring to ensure the stability and reliability of your deployments.
Mentor teammates and establish engineering best practices to level up the entire team’s output.

Who You Are:

You think in terms of scalability. When you build a solution for one customer, you’re already thinking about how it could benefit the next ten.
You take 100% ownership of the success of your deployments. You don't wait for a ticket; you find the bottleneck and fix it.
You are as comfortable whiteboarding a system diagram for a CTO as you are submitting a pull request for a mission-critical API endpoint.

Experience Requirements:

7+ years of professional experience in full-stack or frontend development, specifically within SaaS products or startup environments.
Strong coder with shown proficiency in TypeScript/JavaScript, Python, Java, C++, or similar.
Hands-on experience with Next.js App Router (server components, layouts, streaming, caching).
Experience with tRPC or equivalent type-safe API frameworks.
Experience implementing complex, data-heavy views with Tailwind and component libraries (shadcn/ui, Mantine, etc.). Background in UI/UX design or working closely with designers is highly preferred.
Ability to design scalable systems and a solid understanding of frontend performance, state management, and accessibility.
Excellent communication skills and the ability to work autonomously, acting as a consultant/partner to our customers while remaining accountable for deliverables.
Familiarity with insurance and underwriting operations, gained through prior work in insurtech or with carriers, MGAs, or brokers
Ability and interest to travel up to 20% as needed to customer sites.

Why Join Convr?

Full Transparency. We believe in open communication with our team and customers.
We foster a work-life balance. We believe in flexibly because "life" happens!
Team mentality. We believe in "All Hands-on Deck"! Helping one another regardless of department.
Everyone knows your name. We are a high growth, dynamic, entrepreneurial company comprised of passionate team members committed to changing the commercial insurance industry. You will not be just a number!
We believe in challenging yourself to develop your career.
We are a team of experts who strive to be the best!

Benefits & Compensation

Remote work opportunities
Flexible Paid Time Off
Company Paid Holidays
Insurance Coverage (medical, dental, vision, short-term & long-term disability, life insurance, and accident coverage)
401K
Paid Parental Leave

🎯 Who is this job for?

This role is suitable for a Senior-level Forward Deployed Software Engineer with 7+ years of full-stack or frontend SaaS experience and strong TypeScript, React, Next.js, tRPC, UI performance, and system architecture skills.

The ideal candidate should be comfortable designing scalable integrations, building data-heavy interfaces, optimizing APIs and databases, and contributing to testing, CI/CD, monitoring, accessibility, and maintainable product code.

They should also be experienced in customer-facing technical consulting, stakeholder workshops, translating customer needs into reusable platform features, mentoring teammates, working autonomously, and preferably understanding commercial insurance or underwriting operations.

💬 Potential Interview Questions

How would you design a multi-tenant underwriting workflow that can support different carrier-specific rules without creating bespoke implementations?

I would separate the core workflow engine from configurable policies, schemas, and feature flags. Shared abstractions should handle common underwriting concepts, while tenant-specific behavior is represented through versioned configuration and extensible domain services.

How would you use the Next.js App Router to build a fast, data-heavy underwriting application?

I would use server components for data fetching and static rendering, client components only for interactive areas, and streaming with loading boundaries for large workflows. I would also apply appropriate caching and revalidation strategies while avoiding unnecessary client-side JavaScript.

What are the advantages of using tRPC or another type-safe API framework in this platform?

Type-safe APIs allow client and server contracts to be inferred from shared procedures, reducing runtime mismatches and duplicated types. I would still enforce authorization, input validation, and clear error handling at the procedure boundary.

How would you optimize a slow API endpoint that retrieves submission and policy data?

I would measure the endpoint first using tracing and database query analysis, then inspect indexes, joins, pagination, and over-fetching. Improvements could include query restructuring, batching, caching stable data, and returning only the fields required by the UI.

How would you design a complex underwriting UI using TypeScript, Tailwind, and a component library such as shadcn/ui?

I would establish reusable, accessible primitives and compose them into domain-specific components with strongly typed props. Complex views should support progressive disclosure, virtualization where needed, clear loading and error states, and consistent responsive behavior.

How would you manage server state and client state in a Next.js application?

Server state should remain close to the server and be fetched or mutated through typed APIs with deliberate caching and revalidation. Client state should be limited to transient UI concerns such as filters, dialogs, selections, and unsaved form input.

How would you make an integration with a carrier or broker production-ready?

I would define an explicit contract, validate and normalize external data, make operations idempotent, and implement retries with backoff for transient failures. The integration should also include authentication, audit logging, observability, dead-letter handling, and contract tests.

How would you prevent customer-specific requirements from causing bespoke product bloat?

I would identify the underlying reusable capability behind each request and compare it with patterns across customers. Customer-specific behavior should be implemented through stable extension points or configuration, while broadly useful capabilities should become versioned core product features.

What testing strategy would you use for an AI-assisted commercial underwriting workflow?

I would combine unit tests for domain logic, integration tests for APIs and persistence, contract tests for external systems, and end-to-end tests for critical underwriting journeys. AI outputs should also be evaluated with curated datasets, regression checks, confidence thresholds, and human-review fallbacks.

How would you ensure accessibility and performance in a data-heavy React application?

I would use semantic HTML, keyboard navigation, proper labels, focus management, sufficient contrast, and automated accessibility checks. For performance, I would minimize client bundles, virtualize large lists, memoize selectively, avoid unnecessary re-renders, and monitor Core Web Vitals in production.

📋 Job Summary

Convr is modernizing commercial P&C insurance with an AI-powered underwriting, data, and intelligent document automation platform. As a Forward Deployed Software Engineer, you’ll partner with strategic customers while building scalable SaaS features, production integrations, and data-rich workflows across the full stack. Work remotely from Chicago using TypeScript, React, Next.js App Router, tRPC, Tailwind, and modern component libraries, with up to 20% customer travel; salary is not disclosed in the posting. Apply to shape the future of insurtech, influence core product strategy, mentor teammates, and enjoy flexible PTO, comprehensive insurance, 401(k), paid parental leave, and a collaborative startup environment.