Own complete changes
Take work from a clear problem through design decisions, implementation, tests, release evidence, monitoring and follow-up.
IDENT.INK
IDENT.INK
We are building one practical platform for identity, publishing, business, esports, creators and developers. We need engineers who can move between interface, API, data, security and production without losing sight of the person using the work.
Ident.ink connects public identity, websites, business and esports operations, media tools, hosting, bots, databases, communication and payments through one account. The surface is broad. The standard is not.
You will work in an existing production system where a clean customer outcome matters more than producing the largest diff. Some changes are visual, some are deeply operational, and many cross both.
Take work from a clear problem through design decisions, implementation, tests, release evidence, monitoring and follow-up.
Work comfortably in React and Next.js interfaces, Node.js services, API boundaries, relational data and real-time product behaviour.
Treat authentication, permissions, billing, private data, moderation and production access as engineering responsibilities, not somebody else’s review step.
Remove repeated failure modes, simplify architecture and leave useful documentation instead of adding another isolated workaround.
Explain assumptions, review diffs, reproduce errors, test failure paths and communicate clearly when confidence is incomplete.
Use scoped access, immutable releases, backups, health checks and rollback paths. Ownership continues after a feature becomes live.
Tools can assist investigation and implementation. The engineer remains accountable for understanding and reviewing the result.
Developers receive only founder-selected source areas. Environment files, credentials, databases, backups and runtime storage remain outside developer workspaces.
Developer submissions receive a long automated review. Clean evidence can publish automatically. Findings require correction or an explicit founder decision.
Raise security concerns, unclear requirements and bad news early. Hiding uncertainty is more damaging than asking a precise question.
The exact engagement may vary with experience, availability and business need. These stages explain the normal direction, not a promise of employment or a fixed contract type.
Send a concise note, links to work you can discuss, what you owned and the kind of problems you want to solve.
We discuss one real system or project in depth. Clear decisions and honest trade-offs matter more than rehearsed terminology.
When useful, we agree a small relevant exercise with explicit expectations. We do not ask candidates to build unpaid production features.
Role shape, availability, compensation, confidentiality, intellectual property and access are agreed before company systems are provided.
New engineers begin with selected source workspaces and reviewed releases. Access grows only when the work requires it.
We assess relevant work, judgement, communication and ability to perform the role. We do not require a particular degree or a perfectly conventional career history. Reasonable adjustments can be discussed through the application channel.