engineer

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-08-06

Final complete day: 2026-08-06. Attention was 0.8% — this entity appeared in 14 of 1,744 analyzed posts/comments in the seven days ending that day (15 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-08-06 20:04 UTCComment

   Every engineer joining a startup needs education in equity. It’s surprising how many founding engineers don’t understand the basics. I had to educate my team

2. 2026-08-06 17:39 UTCComment

   It's not ego at all. It's that I don't want a venture scale startup. I want a small business that pays me my current full time engineer rate but lets me work my desired hours. The second I take an investment, that doesn't work anymore. Plus, I have enough assets personally to put into this project (as I've already been doing) so I'd have to get an offer that is more than I'd be willing to personally invest first. I'm not sad about access to the money, I was sad about losing access to no-strings-attached money

3. 2026-08-06 14:59 UTCPost

   How did you find your first design partners / pilots ? i will not promote - I'm validating a problem around support engineers at mid-size companies (30-100 people) and trying to figure out how to actually get my first design partners lined up, people I can work closely with while building this out. Quick context on the problem: support engineers spend a ton of time turning half-finished tickets into technical cases that engineers can actually dig into. On complex Tier 2 stuff the info you need is scattered everywhere, ticketing system, logs, monitoring tools, docs, past incidents. So they end up manually hunting all of it down before they can even escalate, which can eat 30-45 min per case. If you've gotten early design partners before, curious how you did it. where did you actually find people willing to talk to you? Right now my playbook is just manually outreaching my persona on LinkedIn, managing to get them on a call, and if there's a fit, I come back to them a week later to ask if having the company as a design partner is possible, routing me to the decision maker to see if something can be done I don't know if this is the right way to do it or if there's a better approach out there. Would appreciate any playbooks or communities that worked for you.

4. 2026-08-06 11:09 UTCComment

   What you say sounds pretty normal. I just wonder if the definition of "founding engineer" is broadening so now people who join even past series A might describe themselves as a founding engineer for CV reasons - I can't explain the value of these options otherwise. In my company pretty much anyone who looks at code wants to call themselves an engineer.

5. 2026-08-05 20:01 UTCComment

   It's normal. It just means they want more money to grow the business (e.g. hire more engineers). The only cause for concern would be if they are unable to find funding with ~6 months (no one is interested) or if they have a reverse round where their valuation goes down (they are desperate and running out of money).