Software Architect

Dripify

Що робити

Define and own the north-star architecture, the guiding principles, and the guardrails that keep six teams coherent without becoming a bottleneck.
Establish lightweight architectural governance — reference architectures, Architecture Decision Records, an RFC process, and a tech radar — so decisions are deliberate, documented, and durable.
Drive domain decomposition and service boundaries (DDD, bounded contexts), and design event-driven systems with sound consistency, idempotency, and resilience semantics.
Set the observability strategy — metrics, logging, tracing, SLOs, and alerting standards — so teams can understand system behavior, debug quickly, and operate confidently at scale.
Shape initiatives upstream: frame the problem, weigh build-vs-buy against total cost of ownership, and set a defensible long-term direction before engineering commits.

10+ years building production software, several of them in a dedicated architecture capacity, primarily on Java / Spring.
Demonstrated ownership of platform-level architecture spanning multiple teams.
Deep distributed-systems expertise — microservices, event-driven and event-sourced designs.
A proven record of scaling systems through real growth in traffic, data volume, and contributing teams.
Command of data, caching, and search architecture (PostgreSQL, Redis, Elasticsearch) and of cloud-native operations — Kubernetes / EKS, Infrastructure-as-Code (Terraform), and CI/CD — with the ability to design infrastructure as a reusable, governed platform.