hatchet retweeted
biased but our @hatchet_dev engineering team is the strongest team of engineers I've worked with and we still do coding interviews. the difference is that we do them live and pair-program on a feature together. use claude code, cursor, etc - we don't care. we just want to see how you build and ship code.
the things we’re looking for in particular are:
- competency with tooling: how are you using/prompting your coding agent? Do you have an opinionated and productive setup?
- coding fundamentals: can’t really test this with coding output anymore, but asking people to explain or walk through their code has been a good signal.
- approach: get something working without sweating too many details right away (build first, then optimize)
I've been particularly surprised by engineers who are completely reliant on Claude Code and Cursor but absolutely horrible at using them. great engineers really care about their tools; there’s an element of specificity and clear thinking which translates directly to their use of coding agents.
for startups, the best signal by far is a paid trial period, but this likely excludes the most talented candidates who are already working impressive jobs.
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
wingdings translation 👇
♒︎♋︎⧫︎♍︎♒︎♏︎⧫︎ ♓︎⬧︎ ●︎□︎⬥︎🙵♏︎⍓︎ ♌︎♋︎⬧︎♏︎♎︎ ♋︎⬧︎ ♒︎♏︎●︎●︎
♑︎●︎♋︎♎︎ ⬥︎♏︎ ♑︎□︎⧫︎ □︎♐︎♐︎ □︎♐︎ ♍︎●︎□︎◆︎♎︎ ⧫︎♋︎⬧︎🙵⬧︎
it's been a week. to end it on a high note, we're releasing FIPS-compliant images for everyone (not gated behind some enterprise sales maze).
you're either in one of two camps: you've never heard of FIPS, or you deal with it every day. this is for the second camp.
docs: docs.hatchet.run/self-hostin…
hatchet retweeted
C++ was the first language I learnt and abstractions were quite important from day one. The way objects can mutate their way to various identities and the compiler makes it all work is one of the beautiful ways of reasoning about writing useful code, something that OOP languages brought with them.
If you're building a startup today, one of the core strategies to become a winner in your space is to build a platform with abstractions and primitives that scale across various use-cases. I tend to always think on these lines given my early intro to programming with languages like C++ and Java.
So naturally, I love working at @hatchet_dev where we are building the orchestration engine to power every workload out there. The primitives we have built over the time have been extremely powerful to provide our users with an abstraction layer over all of their running workflows and jobs, ranging from AI agents to data pipelines and even notification systems.
hatchet retweeted
Our European takeover continues. We're so excited to have JB on the @hatchet_dev team!
please join us in welcoming jean-baptiste souvestre to the team! based in paris (ooh-lala), JB joins our growing engineering squad in europe. 🥖🇪🇺🍷
we asked him some questions to get to know him better, here's what he said:
➡️ light mode or dark mode?
🎤 what is a light mode?
➡️ we're told you're a cat man. tell us about your cats.
🎤 so i have 3 cats, kiki, chablis, and croche-pattes, all of whom are scoundrels in one way or the other. they love wet food, waking up at 4pm, and going to bed at 5.
➡️ how did you first come across hatchet?
🎤 i wanted to introduce hatchet to my last company because i liked the tech that much, but i figured it might just be more fun to work on it directly.
➡️ if i were in paris for one (1) day and wanted to get the best croissant, where would you suggest i go?
🎤 that's mamiche, in the 10th arrondissement, for sure.
➡️ what's something that surprised you in your first week here?
🎤 honestly can't decide between the tech maturity at such a young startup and the amount of custom frog emojis one can add to slack.
➡️ last, but not least: claude code or codex?
🎤 claude, but just because it was a french first name.
bienvenue à bord, JB! 🚀
please join us in welcoming jean-baptiste souvestre to the team! based in paris (ooh-lala), JB joins our growing engineering squad in europe. 🥖🇪🇺🍷
we asked him some questions to get to know him better, here's what he said:
➡️ light mode or dark mode?
🎤 what is a light mode?
➡️ we're told you're a cat man. tell us about your cats.
🎤 so i have 3 cats, kiki, chablis, and croche-pattes, all of whom are scoundrels in one way or the other. they love wet food, waking up at 4pm, and going to bed at 5.
➡️ how did you first come across hatchet?
🎤 i wanted to introduce hatchet to my last company because i liked the tech that much, but i figured it might just be more fun to work on it directly.
➡️ if i were in paris for one (1) day and wanted to get the best croissant, where would you suggest i go?
🎤 that's mamiche, in the 10th arrondissement, for sure.
➡️ what's something that surprised you in your first week here?
🎤 honestly can't decide between the tech maturity at such a young startup and the amount of custom frog emojis one can add to slack.
➡️ last, but not least: claude code or codex?
🎤 claude, but just because it was a french first name.
bienvenue à bord, JB! 🚀
hatchet retweeted
back in february, when we first released the @hatchet_dev CLI, we were pretty adamant that it was the CLI, and not an MCP, that would be the primary entrypoint for agents using Hatchet. and this has definitely been the case! but the rise of coding agents and the latest MCP spec are making MCPs much more usable across a wider range of services by supporting serverless request/response. and, frankly, we've been using MCP servers much more -- shoutout to @Posthog and @Figma.
so we're releasing a new and updated MCP which does everything you'd expect -- debugging runs, triggering workflows and runs, and inspecting configuration of workflows and tasks -- so you can use either the CLI or the MCP (or the regular SDKs) to accomplish what you need.
new: hatchet mcp
trigger, inspect, and replay runs from your coding agent
docs: docs.hatchet.run/reference/c…
hatchet retweeted
our new overview page 1) is great for observability over your workflow orchestration; and also 2) offers relief from the sisyphean burden of shame and guilt over limited metric visibility that we all must carry as we roam this mortal coil. it's great
Replying to @hatchet_dev
wracked with #GUILT because you don't have visibility into key metrics? CLEANSE YOUR CONSCIENCE!! 🌈
hatchet retweeted
We've gotten some great feedback already on our new overview page, excited to share it with everyone!
WE have a NEW overview page 🧨 🧨 🧨
that's right, you read that correctly, hatchet now has a fancy, brand-spankin'-NEW (!!!!) ~ overview page ~ that shows you ALL the stats you might need to know
a key executive #stakeholder flagellating you because the 10 thousand worker pods you provisioned them are sitting idle? point them at the overview page (100% utilization, now that's what i call efficiency!!) and tend to your wounds 📈
#synergy
only the essentials. I'm all about the core primitives
me, just now: hmm i wonder what accounts the @hatchet_dev account follows
the @hatchet_dev account:















