We have been using https://t.co/Zzxj2fS3Iw internally across 3 of my 8 companies (yeah ... i have a problem that needs an intervention) - and I can't work without Tasket, Studio and Friday anymore. There was life before neo and there is life after neo. Can't wait to get it out there in people's hands ... soon.
We don't do everything that other platforms do, but we do somethings that noone else does ... really well
We’re hiring someone who likes asking, “What would a user need to know here?”
At @neoworkos, that question takes you deep into the product.
We’re building an AI-native work platform where tasks, docs, spreadsheets, files, meetings and AI sessions come together in one workspace. There’s a lot to explain, and the product is moving fast.
You’ll work with Product and Engineering to understand what’s being built, spot what a user might miss, and turn it into documentation people can use.
This is a hands-on role with a lot of room to shape how documentation works at Neo, from what we publish to how it gets created, reviewed and maintained.
Apply → https://t.co/tJUBb2b94p
We're hiring a Creative Director to own Neo's visual identity and everything design puts into the market: brand, website, campaigns, product videos and motion, across Tasket, Friday, and Studio.
You'll design as much as you direct. You'll set the design language, build the team across brand, graphics, video and motion, and use AI tools at every step of how the work gets made.
We're looking for 8-12 years in design, with deep experience in brand or product marketing design for software companies, leading video and motion, and building design teams.
Apply: https://t.co/SgNAAWNAxT
Know someone who fits the bill? Tag them below.
We’re building Friday, Tasket and Studio as one AI-native suite at @neoworkos, the place where people and AI work together. And we’re looking for someone to help shape how we tell that story.
We’re hiring a Director, Content and Product Marketing to lead how Neo goes to market: the messaging across the suite, the segments and use cases we lead with, and the content that helps people understand and use the products.
Looking for someone with 10-14 years across product marketing and GTM, including experience leading marketing at a global B2B SaaS company with the US as a primary market.
Strong product instinct, comfort with technical products, and really good writing will matter a lot here.
Apply: https://t.co/KK9Q2Yutnm
When joining a fast-paced team, the challenging part is often figuring out why past decisions were made.. @KhumloB started capturing that context as she got it.
Meet Beulah Khumlo, product manager at @neoworkos.
To avoid relying purely on memory when priorities shift, she maintains what she thinks of as a “second brain”, an AI that captures the context and reasoning behind product decisions, so the “why” is easy to revisit as priorities shift. Things move fast here, and she wanted a way to keep the "why" behind a decision as accessible as the decision itself. She started building it the day she joined and hasn't stopped adding to it since.
At Neo, it shows up in the instrumentation framework she's currently building with the team for the entire platform tracking how users move through the product, where they drop off, and which edge cases the team might be missing without realizing it.
She joined Neo looking for more ownership over problems, not just solutions and that curiosity still shapes how she works today.
A little @neoworkos sighting in print :)
Bhavin Turakhia spoke to Entrepreneur Media @EntrepreneurAPJ about the experiences that have shaped how he builds companies; after more than three decades across Directi, Radix, Titan and Zeta, and now Neo.
The conversation gets into some of the less glamorous parts of building: staying close enough to customers to know what is actually working, being patient about product-market fit, learning which problems are worth sticking with, and eventually building a company that can operate without everything depending on the founder.
Turns out, getting to boring takes a lot of interesting work.
We're building a new way of working, and a core part of the job is communicating it clearly. You’ll define what Neo is, show how it is different from existing tools, and move people from hearing about it to using it daily.
We're hiring across Marketing:
- Director, Content and Product Marketing
- Senior Manager, Product Marketing
- Design Lead
- Product Marketing Associates
If you can get deep into the product, hold strong opinions on how we talk about it, and execute, we'd love to hear from you.
Apply: https://t.co/BcGsmGMf5u
Know someone who should see this? Tag them below.
We are building a work platform where AI is a first-class participant in the work, not a tab beside it. Product Marketing shapes how we explain it, launch it and grow it.
We're hiring Product Marketing Associates across launches, positioning, lifecycle, adoption and sales enablement.
Apply: https://t.co/oLpvvNV7Ez
AI-native teams take on more work because their AI works with more than just a prompt.
It has the task, the context around it, the way the team works, and the tools it needs to get things done. That changes what a team can take on.
At @neoworkos, we’re building this way ourselves: small teams, a lot of ownership, and AI involved in the work from the start.
And we’re looking for more people who want to figure out what working this way can unlock. If that sounds like you, we’d love to hear from you.
Check out open roles ↓
Most apps make you wait for the server before anything happens. Rajarshi's team builds apps that don't wait.
Meet Rajarshi Chakrabarti, Engineering Manager at @neoworkos, focused on client-side engineering.
"I'm not from a CS background. Core electronics, actually. My family still asks me why I ended up in software and I never had a clean answer. I just kept finding my way back to code."
He was one of Neo's first two engineers.
The architecture he walked into flips how most web apps work. Instead of the client asking the server for data and waiting, the browser keeps a working copy of the backend database, so the client already has the answer before it thinks to ask.
Rajarshi's team writes the specs and tech designs themselves, then hands that to AI to build. Development now takes up about 30% of the total effort.
Agents can write a lot of code. Someone still has to decide what it should ship.
At @neoworkos, that’s becoming a bigger part of the Principal Engineer’s job: architecture, evals, guardrails, production reliability, and defining what “correct” actually means.
We’re hiring a Principal Engineer I (Backend) to define how we verify, test and ship agent-written code.
You’ll work across complex backend systems and distributed infrastructure, while building the systems that let engineers run more work through coding agents without lowering the bar.
Apply: https://t.co/K4maWf6NZm
If you’re an engineer using agents every day: what’s slowing you down now?
Work waits on a handoff, an approval, a queue, a person who's on PTO. Between people, tools, and now agents, every gap is somewhere work goes to sit.
- A system of record tells you what happened.
- A system of execution makes it happen.
Different products, different foundations.
@neoworkos is the second one.
Your project tool has never finished a project.
Underneath, every app you use is a database. Capture, organize, display. Then it waits. The doing was always yours.
AI was the first real chance to change that. The industry's answer: a chat box in the corner.
Same database. Now with commentary.
We’re hiring an Accountant to join us in our Mumbai office.
You’ll work across books of accounts, MIS, GST and TDS filings, audits, banking, vendor payments and treasury reporting. This is a hands-on role for someone who likes being involved in the actual work, not just reviewing it.
We’re looking for someone with 3 years of relevant experience, strong Tally and Excel skills, and experience handling GST and TDS filings themselves.
If that sounds like you, or someone you know, we’d love to hear from you.
Apply: https://t.co/Vbr9MKOkri
A few months ago, Sanidhya expected his job to be writing backend code. Today, he’s owning systems used across @neoworkos and sitting in architecture discussions he didn’t expect to be part of.
Meet @sanidhyasmadhiy, a Senior Software Engineer at @neoworkos.
He started out wanting to become a doctor, but gradually found himself more drawn to maths and computers. His engineering career began as an intern at Zeta, where he dived into distributed systems, and scale.
At Neo, that scope has expanded quickly.
Sanidhya built the notification system that powers things daily digests across Neo. More recently, he’s been working on the layer that lets Friday connect to tools like GitHub, Confluence and Jira while handling permissions, actions and governance underneath.
He uses AI to write and review code, but his favourite use is testing: working through negative cases and edge cases that are easy to miss and tedious to cover manually.
That leaves more of his time for the questions he enjoys most: how the system should work, what technology to use and which trade-offs are worth making.
He came in to build backend systems. Now he’s helping decide what those systems should become.