Open roles
We do not have a public job listing open right now. The team is small, and we add people when the work and runway clearly support another hire - not to fill a spreadsheet of headcount. When a role is open, we will post the title, scope, and location or remote policy here. Check this page again or watch X, where we may announce new openings.
How we work
We are a remote-friendly product team. Most collaboration is written: issues, design notes, and review in GitHub. We bias toward async so people in different time zones are not stuck in standing meetings. We still protect focus time: shipping a reliable API and a clear UI matters more than looking busy in chat.
The stack is the one you would expect for this product: a Ruby backend, modern frontend, real databases, and a lot of care around what we send to model providers and how we bill customers. We expect engineers to be comfortable reading production logs and owning incidents for code they touch - not "throw it over the wall to ops."
What we value
Clarity over noise. We want teammates who can explain a tradeoff in a paragraph, not a slide deck. Honesty to users. The product is explicit about what AI can and cannot do. The same bar applies internally: we do not promise each other work we cannot deliver. Respect for code and data. Customer code and account data are not a training playground; security and privacy are not afterthoughts.
How to apply
If you might be a fit in the future, you can still reach out. Send a short note (no need for a cover letter in corporate format) to support@code-critic.com with the subject line prefilled as "Careers inquiry" or similar. Include what you have built, what you want to work on, and a link to your site, GitHub, or CV. We read messages when we are actively hiring; we may not reply to every general inquiry, but we keep a short list for the next opening.
Learn more
For the company story, mission, and how we talk about AI and limits, see About CodeCritic. For the product, start with How it works and the user guide.