ARolek
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
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:
https://img.ogol.io/<domain.com> example: https://img.ogol.io/ogol.io
we also support downloading
https://dl.ogol.io/<domain.com> example: https://dl.ogol.io/ogol.io
Each logo also has it's own page to make working with the asset outside of an API easy.
https://ogol.io/ogol.io/nn0ymd
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.
Ask HN: Errors and Omissions Insurance for SaaS startup
I have been digging into the world of E&O insurance, and all the policies I'm looking at are over engineered labyrinths. Additionally, most of the carriers I have talked with have little understanding of technology companies.I'm looking for some advice on what a SaaS startup should be looking for in E&O insurance and suggestions for providers that understand tech startups.
Why your brand needs a Vector logo
Ask HN: What DNS provider do you use?
I have been using moniker.com to register my domains for years. They have always been solid, but their name servers are failing today and they have no indication of when they will be fixed. I use AWS, so I'm looking into Route 53. There are numerous DNS providers so I want to see what the HN community suggests.
Your brand name needs more than usability
Ask HN: What's your experience with white labeled products and service?
I'm trying to understand the value of white labeling from both the customer and business sides.On the customer side, what was the advantage for using a white labeled solution? Which ones have you used?On the business side, what did you notice about offering a white labeled solution? (Conversion, pricing, offering type, stickiness)
How we tripled our revenue by adding one button
"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."
22 year old Magnus Carlsen now highest rated chess player of all time
The state of digital education
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.
Overall I love this idea and wish you great success! Keep it up.