Software Engineer - Infrastructure & DevOps

About the role

Infrastructure ownership secures reliability, security, and compliance so the platform scales with confidence. Security and observability enable SOC 2 readiness and support regulated growth. The position operates in-office in New York and safeguards cloud infrastructure while balancing performance, cost, and compliance.

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

Reliability, security, and compliance are strengthened through SOC 2 Type II implementation, security controls, and auditor collaboration.

System performance, latency, and cost efficiency are optimized to meet rising customer demand and transaction volume.

AWS networking, security groups, IAM policies, and compliance configurations are managed to support cloud operations.

Requirements

The posting states a bachelor's degree requirement. Hands-on experience with AWS services including EC2, RDS, Lambda, CloudWatch, and IAM is required.

Implementing security best practices and compliance frameworks such as SOC 2, ISO 27001, or similar is required.

Infrastructure-as-code tools such as Terraform or CloudFormation are used to define and manage environments.

Containerization and orchestration via Docker, Kubernetes, and ECS are used to deploy and run services.

Networking and security principles, including encryption, guide architecture and configuration decisions.

Observability platforms such as Datadog, Grafana, Prometheus, or CloudWatch are used to build monitoring and alerting systems.

Scripting languages such as Python, Bash, or Go automate tasks and workflows.

Practical notes

The role is based in an in-office team located in New York.

Technical collaboration spans infrastructure, security, and compliance across cross-functional teams.

Continuous learning supports adapting to evolving technologies in a fast-paced environment.

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

Platform reliability engineering emphasizes automation, observability, and resilient infrastructure.

Cloud providers such as AWS deliver compute, storage, and networking foundations for modern systems.

Security and compliance programs require controls documentation, audit interaction, and certification maintenance.

Infrastructure-as-code enables versioned, repeatable environment provisioning and change management.

Observability data drives insight into system behavior, performance bottlenecks, and incident response.

Container orchestration schedules workloads, manages service discovery, and handles scaling in production.

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.

About the company

Join us on a mission to increase the rate at which Americans save for retirement.