Remote Senior Software Engineer, Services
Remote Senior Software Engineer, Services
Posted 46 days ago
SENIORITY
Lead
About the role
- Design and build shared backend services and APIs used across multiple systems
- Define service boundaries, contracts, and data models
- Own the full SDLC: design, development, testing, deployment, and iteration
- Contribute to domain modeling and system design decisions
- Ensure services are scalable, reliable, and reusable
- Improve system cohesion and reduce duplication across tools and products
- Use AI tools to accelerate development while maintaining high code quality
- Balance speed with long-term maintainability and extensibility
- 7+ years of software engineering experience
- Strong backend expertise with the ability to operate across the full stack when needed
- Experience designing service-oriented or distributed systems
- Familiarity with domain-driven design (DDD) principles
- Exceptional systems thinking and ability to model complex domains
- Experience deploying and operating applications in cloud environments (AWS, Azure, or GCP)
- Solid understanding of the full SDLCDeep experience with (i.e., daily usage of) AI coding toolsAI-Native Development
- Hands-on experience using AI-assisted development tools beyond basic code generation
- Ability to leverage AI across the workflow (e.g., prototyping, debugging, test generation, QA, code review, security analysis)
- Ability to balance AI-assisted development with sound system design and long-term maintainability
- Familiarity with modern AI-enabled development environments and practices
- Preferred Experience
- Infrastructure as Code (e.g., Terraform)CI/CD and modern DevOps practicesAPI design (REST, GraphQL, event-driven systems)
- Messaging systems (e.g., Kafka, SQS), Event sourcing, CQRS patterns
- Data modeling (SQL and NoSQL)
- Observability practices (logging, metrics, tracing)
- Experience with one or more of the following languages: Python, TypeScript, Golang, RustBasic understanding of data engineering principles
- How we work
- Small teams, high ownership, minimal handoffs
- Fast, iterative delivery with an emphasis on sound system design
- Pragmatic decision-making over over-engineering
- Engineers are expected to operate across the stack, not within silos
- You design services that are reused across multiple systems
- You create clean abstractions that simplify downstream development
- You balance speed with long-term maintainability
- You improve system consistency and reduce fragmentation
- You effectively use AI tools to increase speed without sacrificing quality
- Crosslake Technologies
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
