Are any good AI startups hiring engineers through X?
I’m a Staff Software Engineer with 8+ years building products, including AI and complex frontend systems.
Looking for engineering roles, agentic AI or founding teams.
Founders, I’m here. Let’s talk.
RT appreciated 🙏🏻
2/2 Key the cache by inputs that change the result, including tenant identity. Repeat A->B->A and check visible record IDs. Cache separation is not authorization; the server must still enforce access on every request.
1/2 Search cache fixture: tenant=A, query='invoice' returns A's records. Switch to B while that cache entry is fresh. If the key is only 'invoice', the UI can reuse A's data without a new request.
Skyflow: Senior Machine Learning Engineer. Remote India (ATS); 8+ years in ML, Python/Go + production pipelines. Checked 11 Oct: https://t.co/VB0Nx2yQUM follow for more software engineering jobs
Building an editor, creative tool, or complex workspace?
I built GoodAdsAI's core Figma-like canvas. I'm interested in engineering teams where frontend work is a systems problem.
Who should I meet?
For a landing-page test, state the job, show the proposed outcome, and clearly disclose availability before taking payment. Ask interested people how they solve it today. The useful evidence is the problem behind the email, not the waitlist total.
Joel Gascoigne wrote that Buffer started with a product landing page, followed by a not-ready-yet message at signup. The aim was conversations with people who understood the promise, rather than unexplained email interest. https://t.co/4DcfLTts8F
2/2 Calculate total from items during render: items.reduce((sum, item) => sum + item.price * item.quantity, 0). Check add, remove, and quantity edits. Memoize only if measurement shows that calculation is costly.
1/2 A cart stores items and total in separate React state, then updates total in an Effect. A render can show new items with the old total. Two values now need to stay synchronized.
2/2 Fixture: trial_days=14. Baseline: 'The trial is 14 days.' AI: 'Your trial ends tomorrow.' The first states policy; the second invents an account fact. Record both against the same rule. Tomorrow: keep an unseen exam.
Day 3/90: Applied AI. Our trial FAQ says 14 days. A lookup table can answer that without a model. Compare it with a single AI call on the same cases before adding retrieval or agents. Complexity needs a job the baseline cannot do.
An AI asks 'Confirm?' after saying 'update the customer'. Which customer, which fields, which old values? A confirmation button cannot replace a preview.
2/2 Track which draft revision was sent. On success, clear it only if the current revision still matches. Test failure->retry->success and edit-during-retry. An old success must not erase a newer message.
1/2 Form recovery fixture: name='Mira', message='Move the demo'. The API returns 503 before saving. After the error, both fields must still contain those exact values. A retry should not ask the user to type their work again.