srikanthkasa

Building the initial version of app is not the tough part anymore, Completeness is another aspect and most of these are internal tools which can be iterated to fit team requirements

Supero | Cloud / Platform Engineer | REMOTE (SF Bay Area, CA, US · Bengaluru, KA, India) | Full-time | https://www.supero.dev/careers/cloud-platform-engineer/

We generate full-stack apps and deploy them — a generated app becomes a live URL, on our infrastructure or in the customer's own AWS or GCP account. It's in production and it has more shell script in it than it should. You'd own it, and the mandate is to make it boring. Kubernetes, GCP and AWS deploy paths, CI/CD, observability, cost, tenant boundary.

No on-call rotation today — it's the founders and whoever last touched it. Building a real one is part of the job, not something you inherit alone.

4+ years production infra, Kubernetes past the tutorial, AWS and/or GCP at depth. The rest is on the page, including the open problems that don't flatter us. I'm a co-founder — ask me anything here.

You can apply at: https://www.supero.dev/careers/cloud-platform-engineer/ Intern Position: https://www.supero.dev/careers/software-engineer-intern/

the problem usually isn’t missing facts. it’s that null means different things in different counties — no flood map vs no flood risk, wrong parcel, owner fields that don’t map cleanly.

if the API returns absent/failed instead of making the model guess, that’s actually a really good design choice.

curious how often those cases show up on normal residential parcels vs the messier commercial/infill sites.