Software Engineer Backend

About the role

This role advances a secure identity platform that connects attributes and qualifications across industries. The engineer designs systems that keep member privacy and security central while enabling networked digital identity.

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

What you'll do

Platform boundaries expand through work on identity attributes and qualifications across multiple domains. Solutions scale on AWS cloud and integrate Java services with Kafka and Postgres.

Production reliability and member privacy guide architecture and implementation choices. Code moves through testing, documentation, and observability standards before deployment.

Requirements drive solutions as product, security, and operations teams collaborate to solve complex identity problems.

Requirements

Backend software development in Java totals a minimum of 3+ years of experience. Candidates work with cloud-based applications and are fluent in AWS, containerization technologies such as Docker and Kubernetes, and deployment tools like GitHub, Argo, and Jenkins.

Clear communication explains technical concepts to mixed audiences of technical and non-technical stakeholders. Mentoring less experienced team members reflects collaborative norms within the backend team.

Comfort with ambiguous requirements supports autonomous prioritization of what matters most for identity workflows. Curiosity about technology and commitment to constant learning sustain independent problem solving.

Practical notes

US employment eligibility is required, and roles may involve occasional travel within the country. The role is onsite at headquarters in New York City with access to senior leadership. 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

Backend engineering in identity and access relies on strict security and privacy practices. Cloud platforms and container orchestration streamline deployment of identity services. Observability and documentation help teams maintain reliable identity workflows. Cross-functional collaboration supports product outcomes across travel, stadium, and physical identity domains. Ongoing learning helps engineers adapt to evolving identity standards and technologies.

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.