Senior Database Architect - Couchbase - 12+ Years - Immediate Joiners

Job Summary

We are looking for an experienced Database Architect with strong expertise in Couchbase to design, implement, optimize, and maintain scalable, high-performance database solutions. The ideal candidate should have hands-on experience in NoSQL database architecture, data modeling, query optimization, indexing, and high availability.

Key Responsibilities

• Design and implement scalable, secure, and high-performance Couchbase database architectures.
• Develop efficient data models and document structures to support business and application requirements.
• Optimize SQL++ (formerly N1QL) queries, indexing strategies, and database performance.
• Configure and manage Couchbase clusters, replication, and high-availability environments.
• Implement backup, recovery, disaster recovery, and failover strategies.
• Monitor database performance, troubleshoot bottlenecks, and perform root-cause analysis.
• Plan database capacity, scalability, and resource utilization.
• Establish database security, access controls, and performance optimization standards.
• Collaborate with application developers, cloud engineers, and DevOps teams.
• Lead database architecture reviews and recommend best practices for database design and deployment.

Required Skills

• Minimum 6+ years of experience in database technologies, with strong hands-on expertise in Couchbase.
• Strong understanding of NoSQL databases and distributed database architecture.
• Expertise in Couchbase Server, SQL++/N1QL, indexing, and query optimization.
• Experience with data modeling, performance tuning, clustering, and replication.
• Knowledge of high availability, disaster recovery, backup, and recovery mechanisms.
• Experience with Linux and database monitoring and troubleshooting.
• Strong analytical, problem-solving, and communication skills.

Good to Have

• Experience with cloud platforms such as AWS, Azure, or GCP.
• Knowledge of Docker and Kubernetes.
• Experience with database migration, automation, and scripting.
• Familiarity with CI/CD and infrastructure automation tools.

Candidate Requirements

• Experience: 6+ years
• Primary Skill: Couchbase Database Architecture
• Location: Bangalore
• Joining: Immediate joiners preferred/required
• Interview Process: Technical interview followed by managerial discussion

A Database Architectdesigns, builds, and optimizes large-scale database systems, data models, and storage infrastructures to ensure high performance, security, and scalability

Requried Skills::

Typically requires 12+ years of hands-on experience in database administration, database development, or systems architecture

• Deep expertise in SQL and NoSQL databases (e.g., Oracle, MySQL, PostgreSQL, MongoDB, Amazon DynamoDB).
• Hands on Experience in Couchbase
• Proficiency in data modeling tools and cloud architecture.
• Knowledge of data governance, security standards, and high-availability frameworks.

Connect new databases with existing infrastructure, APIs, and cloud platforms (such as AWS, Azure, or Google Cloud)

Partner with software developers, data engineers, and IT teams to guide database implementation and operational best practices

Qualification ::

Education: A bachelor’s degree in Computer Science, Information Technology, Data Science, or a related field (some senior roles prefer a master's degree).

Key Responsibilities

Administer, monitor, and support database platforms including Couchbase, PostgreSQL, and Oracle.

Perform database performance tuning, optimization, and troubleshooting.

Write and optimize complex SQL queries, stored procedures, and scripts.

Ensure database availability, reliability, backup, recovery, and security compliance.

Support production incidents, root cause analysis, and ongoing operational improvements.

Collaborate with application, infrastructure, and support teams to resolve database-related issues.

Required Skills

5 to 10 years of hands-on experience in Database Administration.

Strong experience with Couchbase, PostgreSQL, and/or Oracle databases.

Expertise in performance tuning, query optimization, indexing, and SQL development (Complex Queries, Stored Procedures, Scripts)

Experience with database monitoring, backup, recovery, and maintenance activities.

Production Support, Troubleshooting & RCA

Strong analytical and troubleshooting skills.

Nice to Have

Experience with cloud platforms such as AWS, Azure, or GCP.

Exposure to database automation and scripting

About the Organisation

DataFlow Group is a pioneering global provider of specialized Primary Source Verification (PSV) solutions, and background screening and immigration compliance services that assist public and private organizations in mitigating risks to make informed, cost-effective decisions regarding their Applicants and Registrants.

DataFlow with its best practices in this field such as a high level of data security, cutting-edge technology, rigorous processes, qualified research analysts, and a global network of over 100,000 issuing authorities, verifies professionals credentials from the primary issuer of the document - regardless of its nature.The company complements its advanced verification processes and long-standing industry expertise by adhering to the highest regulatory standards, including the Joint Commission International (JCI), International Organization for Standardization (ISO), and the European Union’s General Data Protection Regulation (GDPR).

About the Role:

We are looking for a Backend Architect / Lead who lives and breathes code. This isn't a role for someone who wants to delegate; it’s for a technical heavyweight who wants to own core product development, define backend architecture patterns, and build scalable, secure, and resilient systems from the ground up. You will join a fast-paced environment where we ship high-quality code under tight timelines. You’ll be expected to take full ownership of our server-side ecosystem, database design, and API layer, ensuring high availability, bulletproof operational excellence, and top-tier performance.

Duties and Responsibilities:

● Architect & Build: Design and implement complex, scalable microservices and monolithic architectures using Node.js, Express.js, and MongoDB (MERN backend stack).

● Heavyweight Coding: Spend the majority of your time writing high-quality, production-ready backend code. You should be comfortable solving complex systems problems using efficient Data Structures, Algorithms, and clean architecture principles.

● Performance & Data Engineering: Own database optimization, query performance, indexing strategies, caching layers (Redis), and system throughput to ensure low-latency API response times.

● Technical Leadership: Establish and enforce industry best practices for REST/GraphQL API design, security standards, code reviews, and automated CI/CD pipelines.

● End-to-End Ownership: Participate in the full SDLC—from initial ideation and system design to deployment, infrastructure setup, and production monitoring on AWS

Qualifications:

● The Deep Diver: You have spearheaded at least one large-scale, complex backend project or system redesign. You can explain every architectural decision, trade-off, database schema choice, and line of code in a deep-dive technical discussion.

● Experience: You have at least 8 years of professional software development experience, with a significant focus on high-traffic, distributed backend systems.

● Tech Stack Mastery: Expert-level proficiency in Node.js, Express.js, MongoDB (Mongoose/Aggregation framework), and TypeScript. Strong hands-on experience with AWS (EC2, S3, ECS/Lambda, CloudWatch) and containerization (Docker).

● Architectural Fluency: A solid understanding of modern backend patterns (Microservices, Event-Driven Architecture, Pub/Sub, Caching strategies, Message Queues like RabbitMQ/Kafka, State Management, and Authentication/Authorization protocols).

● Optimization Expert: Proven experience in tuning database performance, scaling server instances, managing connection pools, and debugging memory leaks or high CPU usage under heavy load.

● Grit & Speed: You thrive in high-pressure environments and enjoy the challenge of meeting tight deadlines without compromising on quality or system reliability.

Skill: Java Architect

Location: Pune Baner Office

Note: Client F2F is mandate

Budget:33 LPA

Experience: 10+ Years

Mandate Skills- Cloud+ Java Architect

Who are we looking for?

We are looking for a Technical Architect, having strong software design and development experience of 9+ years on Core Java, Spring Boot, REST API, AWS & Microservices.

Technical Skills: 

Proficient in software Design and development and familiar with technologies - Java, Java-J2EE, Spring Boot, Hibernate, Ajax, REST API, Microservices etc.

Working knowledge of JVM internals

Working knowledge in Mongo DB

Working knowledge of any database (MySQL or HSQLDB)

Working knowledge of No-SQL database (Mongo or Dynamo DB)

Working experience with messaging (JMS/RabbitMQ) 

R & D on new advanced cloud-based technologies in a test-driven agile development.

Experience in designing and architecting systems with high scalability and performance requirements

Ability to design infrastructure for performance evaluation and reporting of cloud-based services, namely AWS

In depth knowledge of key AWS services like EC2, S3, Lambda, CloudWatch etc.

Certification on AWS architecture desirable

Roles and Responsibilities: 

Participate and contribute in platform requirements/story development.

Contribute to the solutioning, design and design alternatives to the requirements/stories and also participate in design reviews.

Involve in Platform Sprint activities.

Development of assigned stories in appropriate languages defined for each module.

Participate in peer code reviews 

Develop use cases and do unit test cases and execute them part of continuous integration pipeline.

Understand stack deployment and resolve issues with components in stacks across the ecommerce platform.

Process Skills: 

Agile – Scrum and Test-Driven Development

Qualification:

Bachelor of Engineering (Computer background preferred)

Senior Database Administrator (DBA)

Database Reliability & Performance  •  Senior Individual Contributor

• Experience: 6–9 years in production database administration / engineering
• Level: Senior Individual Contributor (hands-on)
• Function: Data Platform — reliability, performance, and governance across relational and distributed SQL & NoSQL DBs.

About the Role

We are hiring a Senior Database Administrator to own the health, performance, and reliability of the data layer behind a high-scale, multi-tenant platform. Our environment spans several independent PostgreSQL database instances, a cache-first read tier, change-data-capture pipeline, analytics and archival stores. Should be capable of implementing NoSQL stores (Cassandra / ScyllaDB) & MySQL  end to end as we scale.

This is a hands-on senior IC role for someone who has run demanding production databases and wants full ownership: partitioning and maintenance, performance tuning, monitoring, uptime, disaster recovery, and the security and data-governance documentation that keeps a regulated, multi-tenant platform audit-ready. You will work closely with, and take direction from, engineering leadership — translating priorities into a well-run, well-documented data platform.

What You'll Own

PostgreSQL Depth

• Administer multiple production PostgreSQL instances (v16+), including schema/DDL review, migrations, and release coordination.
• Design and maintain table partitioning strategies (range/hash/time-based) and automate partition lifecycle — creation, retention windows, and safe drops.
• Own query and instance performance tuning: EXPLAIN/ANALYZE, indexing strategy, autovacuum/bloat management, connection pooling (e.g. PgBouncer), and parameter-group tuning.
• Execute zero-downtime schema changes using expand–migrate–contract / blue-green patterns; assess lock impact and avoid long ACCESS EXCLUSIVE locks on hot tables.
• Manage replica topology (writer/reader endpoints), replication lag, and read-scaling as load grows.
• Partner with app teams on migration tooling (e.g. Flyway) and paired forward/rollback scripts; enforce idempotent, reviewed, tested DDL.

NoSQL & Scale

• Data-model, deploy, and operate distributed NoSQL clusters — Cassandra and/or ScyllaDB — including partition/clustering key design, compaction strategy, repair, and node operations (bootstrap, decommission, scale-out).
• Lead the planned migration of high-volume payload tables from partitioned PostgreSQL to Cassandra/ScyllaDB: capacity planning, dual-write/backfill design, cutover, and validation.
• Tune distributed-store read/write paths, consistency levels, and cluster sizing for predictable latency at scale.
• Support the cache-first architecture (Redis) and change-data-capture / streaming pipelines (e.g. Kafka) that move data to analytics and cold-archival stores.

Operations, Reliability & DR

• Own database uptime and SLOs; build and maintain monitoring, alerting, and dashboards for the key signals (latency, replication lag, CPU/IO, connections, vacuum lag, error rates).
• Define and regularly test backup and disaster-recovery strategy — RPO/RTO targets, point-in-time recovery, restore drills, and cross-AZ / future multi-region readiness.
• Drive incident response for database-related issues: triage, mitigation, root-cause analysis, and follow-up actions.
• Write and maintain runbooks (partition maintenance, failover, archival, DR, migration procedures) and participate in an on-call rotation for the data layer.
• Establish production-change discipline: pre-flight and post-deploy verification, rollback criteria, and backup verification before destructive operations.

Security, Governance & Documentation

• Implement and maintain database access control — least-privilege roles, schema-scoped permissions, and row-level security (RLS) for multi-tenant isolation.
• Own data-governance documentation: PII maps, per-table retention policies, audit-readiness, and the controls behind privacy-regulation compliance (e.g. GDPR / DPDP-style erasure and legal-hold workflows).
• Author and maintain architecture decision records (ADRs), schema documentation, and monitoring/runbook docs so the data platform is legible to the wider team.
• Uphold encryption-at-rest/in-transit posture and safe handling of sensitive columns; keep the data layer aligned with the platform's compliance requirements.

Coding & Automation Bar (Required)

This role is automation-first, not click-ops. The right candidate treats repetitive database work as something to script away and can drop into application code when a problem demands it.

• Strong scripting in Python and Bash for automation of maintenance, backups, partition management, backfills, and health checks.
• Comfortable with infrastructure-as-code (e.g. Terraform) and configuration management (e.g. Ansible) for reproducible database infrastructure.
• Solid SQL and PL/pgSQL; able to read and debug application-layer database code and, worst case, write or patch application code (e.g. Python/Node/Java) to unblock a fix.
• Fluent with Git-based workflows, code review, and CI for database migrations and tooling.

Required Qualifications

• 6–9 years operating relational databases in demanding production environments, with deep PostgreSQL expertise (internals, partitioning, replication, performance tuning).
• Hands-on experience running at least one distributed NoSQL store in production — Cassandra or ScyllaDB strongly preferred (other wide-column/distributed stores considered).
• Proven ownership of backup/DR, monitoring, and incident response for production databases.
• Strong scripting/automation background (Python, Bash) and experience with IaC.
• Experience with managed cloud databases (AWS RDS or equivalent) and understanding of instance/parameter-group tuning, replicas, and failover.
• Experience designing for multi-tenancy and data isolation at scale.
• Clear written communication — able to produce runbooks, ADRs, and governance docs a team can rely on.

Nice to Have

• Experience migrating workloads from PostgreSQL to Cassandra/ScyllaDB (or similar relational-to-distributed migrations).
• Familiarity with Redis as a cache tier and with CDC / streaming pipelines (e.g. Kafka, Debezium).
• Exposure to Flyway (or Liquibase), pgTAP or similar schema testing, and PgBouncer.
• Working knowledge of privacy regulations (GDPR, India DPDP) and audit/compliance processes.

How You Work

• Ownership mindset — takes a directive and runs it to done, with sound judgment on trade-offs.
• Reliability-first and detail-oriented; disciplined about verification, rollback, and documentation.
• Collaborative in a high-performing engineering team; communicates clearly with developers and leadership.
• Pragmatic and scale-aware — designs for where the platform is going, not just where it is.

Role Descriptions: Azure data engineer

SN Required Information Details

1 Role** Azure Cosmos DB Developer

2 Required Technical Skill Set** Primary - PySpark Azure Cosmos DB

Secondary -Python, Microsoft Fabric

3 No of Requirements** 4

4 Desired Experience Range** 8 to 12

5 Location of Requirement Pune

Desired Competencies (Technical/Behavioral Competency)

Must-Have**

1. Deep hands-on experience with Python,Pyspark,Spark batch,notebook in Azure

2. Experience in Cosmos DB – including data modeling, indexing, partitioning, consistency levels, and performance tuning.

3. Strong understanding of Cosmos DB APIs (Core SQL API, MongoDB API, etc.) and integration patterns.

4. Proficiency in query optimization and troubleshooting Cosmos DB performance issues.

5. Experience in data processing using PySpark and Python.

6. Familiarity with Microsoft Fabric for data engineering and analytics workflows.

7. Proficient using source code management tools such as Git or GitHub

8. Experience with Test Driven Development and / or Behavior Driven Development.

Good-to-Have 1. Exposure to data governance tools like Azure Purview.

2. Familiar with various design patterns

3. Familiar with Azure: SQL Managed Instance, Cosmos DB, Storage Services, Azure Functions

4. Global project experience, and excellent communication skills, verbal and written, and soft skills in agile projects

SN Responsibility of / Expectations from the Role

1 Design and implement scalable and high-performance solutions using Azure Cosmos DB.

2 Develop data ingestion and transformation pipelines using PySpark and Azure Data Factory.

3 Optimize Cosmos DB performance through indexing, partitioning, and query tuning.

4 Collaborate with architects and data engineers to ensure best practices in data modeling and cloud architecture.

5 Implement and maintain CI/CD pipelines for automated deployments and testing.

6 Troubleshoot and resolve technical issues related to Cosmos DB and data pipelines.

Desirable Skills:

Keyword:

Skills: Digital : Python~Digital : Databricks~Digital : PySpark~Microsoft Fabric~MySQL

Experience Required: 8-10.

Key Responsibilities

·       System Design: Design secure, scalable, and highly available multi-tenant cloud-based application architectures.

·       Integration Strategy: Build robust APIs, webhooks, and data pipelines for complex enterprise client connections.

·       Technical Guidance: Mentor software engineers and lead critical code and architecture reviews to ensure engineering excellence.

·       Performance & Security: Drive non-functional infrastructure needs including high uptime, strict data privacy compliance, and fast application response times.

·       Cross-Functional Collaboration: Partner closely with Product, Security, and Customer Success teams to align technical execution with business roadmaps.

Required Qualifications

·       Experience: 8+ years of experience in software engineering with at least 3+ years operating as a technical or solutions architect within a B2B SaaS environment.

·       Cloud & DevOps: Deep production knowledge of major cloud infrastructure (AWS, GCP, or Azure), containerization technologies (Docker, Kubernetes), and modern CI/CD automation pipelines.

·       Architecture Patterns: Proven expertise designing microservices, event-driven architectures, and high-performance relational and NoSQL database structures.

·       Communication: Strong written and verbal communication skills, with a proven ability to translate complex technical concepts clearly to both engineers and business stakeholders.

·       Education: Bachelor’s degree in Computer Science, Engineering, or a related field (or equivalent practical work experience).

Preferred Skills

·        Prior experience managing architectural frameworks for enterprise compliance frameworks like SOC2, ISO 27001, or GDPR.

·        Background in building real-time data processing engines, stream frameworks, or integrating enterprise AI/ML components.

Data Architect – Databricks & AWS

• Strong experience in Data Architecture, Data Engineering, Databricks, Apache Spark/PySpark, Python, and Advanced SQL.
• Design and implement scalable ETL/ELT pipelines, data platforms, and Lakehouse architectures using Medallion Architecture.
• Experience with Databricks, Databricks Workflows, Unity Catalog OR Databricks Jobs
• Strong knowledge of Delta Lake, Databricks Workflows, Delta Live Tables (DLT), and dimensional data modeling.
• Hands-on experience with AWS services such as S3, Glue, IAM, Lambda, and CloudWatch.
• Experience with Apache Airflow, Data Warehouse concepts, Git/CI-CD, performance optimization, and data quality.
• Good to have exposure to Kafka/Structured Streaming, Unity Catalog, and modern data governance.

Read This Before Anything Else

We have 6 developers who can ship. What we don't have is someone who turns that into a real engineering function: real architecture, real leverage, real AI-driven advantage. If that gap sounds like an opportunity rather than a headache, you're in the right place. If it sounds like a lot of undefined work with no playbook handed to you, this one probably isn't for you. That's completely okay. There are plenty of great roles that fit differently.

About CraftMyPlate

CraftMyPlate is Hyderabad's go-to platform for food experiences for micro-events: house parties, birthdays, office celebrations, festive gatherings, and more. We're building the operating system for how India discovers, customises, and orders food for smaller events. We're backed by established founders and investors, and we're funded and growing fast. The next phase of that growth runs through engineering.

Where We Stand

Some numbers, because they matter more than adjectives. Order volume has grown 50x in two years, and we're compounding at roughly 3x year over year, without giving up equity to fund it. That means the business runs on its own economics. The growth is real demand, not runway bought with dilution, and every efficient architectural decision this role makes directly protects that.

Most people size up an opportunity by asking what's going to change in ten years. The more useful question, and the one this company is built around, is what won't change. People will keep gathering. They'll keep celebrating, hosting, and marking festivals, in 10 years and in 20. That permanence is the bet. You're not building infrastructure for a trend cycle. You're building for a category that outlasts the current AI wave, the next funding round, and probably us too.

The Technical Reality

Here's an honest read of the engineering problem, not a sanitized version of it.

Event-driven commerce doesn't scale like typical e-commerce. Demand isn't smooth, it's spiky: weekends, festival calendars, and event dates create real load concentration, and each order is tied to a hard deadline that can't slip the way a shipped package can. That has direct architectural consequences: systems need to handle bursty, unpredictable traffic without paying for idle capacity the rest of the time, which is exactly why we're serverless-first on AWS rather than running a fixed fleet sized for peak.

Underneath that, every order touches multiple systems that have to stay consistent: kitchen and vendor fulfillment status, inventory across partners, payment gateway settlement, and refunds, often in real time and often across more than one vendor for a single event. Getting that consistency right across SQL and NoSQL stores, without it becoming a source of support tickets and manual reconciliation, is a real architecture problem, not a CRUD problem.

The AI-agent layer is the next lever, and it's a business lever as much as a technical one. Every workflow we can hand to a well-orchestrated agent instead of a new hire is a workflow that scales without adding headcount, which is exactly how a company grows 3x a year without diluting equity to fund the team behind it. That's why agent orchestration across multiple LLMs, using LangGraph, sits in the "go deep" tier of this role rather than being a nice-to-have.

You'll likely find some of this framing right and some of it worth challenging once you're actually in the codebase. That's expected, and honestly preferred over someone who just nods along.

Why This Role Exists

You'll be the most senior technical person in the company, reporting directly to the founder. Not a manager brought in to run standups. An owner. You set the architecture, you write code yourself, and you make the team materially better. You also own where AI and automation take this company next, starting with our first in-house AI agent product (details shared in the interview), and expanding from there into how the company runs, department by department: HR, finance, marketing, design, development, all sitting on an engineering layer that you design.

If you've outgrown a role where you plan but don't build, or where good ideas die in a committee, this is built to be the opposite of that.

What You'll Own

• Architecture, end to end. Scalable, cost-efficient systems from day one, not "fix it later" engineering. You own the decisions and their long-term consequences.
• Hands-on building. You are still writing code and shipping. This isn't a seat where you review other people's work all day. You lead by building.
• The engineering team. Directly manage, mentor, and level up our 6 developers. Build the technical bar, the review culture, and the calibration that lets the team ship independently.
• The AI-agent roadmap. Own the architecture behind our first AI agent product, then the broader strategy for AI agents and automation across every function in the company, with engineering as the layer underneath all of it.
• Team scaling. Build the next layer of leads under you so execution quality scales without you being the bottleneck.
• Technical accountability. When something breaks, you fix it. You don't escalate and wait.

Our Stack, and the Depth We Expect

Not everything on this list needs the same level of mastery. Some of it you need to own at an architectural level. The rest you need to be strong enough to build yourself, direct the team on, or delegate to AI agents with confidence.

Go deep here. This is where the real architecture decisions live, and where the business impact is highest:

• AWS, serverless first. You should be genuinely well versed in AWS application development, not just "have used AWS." You should be able to design and guide serverless architecture (Lambda, API Gateway, DynamoDB, Step Functions, and similar) as our default way of building, because our demand curve is spiky by nature and fixed infrastructure is money left on the table.
• TypeScript, our primary language across backend and frontend.
• Agent orchestration across multiple LLMs, using LangGraph. This is core to our AI roadmap and our path to scaling operations without scaling headcount. You own how it's architected, not just how it's used.

Working proficiency. Build it yourself, direct the team, or hand it to an AI agent and know if the output is right.

This Is You If

• You've built and shipped real production systems yourself, not just reviewed other people's architecture from a distance.
• You go deep wherever the problem is, and you're comfortable owning the exact stack described above, not just "full-stack" in the abstract.
• You've made engineers around you measurably better, whether or not you've held the title for it yet.
• You're already using AI coding tools and agents seriously, like Claude, Cursor, or similar tools, as part of how you build, not as something you tried once. We'll likely explore this together in the interview.
• You have a bias toward leverage over hours. You'd rather automate or systematize a problem than grind through it. But when something's live and needs to be done right, you see it through completely, with no half-finished work.
• You want to build something for years, not land somewhere comfortable. We'll know the difference from how you talk about your last three years.

This Might Not Be the Right Fit If

• You'd prefer a stable, well-defined role with clear boundaries and someone else making the calls. That's a fair thing to want, just not what this is.
• You'd rather receive direction than bring us architecture and AI strategy yourself.
• You haven't yet gotten hands-on with AI coding tools in your daily work.
• You're drawn more to the title than the work behind it.

If none of that sounds like you, we'd love to hear from you.

Requirements

• 5 to 7 years of experience in software engineering, with real ownership of architecture-level decisions, not just feature delivery.
• Prior experience leading or mentoring engineers, formally or informally.
• Tier-1 or Tier-1+ engineering college strongly preferred (IIT, BITS, top NIT tier, or equivalent). We'll consider other institutions only with clearly commendable, verifiable work: real systems you can walk us through in depth, strong open-source contributions, or a track record that speaks for itself. Pedigree is a proxy for speed, not a checkbox. We test for the underlying ability regardless.
• Comfortable in an early-stage environment: undefined problems, few processes, and the expectation that you help define both.

Compensation

Competitive, with equity. We're formalizing a structured ESOP program alongside this hire. Specific numbers are discussed directly in later interview rounds.

If reading this got you a little excited about what you'd build here, we'd genuinely love to talk. If it didn't quite land, no hard feelings. We just want the right fit for both sides.