GloveBox | Product System Engineering | Denver CO | Fully remote (US only) | $150k + benefits.
GloveBox is an InsurTech with an innovative platform that’s changing how insurance works for everyone involved. We believe the industry has long needed a transformation, and we're here to build it—bridging the gaps between policyholders, agents, and carriers through seamless, powerful connections. Backed by industry-leading InsurTech VCs, influential agencies, and top insurance experts, GloveBox is breaking down outdated barriers with a clear mission: to make insurance transparent, empowering, and accessible for millions.
As a Product System Engineer at GloveBox, you’ll be instrumental in developing core web services and APIs. You will be heavily involved with the design and implementation of system level enhancements, from the database all the way through public facing APIs. This role will have an emphasis on building out CRM and user notification / communication capabilities.
GloveBox is primarily developed using open source software. We also believe in giving back to the community, and support contributing back to projects that we use. Our back end system tech stack includes the following: Go, Postgres, Clickhouse, Docker, Git, Linux (Ubuntu), AWS (ECS, Lambda, SQS, API Gateway, S3, Cloudfront, etc.)
I just wrapped up a Go based SAML integration and I was initially using your package. I encounter a bunch of issues with namespaces, and eventually ended up using xmlsec1 directly against a formed up XML template. I agree with you, SAML should go away. This was my first experience with it, and the nuanced complexities were so exhausting. I’m glad the integration is done...
You only need the PAN to charge the card, and many banks will gladly accept charges on expired cards even if provided with an expiration date in the past.
I'm sure there's money in recycling/reusing the rare and expensive metals and components of now-defunct satellites, but I think it would probably encounter a) resistance from the owners of those satellites if it's not just an altruistic cleanup job sanctioned by governments, and b) related to what you say, the cost of actually performing the task would undoubtedly outweigh any money recouped.
Killer work Alex! It's crazy you just rolled this out. We have been in development on something very similar but have yet to make a public push on the product. The main difference is we host the vector source file and build rasters from it. This helps maintain top quality at any size, and allows us to output to additional formats (i.e. PDF).
The product is still in alpha, but it's amazing how many similarities we came to with the URL scheme design. For example, image embedding:
Our approach requires companies to confirm their domains and associate a vector logo with the domain. Your strategy obviously provides a lot of logos right out of the gates. Logos are such a pain to deal with, it's great to see the problem being attacked from a few different angles.
I'm curious about the claim "pixel perfect every time" seen on your home page. Do you employ some special algorithm to scale images, or do you just use the standard tools? As far as I know, scaling vector graphics isn't enough to guarantee pixel perfection (especially not at low resolutions), and low-res logos are usually hand-crafted by designers. Maybe you should also allow companies to upload raster logos?
I spend about 30% of my time system side in Go, and the rest in Node.js. I'm working to migrate almost all of my time to Go. The language is fun to work in and, personally, the overall experience is much improved over Node.js. It's exciting to see the momentum behind the language and the great people who are attracted to it.
At a startup I worked for we used node.js prototype/sometimes v1.0 and Go for everything after. We shifted to writing everything in Go as we reach a point were we were more efficient from an effort standpoint in Go.
GloveBox is an InsurTech with an innovative platform that’s changing how insurance works for everyone involved. We believe the industry has long needed a transformation, and we're here to build it—bridging the gaps between policyholders, agents, and carriers through seamless, powerful connections. Backed by industry-leading InsurTech VCs, influential agencies, and top insurance experts, GloveBox is breaking down outdated barriers with a clear mission: to make insurance transparent, empowering, and accessible for millions.
As a Product System Engineer at GloveBox, you’ll be instrumental in developing core web services and APIs. You will be heavily involved with the design and implementation of system level enhancements, from the database all the way through public facing APIs. This role will have an emphasis on building out CRM and user notification / communication capabilities.
GloveBox is primarily developed using open source software. We also believe in giving back to the community, and support contributing back to projects that we use. Our back end system tech stack includes the following: Go, Postgres, Clickhouse, Docker, Git, Linux (Ubuntu), AWS (ECS, Lambda, SQS, API Gateway, S3, Cloudfront, etc.)
If you're interested in this position, you may apply here: https://wellfound.com/l/2AKRks