Posting record
Open 10+ days
- Prox Works' site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Prox Works, so its true age is longer.
Last checked Nov 3, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat it asks of you
- 5+ years of experience
What the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
We’re seeking a highly skilled, execution-focused Senior Backend Engineer with a minimum of 5 years of experience to join our team. This role demands hands-on expertise in building and scaling distributed systems, strong proficiency in Java, and deep knowledge of cloud-native infrastructure. You will be expected to design robust backend services, optimize performance across storage and caching layers, and enable seamless integrations using modern messaging and CI/CD pipelines.
You’ll be working in a high-scale, high-impact environment where reliability, speed, and efficiency are paramount. If you enjoy solving complex engineering challenges and have a passion for distributed systems, this is the right role for you.
Responsibilities
- Design, develop, and maintain distributed backend systems at scale.
- Write high-performance, production-grade code in Java .
- Architect and optimize storage systems , ensuring efficient query performance and scalable data models.
- Implement caching strategies to reduce latency and improve system throughput.
- Build and manage services leveraging AWS cloud infrastructure .
- Develop resilient messaging pipelines using Kafka (or equivalent) for real-time data processing.
- Define and streamline CI/CD pipelines , ensuring rapid and reliable deployment cycles.
- Collaborate with product managers, frontend engineers, and DevOps to deliver end-to-end solutions.
- Monitor system performance, identify bottlenecks, and apply proactive fixes.
- Drive best practices in software engineering, testing, and code reviews.
Requirements
- 5+ years of experience in backend engineering, with deep hands-on coding experience.
- Strong proficiency in Java and familiarity with modern frameworks.
- Proven track record in building scalable distributed systems .
- Hands-on expertise with AWS services (e.g., EC2, S3, Lambda, DynamoDB, RDS).
- Solid understanding of messaging systems like Kafka, RabbitMQ, or similar.
- Strong grasp of query performance optimization and storage system design .
- Experience with caching solutions (Redis, Memcached, etc.).
- Familiarity with CI/CD tools (Jenkins, GitHub Actions, GitLab CI, etc.).
- Excellent problem-solving skills and ability to thrive in fast-paced environments.
- Strong communication and collaboration skills, with a proactive mindset.
Benefits
- Best in class salary : We hire only the best, and we pay accordingly.
- Proximity Talks : Meet other designers, engineers, and product geeks — and learn from experts in the field.
- Keep on learning with a world-class team : Work with the best in the field, challenge yourself constantly, and learn something new every day.
About us—
Proximity is the trusted technology, design, and consulting partner for some of the biggest Sports, Media, and Entertainment companies in the world. We’re headquartered in San Francisco and have offices in Palo Alto, Dubai, Mumbai, and Bangalore.
Since 2019, Proximity has built high-impact, scalable products used by millions of users every day. Today, we are a global team of engineers, designers, product managers, and experts solving complex problems and building cutting-edge technology at scale.
Something wrong with this posting?