deet
Waymo has chosen to monitor travelers in a way that drivers of their own cars would not be monitored, while the government has chosen to ban privately owned vehicles from some spaces (like Market Street in San Francisco). This coerces individuals into sacrificing privacy and other rights.
Imagine if your phone company listened to all your calls and reported you to the police if it didn't like something you say.
And what happens when a private company like Waymo partners with a municipality to integrate into its transportation network? Is that now privately operated vehicle or part of a public space system like a sidewalk or the road itself?
Waymo is not like mass transit or even a taxi: only one group of passengers are in the vehicle at a time. Subway and bus rules don't cleanly apply. It's closer to a rental car that drives itself.
We as a society are turning to rely on or even require private companies for much of our essential infrastructure and interpersonal fabric: communications, payments (decline of cash) transportation, surveillance (Flock), places of congregation (virtual town squares), etc. Meanwhile because they are private they are not bound to privacy and other protections like the state itself.
We should rethink this direction.
Our experience might also not be typical because we have built infrastructure around making Devin and similar agents work better. And for the record no ties to Devin/Cognition. Just pay them too much as a customer.
It's coming from a different starting place than Claude Code or Codex are as individually controlled single-developer tools. Devin has been more persistent in pursuing the direction of something that operates more autonomously at the team level, as a peer. And while it might be slightly behind in raw harness ability (maybe?) it's probably ahead on the team-focus.
The key is consciously making that choice. What people don't want is to be forced into a way of living by others. People can accept what they have a hand in discovering and choosing.
Kinelo is building the "org structure" for humans+AI working together, shoulder-to-shoulder, as peers. We help coordinate tasks between each actor in a company, handoff context, and provide a voice and "seat at the table" to AI coworkers.
We're a small team, just hired our first GTM lead and a new product engineer. Getting ready to grow. We'd like to find another strong, experienced software engineer who can span everything from talking to customers to designing robust architectures to inventing new UX patterns.
Job description here: https://job-boards.greenhouse.io/kinelo/jobs/4205846009
We offer competitive salary and very meaningful (~first batch of hires) equity, with a founder previously exited to Apple and strong fundraising history (~$10m).
Please email us at [email protected] in addition to applying on Greenhouse. For the engineering role, tell us how you think the job of a software engineer is changing.
Opus 5 still uses "carry the argument", "worth stating plainly", ", and the trap", "The X matters more", the use of "move"
We need an "annoying English" benchmark.
- Fable 5 Max: https://gist.github.com/deet/3d97f854b48eac6658d642fa18bb24d...
- Opus 5 Max: https://gist.github.com/deet/1a43693a732dfccb4d0d914bfc42692...
Kinelo solves "context myopia": autonomous and semi-autonomous AI agents don't know what they don't know, so they can't search or find the background information required to accomplish tasks accurately and effectively. The result looks like slop but it's not due to model performance, more due to workflow integration. From there, we're rapidly moving into organizing humans together with autonomous "AI coworkers" into workflows that span both. Our goal is to change how organizations are run and structured.
We're hiring for two roles right now:
- Product Engineer / Senior Software Engineer (https://job-boards.greenhouse.io/kinelo/jobs/4205846009) -- do you have the software engineering wisdom not yet encoded in an LLM? and do you have product sense and the willingness and desire to think several steps ahead in the market?
- Founding GTM Lead (https://job-boards.greenhouse.io/kinelo/jobs/4215784009) -- there's no playbook for go-to-market in the category we're creating + the landscape is changing daily. Come architect a strategy and then move mountains to execute on it and help us grow insanely fast.
Competitive salary, meaningful (~first batch of hires) equity, founder previously exited to Apple, strong fundraising history (~$10m).
Please email us at [email protected].
If you want to stand out:
- For the product engineer role, tell us how you think the job of a software engineer is changing.
- For the GTM role, tell us about a time you got massive results with limited resources, all through your ingenuity, creativity, and hard work.
Or if you couldn't buy scissors (because they could cut brake lines).
Or if you couldn't buy a car (because it could be used to run someone over).
And if all of those checked with the government before functioning.
It's almost like maybe instead you should just ban the undesirable end action, enforce that law, and create societal conditions that don't nudge or force people into doing undesirable things.
Spaces that are less chaotic - coffee shops, gyms, even elevators - are places that people used to be able to strike up random short conversations with each other. Sometimes these would become longer. Sometimes they even turned into friendships.
It still happens of course, but I, like the author, am saddened that casual socialization seems to be on the decline.
I like to say Hi to people in elevators. Some reciprocate. Some find it awkward. But I don't even bother saying Hi to those wearing AirPods since that would be rude, interrupting them. Could an interaction have brightened our mutual days? Could we have become friends? Who knows, AirPods preempted it from the start.
We've had agents go as far as interactively testing how our product responds in video calls by launching our full stack in a set of docker containers (app, api, db, queues, etc.), all inside a larger sandbox, populating test data, connecting the mock system to a real video call solution like Google meet, and injecting audio and video to test the response. End-to-end, like a real user flow.
It's not perfect yet, but if you are a skeptic on the ability for AI agents to productively modify a complex product, I'd highly encourage you to play with a setup like this before ossifying your conclusions.
If AI is reducing the cost of using the long tail of small vulnerabilities or is making possible chaining them together into something more profound, then those small, less-concerning issues might requiring addressing in a way that was previously not required.
Kinelo solves "context myopia": autonomous and semi-autonomous AI agents don't know what they don't know, so they can't search or find the background information required to accomplish tasks accurately and effectively. The result looks like slop but it's not due to model performance, more due to workflow integration. From there, we're rapidly moving into organizing humans together with autonomous "AI coworkers" into workflows that span both. Our goal is to change how organizations are run and structured.
We're hiring for two roles right now:
- Product Engineer / Senior Software Engineer (https://job-boards.greenhouse.io/kinelo/jobs/4205846009) -- do you have the software engineering wisdom not yet encoded in an LLM? and do you have product sense and the willingness and desire to think several steps ahead in the market?
- Founding GTM Lead (https://job-boards.greenhouse.io/kinelo/jobs/4215784009) -- there's no playbook for go-to-market in the category we're creating + the landscape is changing daily. Come architect a strategy and then move mountains to execute on it and help us grow insanely fast.
Competitive salary, meaningful (~first batch of hires) equity, founder previously exited to Apple, strong fundraising history (~$10m).
Please email us at [email protected].
If you want to stand out: - For the product engineer role, tell us how you think the job of a software engineer is changing. - For the GTM role, tell us about a time you got massive results with limited resources, all through your ingenuity, creativity, and hard work.
They explore the root causes of historical accidents. Importantly, they do it from a broad perspective: not just the chemistry, but the human factors, the decision making, and the process failures that led to the accident and how to prevent such things in the future.
Kinelo solves "context myopia": autonomous and semi-autonomous AI agents don't know what they don't know, so they can't search or find the background information required to accomplish tasks accurately and effectively. The result looks like slop but it's not due to model performance, more due to workflow integration. From there, we're rapidly moving into organizing humans together with autonomous "AI coworkers" into workflows that span both. Our goal is to change how organizations are run and structured.
We're hiring for two roles right now:
- Product Engineer (https://job-boards.greenhouse.io/kinelo/jobs/4205846009) -- do you have the software engineering wisdom not yet encoded in an LLM? and do you have product sense and the willingness and desire to think several steps ahead in the market?
- Founding GTM Lead (https://job-boards.greenhouse.io/kinelo/jobs/4215784009) -- there's no playbook for go-to-market in the category we're creating + the landscape is changing daily. Come architect a strategy and then move mountains to execute on it and help us grow insanely fast.
Competitive salary, meaningful (~first batch of hires) equity, founder previously exited to Apple, strong fundraising history (~$10m).
Please email us at [email protected].
If you want to stand out:
- For the product engineer role, tell us how you think the job of a software engineer is changing.
- For the GTM role, tell us about a time you got massive results with limited resources, all through your ingenuity, creativity, and hard work.
We are hiring two Product Engineers to join us in our newly opened office in SF. We're small and early and you'll help shape team culture.
Kinelo solves "context myopia": autonomous and semi-autonomous AI agents don't know what they don't know, so they can't search or find the background information required to accomplish tasks accurately and effectively. The result looks like slop but it's not due to model performance, more due to workflow integration. From there, we're rapidly moving into organizing humans together with autonomous "AI coworkers" into workflows that span both. Our goal is to change how organizations are run and structured.
Our #1 hiring criteria for this position is immense software wisdom, the kind not yet encoded in the weights of an LLM. We are not looking for artisans to meticulously craft single lines of code. We're looking for software engineers excited to use the leverage that AI offers for code production to permit focus on higher order technical architecture, product requirements, and user needs.
We're looking for enough experience that indicates accumulated wisdom in shipping and maintaining reliable, scalable software, solid CS fundamentals, experience taking products from 0 to 1, and versatility.
Our current tech stack includes TypeScript, a managed container service, Postgres, and Redis. But we are adaptive and you should be too. We highly value software engineering and computer science fundamentals and experience with other languages like Go, C++, Python is valued.
Competitive salary, meaningful (~first batch of hires) equity, founder previously exited to Apple, strong fundraising history (~$10m).
Please email us at [email protected]. If you want to stand out, tell us how you think the job of a software engineer is changing. There's also a full JD here: https://job-boards.greenhouse.io/kinelo/jobs/4205846009
In my own team, I have seen ICs increasingly function like engineering managers, and even suffer some of the pitfalls of the role switch, as they change from reasoning about creating code to delegating to teams of software agents.
Increasingly, ICs are needing to understand the product roadmap more deeply, figure out how to spec a problem and constraints on a solution in the right way to get their subordinates to produce reasonable output, and be the communication bridge between other jobs functions and the entities actually producing the code.
I've also heard concerns of skill atrophy, as these team members spend less brain energy on language syntax, low level logic, etc, and more on interpreting abstract strategies to solving a problem and pattern matching those strategies against their software engineering wisdom.
If anything, ICs should consider that the skills that will make them successful managing agents might be the ones that have made first-level engineering managers successful: the ability to coordinate with other job functions, map implementation strategies to product and organization needs, and deliberately and carefully delegate and coordinate work of others writing the actual code.
Kinelo manages the new type of hybrid team that will emerge in the future: humans+AI working shoulder-to-“shoulder”.
Our first product helps human software engineering teams deliver more efficiently and more reliably by assisting in coordination and engineering management. But it’s built on a foundational layer that ingests data, knowledge, and process across communications and systems, exposing that to humans and AI alike.
Eventually, Kinelo will become a proper human+AI orchestration layer, managing entire companies, and our goal is to have Kinelo run Kinelo (we already dogfood it today).
We’re looking for high ownership individuals to join our small team and shape its direction. We also just opened a new SF office and new hires will have the ability to help shape company culture, engineering practices, architecture, and roadmap.
We’re well-funded (just raised another round), founded by a serial founder, anti-bureaucratic, and highly technical.
We’re looking for:
- Those who want to go 0 to 1 with high ownership: moving features and products from idea on a napkin, to prototype, to engineering UI, to shipped and polished product
- ~8 years professional experience, including the pre-LLM days with strong CS fundamentals
- A balance of wisdom from experience and optimism about the future
- Strong TypeScript and Postgres (or other RDBMS) experience at scale and with high reliability (SaaS apps, APIs, etc)
- Experience with a variety of technologies, including containerization, distributed systems, and at least one strongly typed programming language (Go, C++, Java, etc)
- Ideally experience with ML and AI systems (though expertise in ML, data science, etc is not needed for this role)
We can’t sponsor visas but relocation assistance to SF is possible.
Please apply here: https://job-boards.greenhouse.io/kinelo/jobs/4088659009 and also email [email protected], mentioning this post.
It's hard to predict how quickly it will be solved and by whom first, but this appears to be a software engineering problem solvable through effort and resources and time, not a fundamental physical law that must be circumvented like a physical sciences problem. Betting it won't be solved enough to have an impact on the work of today relatively quickly is betting against substantial resources and investment.
Kinelo manages the new type of hybrid team that will emerge in the future: humans+AI working shoulder-to-“shoulder”.
Our first product helps human software engineering teams deliver more efficiently and more reliably by assisting in coordination and engineering management. But it’s built on a foundational layer that ingests data, knowledge, and process across communications and systems, exposing that to humans and AI alike.
Eventually, Kinelo will become a proper human+AI orchestration layer, managing entire companies, and our goal is to have Kinelo run Kinelo (we already dogfood it today).
We’re looking for high ownership individuals to join our small team and shape its direction. We also just opened a new SF office and new hires will have the ability to help shape company culture, engineering practices, architecture, and roadmap.
We’re well-funded (just raised another round), founded by a serial founder, anti-bureaucratic, and highly technical.
We’re looking for:
- Those who want to go 0 to 1 with high ownership: moving features and products from idea on a napkin, to prototype, to engineering UI, to shipped and polished product
- ~8 years professional experience, including the pre-LLM days with strong CS fundamentals
- A balance of wisdom from experience and optimism about the future
- Strong TypeScript and Postgres (or other RDBMS) experience at scale and with high reliability (SaaS apps, APIs, etc)
- Experience with a variety of technologies, including containerization, distributed systems, and at least one strongly typed programming language (Go, C++, Java, etc)
- Ideally experience with ML and AI systems (though expertise in ML, data science, etc is not needed for this role)
We can’t sponsor visas but relocation assistance to SF is possible.
Please apply here: https://job-boards.greenhouse.io/kinelo/jobs/4088659009 and also email [email protected], mentioning this post.
Kinelo manages the new type of hybrid team that will emerge in the future: humans+AI working shoulder-to-“shoulder”.
Our first product helps human software engineering teams deliver more efficiently and more reliably by assisting in coordination and engineering management. But it’s built on a foundational layer that ingests data, knowledge, and process across communications and systems, exposing that to humans and AI alike.
Eventually, Kinelo will become a proper human+AI orchestration layer, managing entire companies, and our goal is to have Kinelo run Kinelo (we already dogfood it today).
We’re looking for high ownership individuals to join our small team and shape its direction. We also just opened a new SF office and new hires will have the ability to help shape company culture, engineering practices, architecture, and roadmap.
We’re well-funded (just raised another round), founded by a serial founder, anti-bureaucratic, and highly technical.
We’re looking for:
- Those who want to go 0 to 1 with high ownership: moving features and products from idea on a napkin, to prototype, to engineering UI, to shipped and polished product
- ~8 years professional experience, including the pre-LLM days with strong CS fundamentals
- A balance of wisdom from experience and optimism about the future
- Strong TypeScript and Postgres (or other RDBMS) experience at scale and with high reliability (SaaS apps, APIs, etc)
- Experience with a variety of technologies, including containerization, distributed systems, and at least one strongly typed programming language (Go, C++, Java, etc)
- Ideally experience with ML and AI systems (though expertise in ML, data science, etc is not needed for this role)
We can’t sponsor visas but relocation assistance to SF is possible.
Please apply here: https://job-boards.greenhouse.io/kinelo/jobs/4088659009 and also email [email protected], mentioning this post.
We are an early-stage, well-funded startup making humans and computers work together more efficiently. Experienced team from Apple AIML and other great companies.
We're looking for a polyglot "startup engineer" at the Staff+ level can help with the end-to-end implementation of new features and capabilities and who can move between different components, be creative, be flexible, take ownership, and get things done. We have a complex, challenging product, but one that's amazing to work on and that will soon change how people think about working with each other and with AI.
You'll enjoy this role if:
- You like going 0 to 1 with high ownership: moving features and products from idea on a napkin, to prototype, to engineering UI, to shipped and polished product
- You are innovative, get satisfaction out of learning new things, and thrive in an environment of uncertainty and opportunity
To succeed, you should:
- Have the wisdom to know when to take the fast route vs when to step back and clean up your mess
- Be capable and excel on your own, but be humble and communicate well with others as projects require more collaboration
- Be versed across many programming languages (e.g. from C++/Java/Swift to Go to JavaScript or Python)
- Have worked on many types of projects and software -- have you built servers, written games, shipped native apps, and vibe-coded (kidding) web apps? If so, you're a fit.
- Be versatile and work both high level and low level, on old tech and new. Have you both prompt-engineered an LLM AND tweaked the code that decodes tokens in your own local LLM runner? If so, you're a fit.
https://www.avy.app/careers.html?gh_jid=4007253009
Email us at [email protected]
We are an early-stage, well-funded startup making humans and computers work together more efficiently. Experienced team from Apple AIML and other great companies.
We will be opening several roles soon, but are previewing this one early: Staff Engineer / Startup Polyglot Engineer.
You'll enjoy this role if:
- You like going 0 to 1 with high ownership: moving features and products from idea on a napkin, to prototype, to engineering UI, to shipped and polished product
- You are innovative, get satisfaction out of learning new things, and thrive in an environment of uncertainty and opportunity
To succeed, you should:
- Have the wisdom to know when to take the fast route vs when to step back and clean up your mess
- Be capable and excel on your own, but be humble and communicate well with others as projects require more collaboration
- Be versed across many programming languages (e.g. from C++/Java/Swift to Go to JavaScript or Python)
- Have worked on many types of projects and software -- have you built servers, written games, shipped native apps, and vibe-coded (kidding) web apps? If so, you're a fit.
- Be versatile and work both high level and low level, on old tech and new. Have you both prompt-engineered an LLM AND tweaked the code that decodes tokens in your own local LLM runner? If so, you're a fit.
All said, we're looking for the stereotypical "startup engineer" who can move between different components, be creative, be flexible, take ownership, and get things done. We have a complex, challenging product, but one that's amazing to work on and that will soon change how people think about working with each other and with AI.
Email us at [email protected].
Two questions / thoughts:
1. I stumbled for a while looking for the license on your website before finding the Apache 2.0 mark on the Hugging Face model. That's big! Advertising that on your website and the Github repo would be nice. Though what's the business model?
2. Given the LLama 3 backbone, what's the lift to make this runnable in other languages and inference frameworks? (Specifically asking about MLX but Llama.cpp, Ollama, etc)
The bigger thing though was getting the models to have the appropriate levels of verbosity and detail in their ouput which fine tuning made more consistent.
If you have a Mac, you can also do pretty well training LORA adapters using something like Llama-Factory, and allowing it to run overnight. It's slower than an NVIDIA GPU but the increased effective memory size (if you say have 128GB) can allow you more flexibility.
At Avy.ai we're running small (2B-7B, quantized) vision models as part of a Mac desktop application for understanding what someone is working on in the moment, to offer them related information and actions.
We found that the raw results in understanding the images with a light LORA fine tune are not substantially different -- but the ease of getting a small model to follow instructions in outputting structured data in response to the image and at the level of verbosity and detail we need is greatly enhanced with fine tuning. Without fine tuning the models on the smaller end of that scale would be much more difficult to use, not reliably producing output that matched what the consuming application expects
But I left Apple where I was an engineering manager in the AIML group a few years ago to start a company that I think will significantly surpass Apple Intelligence for workplace use cases on the desktop soon.
Our strategy with AI models isn't that dissimilar (small, specialized local models, and opt-in remote models if needed), but we're targeting much higher value use cases where there's significant complexity that AI can help reduce, while Apple seems to be going for low-value low-reward things first. We're also trying to be much more proactive for the user, enabled by focusing on actual common business workflows rather than Apple's surface level product treatment in Apple Intelligence so far.
If you're so inclined, I've love to chat about what you're looking for ([email protected]), and you can hear about when we unstealth at https://www.avy.ai
What exactly would you like a third party system to do? Mac or iOS?