General Opening - Create Your Own Role!

About the role

Candidates explore how they can contribute to Injective across product, engineering, and operations without a predefined opening. The role targets people who align with the company mission and are comfortable in technical, evolving settings.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

Location: USA

Engagement: Full-time.

Equal opportunity employer adheres to non-discrimination and anti-harassment protections.

Contact uses only Injective.foundation email addresses.

What you'll do

Operating within highly technical teams, you adapt quickly as priorities evolve and manage shifting demands. Clear communication and cross-functional collaboration advance shared objectives across product, engineering, and operations. Proactively identifying problems, you drive solutions forward from discovery through completion. Using genuine passion for crypto, DeFi, and emerging technologies, you define the impact of your work on users and partners. The team shapes the role responsibilities and defines where contribution is greatest based on how you think you could contribute.

Requirements

You demonstrate comfort with fast-paced, dynamic work conditions and sustained focus amid change. High ownership and autonomy guide your decision making and execution without constant direction. Functioning effectively within highly technical team environments, you collaborate closely with engineers and product colleagues. Problems are identified and solutions are driven to completion without lingering. Clear communication supports cross-functional collaboration across product, engineering, and operations. Authentic passion for crypto, DeFi, and related emerging technologies informs your priorities and choices.

Practical notes

The position is full time and open to locations in New York or Remote within the United States. Injective operates as an equal opportunity employer with stated non-discrimination and anti-harassment policies. Report and avoid any unsolicited contact from non-Injective-foundation accounts, and stay cautious with unexpected messages.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

People in this type of role often build products, define processes, and coordinate cross-functional initiatives. Technical teams in crypto commonly use protocols, smart contract tools, and collaborative development workflows. Fast-moving environments require clear communication, quick adaptation, and proactive problem solving.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.