We are seeking an experienced Lead Developer to lead technical delivery for a team: hands-on coding, architecture alignment, and raising the bar on quality and operations. You will design and ship backend capabilities, partner on requirements and trade-offs, and help the team deliver reliably in production.
Responsibilities
Design, implement, and review features and APIs (services, integrations, data access).
Own reliability for services you touch: correctness, performance, observability, and safe releases.
Work with the team on architecture for new capabilities and on improving existing systems (database schema, caching, deployment, operational runbooks).
Partner with product and other engineering teams on requirements, estimates, and technical trade-offs.
Review code, clarify design, and mentor engineers informally; contribute to a culture of quality and learning.
Identify and drive process improvements: clearer contracts, better tests, CI/CD hygiene, and reduced operational toil.
Create and maintain technical documentation where it helps onboarding and operations.
Requirements
8+ years of professional experience shipping production backend services in Java (e.g. Spring Boot) or an equivalent JVM stack; comfortable with REST APIs, validation, auth integration (e.g. OAuth2 / JWT), and common Spring patterns.
Data stores — solid PostgreSQL: schema design, migrations (e.g. Flyway or similar), indexing, transactions, and debugging slow queries.
Caching — hands-on use of Redis or Valkey (or similar): cache keys, TTLs, invalidation, and failure modes when cache is down or stale.
Build and quality — Gradle or Maven, unit/integration tests, constructive code review habits, and CI-friendly workflows.
Containers and cloud — Docker; deploying or operating services on AWS (or similar): configs, secrets, logs, metrics.
Observability — metrics, logs, and tracing sufficient to find regressions and latency issues in production.
API and integration design — clear contracts, versioning or backward-compatibility discipline, and safe handling of errors and idempotency where it matters.
Education — Bachelor’s degree in Computer Science, Engineering, or related field (or equivalent practical experience).
Version control — strong experience with Git and collaborative branching/review practices.