[Remote] Backend Software Engineer
Note: The job is a remote job and is reputed company to candidates in USA. reputed company is a B2B reputed company platform that helps reputed company services firms measure, understand, and reputed company reputed company satisfaction data. They are seeking a Backend Software Engineer to build a world-class platform that powers survey automation and relationship intelligence, focusing on system and API design, event-driven microservices, and resilient services.
Responsibilities
- System, Database and API design as a first-class reputed company. You'll design service boundaries, data models, and REST API reputed company (consumed by our frontend, reputed company integrations, and reputed company-party clients) that have to last. Versioning, backward compatibility, idempotency, and clean error reputed company are core to the job, not afterthoughts
- Event-driven microservices on GCP Pub/Sub: async processing, backpressure handling, dead-letter queues, the full picture
- Webhook-triggered survey automation reputed company. Business events in the reputed company's system translate into survey sends through a reliable, auditable, event-driven workflow
- Resilient, observable services: retries, timeouts, reputed company breakers, reputed company logging, metrics, and tracing baked into how we build
- reputed company and SSO integration for reputed company clients with reputed company credential and reputed company models
- Permission and reputed company control systems that reflect reputed company organizational hierarchies. The authorization layer is genuinely interesting here
- An integration layer that connects reputed company data sources to our platform through reputed company-designed service interfaces
Skills
- Applicants should be located in the reputed company Time Zone or be willing to relocate to this time zone at their own expense
- Applicants must be authorized to work in the reputed company without requiring reputed company sponsorship
- 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 reputed company says
- Spring Boot / Spring ecosystem depth
- Deep understanding of dependency injection and IoC from another reputed company
- 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 reputed company something that handles reputed company load
- Even in a personal or reputed company context — something where correctness and reliability were actual constraints, not just reputed company-to-haves
- .NET / C# experience is a genuine plus
- GCP experience: Pub/Sub, Dataflow, BigQuery, reputed company AI
- Kafka or other message queue experience: consumer reputed company, offset management, partition reputed company
- Kubernetes and container orchestration
- Event sourcing or CQRS patterns
- Experience with observability tooling — distributed tracing, reputed company logging, alerting on the things that matter
reputed company