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...
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 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.
The charts are from appfigures.com. I'm not quite sure what they are using to generate them, but I'm sure the developer console in chrome will tell you ;-)
"It's a common misconception that Bitcoins gain their value from the cost of electricity required to generate them. Cost doesn't equal value – hiring 1,000 men to shovel a big hole in the ground may be costly, but not valuable. Also, even though scarcity is a critical requirement for a useful currency, it alone doesn't make anything valuable. For example, your fingerprints are scarce, but that doesn't mean they have any exchange value."
Have you ever seen the movie Middle Men? It's about some Internet entrepreneurs who setup a payment processor for porn sites. The transaction would show up as "24/7 billing" on your credit card statements. Definitely worth watching.
I use Sencha Touch on a daily basis, and have used it since version 1.0 (v2.0rc is now out). Clients love it because it comes close enough to native performance for data presentation apps. I also enjoy writing apps entirely in JS. I have also learned a lot about JS reviewing the source code.
The biggest downsides of Sencha Touch I see are:
1. Initial load. The framework is pretty large, even compressed, but CDN, gzip, and cache.manifest files help
2. Device support. Right now they they only support Android and iOS, but this fits the majority of my target.
3. Learning curve. Coming from a jQuery background it took awhile to understand their approach.
I love jQuery for desktop dev. When I tried a previous version of jQuery mobile the experience was not as good overall as Sencha Touch. Looking at the release notes for JQM 1.1, I will be giving it another try.
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