Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Stealth | San Francisco, CA (hybrid: M-W-F ONSITE) | Full-time | Fullstack Engineer

We're looking for a backend-leaning fullstack dev. Highlights:

- We're a 5-person startup in San Francisco (hybrid: 3 days/week in office)

- We're working on a b2b SaaS for managing/analyzing cloud costs for really large companies.

- The domain isn't cool, but the complexity is fractal and the need is huge.

- Typescript/Python/Clickhouse currently

- Our founders are also the founders of the Duckbill Group, an AWS cost consultancy. As a result, we've got a great, built-in sales pipeline.

- As a result of that, we're bottlenecked on our ability to just build the features our users clearly want.

- So we're hiring a 4th engineer: a backend-leaning full stack dev to build and own large swaths of this thing we're creating!

- We're looking for someone with 5+ years of experience, though probably closer to 8-10, depending on the person and the experience.

- Comp is 175k-200k base, 0.5-0.75% equity.

If you're interested, apply here: https://careers.duckbillgroup.com/apply/CBxnybZYqm/Full-Stac...

I promise I'm personally reading everything that comes in through that link.



Does fractal here imply complex or simple? (they're visually complex but mathematically simple)


Not the person you're replying to, but I often use "fractal complexity" to describe problems with a certain character, and I (and I assume this poster as well) mean it in the more precise sense: as Wikipedia puts it, fractals have "detailed structure at arbitrarily small scales". Fractal problems have complexity at every level of resolution; they're tricky in broad strokes, and if you zoom into one area it's internally complex, and if you zoom into any sub-area it's internally complex, and so on, forever.

Most of computing is this way if we're honest about it; the space of possible sub-disciplines of software engineering is nearly infinite, as is every possible subfield thereof, or sub-sub-field, or...


GeneralMayhem captured it pretty well, but yeah: it's complex at every scale. You see some complexity, you zoom in, and you find that the bit you zoomed in on is just as complex!

Our founders are pretty deep domain experts on aws cost management. At this point one of them has pretty much a catch phrase: whenever I say how I think some little aspect of aws billing works, he'll reply with "Let me complicate that for you" and describe 2-3 edge cases where what I thought I knew doesn't quite apply. :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: