Basic Capital
Software Engineer - Infrastructure & DevOps
About this role
Join Basic Capital's founding Infrastructure & Security team to build and maintain the cloud platform powering a fintech retirement solution. You'll drive platform reliability, security compliance (SOC 2), and operational excellence across AWS infrastructure while enabling the company to scale securely.
What you'll do
- Establish and maintain SOC 2 Type II compliance, implementing security controls and documentation
- Design observability systems including logging, monitoring, alerting, and distributed tracing
- Build CI/CD pipelines and infrastructure-as-code for automated, safe deployments
- Manage AWS infrastructure including networking, security, IAM, and compliance configurations
- Optimize system performance, latency, and cost efficiency at scale
- Serve as founding member of Infrastructure & Security team
What they're looking for
- AWS (EC2, RDS, Lambda, CloudWatch, IAM)
- Infrastructure-as-code (Terraform, CloudFormation)
- Containerization and orchestration (Docker, Kubernetes, ECS)
- Security best practices and compliance frameworks (SOC 2, ISO 27001)
- Observability platforms (Datadog, Grafana, Prometheus)
- Scripting languages (Python, Bash, Go)
- Networking and encryption principles
- Secrets management and key rotation
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Basic Capital
Basic Capital is a fintech startup building AI-powered retirement solutions across mobile, web, and API platforms. The company is hiring full-stack engineers, frontend developers, infrastructure specialists, and go-to-market engineers to develop its product, scale its cloud infrastructure, and drive revenue growth.
View all jobs at Basic CapitalLikely interview questions
- Walk us through your experience implementing SOC 2 Type II compliance or similar security frameworks. What were the biggest challenges and how did you overcome them?
- Describe a time you designed an observability system from scratch. What tools did you choose, how did you structure logging/monitoring/alerting, and why?