​
🔁 Process & Ownership

We work async, fast, and ticket-first. The goal is for developers to be able to operate independently with as little overhead as possible. This only works when expectations are clear and consistent — which is exactly what this page exists to provide.

​
🧾 Ticket Flow

All work comes through Linear tickets. These are fully specced and mapped to Figma. You are expected to: Read the ticket fully. If something’s missing, ask. If something no longer makes sense because of other work, use your experience to resolve it, or flag it if it has larger ramifications. Complete assigned tickets first. If you are awaiting a review, you can pick up another ticket, but don’t leave work hanging. Push to a named branch. Use the ticket ID and a short slug. Open a PR. Connect it to the ticket and assign a reviewer. Mark the ticket done only after review is complete and merged.

​
🔍 Ticket Quality

In alignment with the Nomey ethos, all tickets were co-created with AI. There may be some rough edges, but the goal is to get you started quickly.
  • Example; the ticket may say “create endpoint” when it means “create a tRPC procedure”.
You are not expected to design, only to execute and suggest. If something is unclear, comment directly on the ticket.

​
🧠 Expectations

We are hiring engineers. Not vibe-coders. Not AI operators. That means: You can make decisions based on the ticket, designs, and context. You can read and understand the codebase without needing constant guidance. You escalate problems quickly, not after a day of spinning. You leave things better than you found them. You take ownership of quality — don’t ship sloppy work to move fast. You document anything someone else needs to know after you.

​
🚥 PR & Review

Keep PRs small and scoped. PRs must be linked to Linear. Tag a reviewer — no silent PRs. Fix or respond to all comments. If you’re blocked or unsure, push the WIP and communicate. A ticket is only considered done once the PR is reviewed and merged. Until then, it’s still active. This also means: Code in review counts toward your workload No zombie PRs

​
⚙️ Final Notes

We optimize for autonomy, not process. Ticketing is strict to reduce meetings, not to add bureaucracy. If you have a better way to do something, suggest it. Ownership mindset is non-negotiable. If something’s wrong in the ticket, the process, or the repo — flag it. Improving the system is part of the job.