HN user

ttezel

173 karma
Posts2
Comments7
View on HN

Canopy Connect | $160-205k | Full-time | Remote | US & Canada only | Product Engineer

Canopy Connect is single-click insurance data sharing (like "Plaid for insurance").

We serve over 3,500 companies (and growing rapidly!) including insurance agencies, lenders, insurtechs, fintechs, and insurance carriers to streamline acquiring verified insurance data from consumers and businesses.

We're hiring Product Engineers. We're a small, fully remote team based in the US and Canada. We present the best of both worlds - a nimble startup and small team (low strike price on equity and more ownership/impact), yet derisked because of our capital efficiency.

Apply here: https://www.usecanopy.com/company/careers

Canopy Connect | Product Engineer | Full-time | Remote | https://www.usecanopy.com/company/careers

Canopy Connect is single-click insurance data sharing (like "Plaid for insurance"). We serve large and small insurance agencies, lenders, insurtechs, fintechs, and insurance carriers to streamline acquiring verified insurance data from consumers and businesses.

We're hiring Product Engineers. We're a small, fully remote team based in the US and Canada. Apply here: https://boards.greenhouse.io/canopyconnect

Hi friends! At Canopy Connect, We're building single-click insurance data sharing - think "Plaid for insurance". Our infrastructure powers best-in-class insurance experiences. We're hiring Senior Full-Stack Engineers, a VP of Operations, Director of Marketing and Recruiter/People Operations. We're a small, fully remote team based in the US and Canada. Check out our open roles here: https://boards.greenhouse.io/canopyconnect

Yes my argument is simply that we publish API specs in a machine-readable format to avoid wasting time implementing clients repeatedly. WSDL and WADL had good intentions at heart, but XML is ugly. JSON is nice since it's human-readable and light. Why not publish JSON versions openly for REST APIs, reducing implementation cost for clients?