pBuild the platform a production runs on: generation, storage, permissions and the interface around them.
Small team, wide surface, work that ships the same week.
/ph3What you'd do /h3ulliShip features end to end — schema, server, interface — and own them afterwards.
/liliWork on the parts where correctness matters: permissions, credits, versioning, money.
/liliKeep frontier models useful inside a real workflow, which is a different problem from calling them.
/liliRead what breaks in production and fix the cause, not the symptom.
/li /ulh3Why it's hard /h3pThe surface is wide and the users are demanding: they look at frames all day, so a misaligned label reads as a broken tool.
And a bug in permissions or in credits is not a bug you get to fix quietly.




/ph3What it isn't /h3pNot a role with a narrow slice and a spec handed down.
Not a place where the interface is someone else's problem.
/ph3Who tends to fit /h3ulliYou have shipped something you were responsible for end to end, and maintained it afterwards.
/liliYou are strong in TypeScript and comfortable in Postgres — including the part where you have to reason about who can read a row.
/liliYou care how it looks and feels, and you would rather cut a feature than ship it half-finished.
/li /ul #J-*****-Ljbffr

📌 Developer (Milano)
🏢 Greatspir
📍 Milano