Real systems that enterprise clients depend on. Not greenfield experiments, but a world class brand new platform with production code that has to be correct, observable, and resilient:
Integration layer that ingests structured data from enterprise sources (Snowflake, BigQuery, SQL databases) and routes it through our platform
A Snowflake-to-BigQuery bridge over ODBC: custom infrastructure work that will serve as the pattern for all future enterprise integrations
Webhook-triggered survey automation engine. Business events in the client’s system translate into survey sends through a reliable, auditable event pipeline
REST APIs consumed by our frontend, enterprise integrations, and third-party clients — you’ll design contracts that have to last
Event-driven microservices on GCP Pub/Sub and Kafka — async processing, backpressure handling, dead-letter queues, the full picture
Security and SSO integration for enterprise clients with complex credential and access models
Permission and access control systems that reflect matrix organizational hierarchies — the authorization layer is genuinely interesting here

Requirements

Java you understand at the JVM level. Concurrency, memory model, garbage collection, exception hierarchy — you can reason about what the runtime is doing, not just what your code says.
Spring Boot / Spring ecosystem depth. Or deep understanding of dependency injection and IoC from another framework — we care that you understand the pattern, not just the annotations.
SQL and data modelling confidence. You can write a query with joins, aggregations, and window functions. You think about indexes. You understand what an N+1 problem looks like in production.
API design instincts. You know what makes an API contract good and what makes it a maintenance nightmare. You’ve thought about versioning, error semantics, and idempotency.
Systems thinking under failure. You consider retries, timeouts, idempotency, and consistency before you consider happy paths.
You’ve built something that handles real load. Even in a personal or academic context — something where correctness and reliability were actual constraints, not just nice-to-haves.

Benefits

How We Hire
We hire on ability, not tenure. We don’t care whether your experience comes from a top university, a bootcamp, an open-source project, or a side hustle you built at 2am. What we care about is whether you can think clearly, build well, and learn fast.
Our interview process is deliberately hard. If you make it through, you’ll know you earned it — and so will we. We test fundamentals, systems thinking, and the ability to reason through problems you haven’t seen before. We don’t ask you to recite design patterns. We ask you to think.
Our backend interview tests: Java fundamentals and JVM reasoning, systems design, API design, SQL, and your ability to think through distributed system failure modes. We give you real-world scenarios, not toy problems. Expect to discuss trade-offs, not just correct answers.

Applicant Tracking System Keywords

Tip: use these terms in your resume and cover letter to boost ATS matches.

Hard Skills & Tools

JavaSpring BootSQLAPI designevent-driven microservicesGCP Pub/SubKafkadata modelingconcurrencydependency injection

Soft Skills

systems thinkingproblem-solvingattention to detailcollaborationadaptabilitycritical thinkingcommunicationreliabilitycreativityanalytical skills