Sr. Backend Engineer

This a Full Remote job, the offer is available from: South America, North America, United States, Latin America, Colombia, Chile, Mexico, California (USA)

Peek is the operating system powering the experiences industry - from museums and attractions to tours and activities. With over $7B in bookings, Peek’s AI-powered platform has helped thousands of merchants to increase revenues, save time, and deliver seamless guest experiences. Customers include MoMA, Whitney Museum, Seattle Aquarium, Bryant Park & Looping Group. The company has raised over $150 million from institutional investors Westcap, Goldman Sachs, and SpringCoast Partners. Learn more at

As a remote-first company recognized by Forbes as one of America's Best Startup Employers and by Built In as a 2025 and 2026 Best Place to Work, we are a global team of "Peeksters" who "Obsess Over Our Customers," "Accomplish Big Things," "Collaborate With Purpose," and "Get Better Every Day.

The Role

We work on several systems: our ACME operations management suite, embeddable scheduling and booking widgets, B2B and B2C sales and support tooling, and custom solutions for enterprise operators. The work is technically varied and the stakes are real: operators depend on this software to run their businesses.

We’re hiring a Senior Backend Engineer with strong technical depth who is also highly effective with AI-assisted development. You reason independently about complex systems, find the problems that aren't obvious from the requirements, and use AI as a tool to build faster while owning every decision it informs. That means you know how to break down ambiguous problems, delegate to agents, review their work critically, and course-correct when things go sideways. You'll join the platform team, working deep in our existing systems, including ACME Core, to make other teams faster and safer, using AI-assisted development as a force multiplier for your engineering judgment, not a replacement for it. The platform team works closely with DevOps, who own our infrastructure, so this is a backend-focused role rather than an infrastructure one.

Over the past few months, we've seen a step-function improvement in the reliability and capabilities of long-running AI agents. We're adapting our engineering practice to match, and we want strong backend engineers who are already building this way and excited to push it further.

What you’ll do

  • Work as part of the platform team, improving the backend systems, tooling, and practices that other teams build on. Feature development is still part of the role where it fits.

  • Identify automation opportunities across the engineering workflow (repetitive manual work, slow or fragile processes, recurring operational toil) and build the solutions, using AI agents where they help.

  • Enable other teams: build and maintain shared services, libraries, and APIs, make the right way the easy way, and unblock engineers who depend on the platform through guidance, documentation, and code review.

  • Own security fixes and dependency updates across our backend systems: triage vulnerabilities, plan and ship upgrades safely in an existing codebase, and make sure they don't break the teams and services that depend on them.

  • Identify and diagnose performance bottlenecks, and recognize scalability limits before they become production problems.

  • Reason about concurrency, failure modes, and reliability across APIs and integrations.

  • Own your services in production: monitoring, debugging, performance, and reliability. When something breaks, you get to root cause and fix it properly.

  • Contribute to our AI-first engineering culture, share patterns, document what works, and help the team level up on how we build with AI.

  • Use AI tools fluently - Claude Code, Augment or equivalent, to compress implementation time, then critically review everything that comes out of them. AI makes a strong engineer faster; it does not replace technical judgment.

What We're Looking For

Required

  • 5+ years of professional backend development using Java, with a meaningful track record of shipping and operating production systems.

  • Strong system design: you make sound architectural decisions, think about tradeoffs, edge cases, and what happens when things scale or fail, and you know when a simple solution is enough.

  • Strong backend fundamentals: API design, integrations, concurrency, failure modes, and service reliability.

  • Deep understanding of database behavior: data modeling, query design, indexing, and the performance implications of your choices.

  • Proven ability to diagnose performance bottlenecks and debug complex production issues to root cause, including problems that aren't obvious from the requirements.

  • Comfortable working in an existing, evolving codebase: you can get up to speed quickly, make safe incremental changes, and leave things better than you found them, without defaulting to rewrites.

  • Hands-on, daily use of AI coding tools (Claude Code, Codex, Cursor or equivalent) in a production engineering workflow, as a force multiplier on top of strong fundamentals.

  • Ability to critically evaluate AI-generated code: catch logic errors, identify security issues, assess maintainability, and own what gets merged regardless of how it was written.

  • Clear communicator: you can articulate why you made a technical choice, flag when a spec has holes, and disagree constructively.

  • Interest in Elixir or functional programming languages as we expand our stack

Nice to haves

  • Experience building B2B SaaS products, ideally with complex multi-tenant data models or transactional workflows.

  • Experience on small, high-output teams where you've had to make architectural calls without a committee.

  • Familiarity with frontend development and JavaScript/TypeScript (Angular or modern JS frameworks), enough to collaborate effectively with frontend engineers and understand how your APIs are consumed.

  • Experience on a platform, internal tooling, or developer-enablement team, including security patching and dependency upgrades in a large existing codebase.

  • Background in the travel, hospitality, or experiences industry.

What We Value

A few things that define how we build:

  • Depth first. We value engineers who understand how systems actually behave: databases, concurrency, failure modes, and performance. AI amplifies that understanding; it doesn't replace it.

  • Judgment over speed. AI compresses implementation time. What differentiates engineers now isn't typing speed or memorized syntax, it's the ability to make the right calls on what to build, how to build it, and when it's not ready to ship.

  • Ownership. You built it? You own it. That includes AI-generated code. You know when to use agents and when to do it yourself.

  • Directness. We want people who ask hard questions, surface problems early, and are willing to push back on a bad spec rather than build it and hope for the best.

  • Quality as a habit. Peer code reviews, test coverage, and clean APIs are not optional. We move fast, but not by cutting corners on the things that compound.

Peek Travel Inc. is an equal-opportunity employer.  All qualified applicants will receive consideration for employment without regard to race, color, religion, national origin, sex, sexual orientation, gender identity, veteran status, disability, or other legally protected status.

If you are unable to apply due to incompatible assistive technology or a disability, please contact us at talent@peek.com.  We will make every effort to respond to your request for disability assistance as soon as possible.

This offer from "Peek" has been enriched by Jobgether.com and got a 0% flex score.
Back to blog

Other Jobs To Apply

No other job posts for this day.

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...