DevOps Engineer - Contractor
Job description
About the role
The role designs and delivers backend infrastructure for market data and business systems. It focuses on stability, scalability, and performance under global load.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Tune services and manage concurrency to improve stability, throughput, and response efficiency for global users.
Build core services including user management, authentication, authorization, and open API capabilities for internal and external consumers.
Diagnose production incidents, analyze performance metrics, and resolve complex technical problems to restore service and prevent recurrence.
Requirements
Hold a Bachelor's degree or higher in Computer Science or a related field.
Bring 3-5+ years of Java backend development experience with a solid technical foundation, and outstanding fresh graduates may also be considered.
Demonstrate mastery of Java core technologies, including deep knowledge of JVM, concurrency programming, collection frameworks, I/O, and network communication.
Apply familiarity with Spring Boot and Spring Cloud, with hands-on experience in microservices development and governance.
Design and develop high-performance, high-concurrency systems, using caching, asynchronous processing, rate limiting, circuit breaking, and thread pools.
Operate common middleware such as MySQL, Redis, Kafka, and Elasticsearch, understanding use cases and performance optimization methods for each.
Address common distributed system challenges including idempotency, consistency, distributed locks, transaction processing, and service fault tolerance.
Show strong analytical and problem-solving skills to independently troubleshoot production issues and resolve complex problems.
Implement authentication and authorization mechanisms, using OAuth2, JWT, SSO, RBAC, and Session in designs and implementations.
Use Kubernetes for containerized deployment, service orchestration, auto-scaling, and configuration management in production environments.
Value AWS cloud services as a practical advantage for cloud-native implementations.
Maintain strong coding standards, produce clear documentation, and work effectively within a team.
Practical notes
The role is a contractor position with a global location. Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
Questions to ask
Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.