Backend Engineer

About the Role

We are seeking a Backend Engineer to take ownership of our time and attendance backend system, with the goal of eventually expanding into leading the backend architecture for our access control solutions. These are critical parts of Keyo’s privacy-first identity platform—solutions that power real-time decision-making for physical access, workforce tracking, and operational compliance.

You will play a central role in designing, building, and maintaining backend services that are scalable, secure, and high-performing. This is an ideal role for someone excited by real-world impact, ownership of product-critical systems, and building things the right way from the ground up.
 

Responsibilities  

• Design and develop RESTful APIs and backend services for time and attendance, and later, access control systems.
• Write clean, efficient, and maintainable code—primarily in Python using Django or similar frameworks.
• Build and optimize data models and pipelines for high-throughput event tracking
• Experience building backend services that interact with complex frontends or mobile apps
• Implement robust data models and database schemas in PostgreSQL for time-tracking and access-related data.
• Ensure all backend systems are secure, scalable, and optimized for performance.
• Design for fault tolerance and high availability, especially in mission-critical real-time decision systems (e.g., opening a door, denying access).
• Support testing and validation of APIs and business logic for edge conditions, failovers, and integrations.
• Eventually support hardware integration logic with access points, biometric readers, and real-time hardware events.

• Stay informed on best practices in system architecture, backend development, and privacy/security protocols.

   

Skills & Qualifications:

Required Technical Skills:

• Proficient in Python, with strong experience using Django, Flask, or FastAPI.
• Deep understanding of PostgreSQL and relational database performance tuning.
• Strong grasp of RESTful API development and architectural patterns.
• Familiarity with Go (for future microservices or high-perf modules)
• Experience using Docker for containerization and deployment.

• Ability to write secure, well-tested code that scales with growing usage.

   

Preferred Skills:

• Experience working with IoT or hardware-integrated systems.
• Familiarity with CI/CD pipelines, Git workflows, and testing strategies.
• Familiarity with Snowflake, data warehouses, and analytics pipelines
• Knowledge of cloud platforms like AWS or GCP.
• Exposure to GraphQL for future-facing API design.
• Experience with monitoring tools such as Prometheus and Grafana.

• Background in access control systems, real-time event processing, or badge management is a major plus.

   

What We Offer

• Remote-first Work Environment
• Growth Opportunities
• Competitive Compensation

• Work at a mission driven company with team members from around the world

   

How to Apply

Start your application with the word banana this helps us confirm that you’ve read the job description and understand the requirements.

To apply:

• Submit your resume.
• If you advance past the second interview, you’ll be asked to walk us through a project you’ve completed.
• All interviews require your camera to be turned on.

Important:

Reading from any AI agent during the interview will immediately disqualify you. We fully embrace AI as a tool for engineers, but we need critical thinkers. Show us that you’re a great fit by demonstrating extreme ownership, strong teamwork, technical excellence, and problem-solving skills.

Equal Employment Opportunity Employer

We are proud to be a global team united by diverse perspectives, cultures, and experiences. Our commitment to inclusion and respect extends across every border, embracing the unique contributions that individuals bring from all walks of life and every corner of the world.

We are an equal opportunity employer and welcome everyone, regardless of race, color, religion, gender, gender identity, sexual orientation, age, national origin, disability, veteran status, or any other characteristic that makes you uniquely you. Your story matters, and we value the richness it adds to our shared journey.

We strive to create an environment where every team member—no matter where they are in the world—feels seen, heard, and empowered to succeed. From hiring to development, promotions, and beyond, we are dedicated to ensuring equity and fairness for all.

Together, we are building a global community where collaboration and respect drive innovation and belonging. 

Application Prompt (Loom Video Required)

This isn’t just another backend gig. You’ll be owning product-critical infrastructure that impacts real-world identity, access, and operational compliance. Before diving into code with us, we’d like to understand how you think, how you build under pressure, and how you communicate complex decisions clearly.

Scenario

You’ve just been onboarded and have taken ownership of the time and attendance backend. A critical client with 24/7 operations reports that clock-in data from multiple locations is missing or delayed, especially during peak traffic.

Here’s what you discover:

• The system uses a Python/Django backend with PostgreSQL, receiving real-time events from biometric terminals.
  
   
• Load tests reveal spikes in API latency, and database writes are sometimes locking during bursts of 500+ concurrent events.
  
   
• A product stakeholder is asking for a quick fix while still expecting long-term stability.
  
   
• Another engineer suggests using Redis queues or a message broker like RabbitMQ, but there’s no clear implementation yet.
  
   

In your Loom (5–7 minutes), walk us through:

1. Your Diagnostic Process:
   
    
   • How would you identify the root cause of the data lag or loss?
     
      
   • What tools, logging strategies, or monitoring frameworks would you use to gain visibility?
     
      
2. Your Short-Term Fix + Long-Term Plan:
   
    
   • How would you quickly stabilize the system to prevent data loss today?
     
      
   • Then, how would you refactor or re-architect the backend to scale properly (e.g., message queues, DB tuning, etc.)?
     
      
3. How You’d Communicate with Stakeholders:
   
    
   • What would you say to the product lead who wants this fixed now?
     
      
   • How do you bring non-engineers along on a technically nuanced but critical problem?
     
      

Start your video by saying the word “banana” so we know you’ve read the prompt.

Your Loom should be:

• Clear and unscripted (bullet points are okay)
  
   
• Focused on how you approach problems, not perfection
  
   
• Respectful of time (5–7 minutes max)
  
   

Please submit your Loom link along with your resume and any technical portfolios or GitHub links.