Kapitus
Software Engineer II - Engineering
About this role
Kapitus seeks a Software Engineer II to design and build modern backend systems that replace legacy applications, primarily using Python and Flask on AWS. You'll contribute to platform architecture, mentor junior developers, and help small businesses access lending solutions through well-crafted, scalable software.
What you'll do
- Design, develop, test, and maintain new backend software while establishing foundations for future growth
- Define architecture, technical patterns, and engineering practices for a new platform while integrating with legacy systems
- Develop backend services in Python with emphasis on Flask, and build AWS solutions using Lambda, Cognito, SNS, SQS, and DynamoDB
- Maintain and improve deployment pipelines, CI/CD processes, and infrastructure using OpenTofu and Terraform
- Collaborate with stakeholders and technical leadership to understand roadmaps, communicate progress, and deliver in Agile/Scrum environments
- Mentor junior developers on Python and engineering best practices while participating in code reviews
What they're looking for
- Python (5+ years)
- Flask
- AWS services (Lambda, Cognito, SNS, SQS, DynamoDB)
- CI/CD pipelines and deployment processes
- Infrastructure-as-code (OpenTofu, Terraform)
- Salesforce (2+ years)
- Agile/Scrum methodologies
- Technical leadership and mentorship
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.
Kapitus
Kapitus builds cloud-based solutions and infrastructure on AWS, focusing on serverless microservices and secure, scalable enterprise systems. The company is hiring senior software engineers and DevSecOps specialists to design, build, and maintain high-impact cloud infrastructure.
View all jobs at KapitusLikely interview questions
- Describe your experience migrating legacy systems to modern architectures—what challenges did you face and how did you address them?
- Walk us through a time you designed and implemented a Flask-based backend service; what architectural decisions did you make and why?