Senior Database Developer (Oracle to PostgreSQL)

You'll own heterogeneous database migrations end to end for enterprise customers moving off Oracle and SQL Server onto PostgreSQL and Aurora PostgreSQL. That means running the AWS DMS and SCT toolchain, then doing the part the tools can't: rebuilding procedural business logic in PL/pgSQL when SCT flags a gap it can't close on its own. You ship the runbook, you run the cutover, you validate the result. 

What you'll do?

• Lead end-to-end database migration initiatives, including assessment, planning, schema conversion, execution, and post-migration validation.
• Design, configure, and manage AWS DMS and SCT environments while ensuring migration quality, performance, and reliability.
• Author comprehensive migration runbooks that define execution procedures, validation checkpoints, rollback plans, and operational readiness activities.
• Perform database migration assessments, dependency analysis, compatibility reviews, and migration strategy recommendations.
• Collaborate with infrastructure, application, security, and platform teams to ensure successful migration outcomes.
• Drive migration testing activities, including functional validation, performance testing, failover testing, and production readiness reviews.
• Provide technical leadership and guidance to migration teams while ensuring adherence to AWS migration best practices and governance standards.
• Lead conversion and refactoring of procedural database code — Oracle PL/SQL (packages, procedures, functions, triggers, cursors) and SQL Server T-SQL (stored procedures, functions, triggers) — into PostgreSQL/Aurora PostgreSQL PL/pgSQL, resolving semantic and behavioral differences identified by SCT.

What we're looking for?

• 8–12 years of professional experience in database architecture and migration delivery
• Hands-on expertise in AWS Database Migration Service (DMS) and AWS Schema Conversion Tool (SCT) for enterprise-scale database migrations
• Deep proficiency in Oracle, SQL Server, PostgreSQL, and Aurora PostgreSQL environments, including migration planning, execution, and optimization
• Proven background in delivering heterogeneous database migrations across on-premises, cloud, and AWS environments
• Knowledge of production database operations, including backup and restore strategies, parameter tuning, performance optimization, and failover testing
• Skills in authoring and executing migration runbooks, validation plans, cutover procedures, rollback strategies, and post-migration stabilization activities
• Strong understanding of AWS database services, migration best practices, and integration with broader cloud migration programs
• Experience engaging directly with enterprise customers, architecture teams, and migration stakeholders to drive successful delivery outcomes
• Strong hands-on experience converting Oracle PL/SQL and SQL Server T-SQL business logic to PL/pgSQL, including handling of exception handling models, cursor semantics, autonomous transactions, sequences/identity columns, implicit data type conversions, and proprietary built-in packages/functions with no native PostgreSQL equivalent
• Ability to identify and remediate SCT action items and manual conversion gaps in procedural code (e.g., DBMS_* packages, UTL_* utilities, SQL Server system procedures, dynamic SQL, and nested/recursive procedure calls) and validate converted logic through functional and regression testing.

You'll be preferred if you

• Have tuned production database performance, backup and restore strategy, and failover testing in high-stakes environments.
• Have led migration teams or mentored engineers through complex conversions.
• Bring experience with broader AWS cloud migration programs beyond the database layer.

We are looking for a Database Engineer (PostgreSQL) with 1-5 years of experience to manage, optimize, and maintain PostgreSQL databases. The ideal candidate will have expertise in PostgreSQL, SQL Optimization, Database Design, Performance Tuning, Data Migration, and Backup & Recovery.

Responsibilities:

• Design, develop, and maintain PostgreSQL databases.
• Optimize SQL queries and improve database performance.
• Perform database design, indexing, and schema management.
• Execute data migration, backup, recovery, and disaster recovery activities.
• Monitor database health and troubleshoot performance issues.
• Collaborate with development teams to ensure scalable database solutions.

Requirements:

• 1-5 years of PostgreSQL database experience.
• Strong SQL and performance tuning skills.
• Knowledge of database backup, recovery, and migration processes.

Description :

Key Responsibilities :

Primary Database Expertise :

1. One resource should have PostgreSQL as their primary database expertise.

2. One resource should have MySQL as their primary database expertise.

3. One resource should have either PostgreSQL or MySQL as their primary database expertise.

Secondary Database Skills :

- Proficiency in other databases such as MongoDB, MSSQL, ElasticSearch, Oracle, and Redis is a plus.

- Hands-on experience with databases in cloud environments, including GCP, AWS, or Azure, is a must.

- Familiarity with database migrations on GCP, AWS, or Azure cloud platforms is advantageous.

Qualifications and Skills :

- Minimum of 4 years of hands-on experience with MySQL, PostgreSQL, and MSSQL databases.

- Strong logical thinking skills to analyze and solve complex database-related issues.

- Excellent communication and articulation abilities, with the capacity to interact effectively with both technical and non-technical stakeholders.

- Proficiency in handling customer calls and addressing their database-related queries and concerns.

- Experience in one of the following primary databases : PostgreSQL, MySQL.

- Knowledge of secondary databases like MongoDB, MSSQL, ElasticSearch, Oracle, and Redis is a plus.

- Prior experience with database administration in GCP, AWS, or Azure cloud environments.

- Familiarity with database migration processes on cloud platforms is a beneficial skill.

This role offers an opportunity to work with diverse database technologies and cloud platforms, making it an ideal position for a skilled Senior DBA who enjoys a dynamic and challenging environment. If you have a strong database background and are looking to take your career to the next level, we encourage you to apply.

Qualifications

● 3-8 years experience in Cloud Database Administration

● Proficient in PostgreSQL database management, including installation, configuration, and performance tuning.

● Experience with Amazon RDS or Cloud SQL and managing databases in cloud environments.

● Proficient in PostgreSQL/MySQL database management, including installation, configuration, and performance tuning.

● Proven experience as a Database Administrator with a focus on

PostgreSQL/MySQL.

● In-depth knowledge of database design, implementation, and management for both PostgreSQL/MySQL environments.

● Familiarity with database security, backup procedures, and performance tuning for both systems.

● Strong analytical and problem-solving skills.

● Excellent communication and collaboration abilities.

● Relevant certifications (e.g., PostgreSQL Certified Professional, MySQLDatabase Administrator) are a plus.

Skills:

● Expertise in PostgreSQL/MySQL database management systems.

● SQL programming and query optimization for both databases.

● Data modeling and database design for PostgreSQL/MySQL.

● Backup and recovery procedures for both environments.

● Performance tuning and optimization for PostgreSQL/MySQL.

● Security protocols and measures for PostgreSQL/MySQL.

● Capacity planning and scalability for both systems.

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: Oracle DBA – GoldenGate & Database Migration

Location: Bangalore / Hyderabad

Experience: 8–15 years

Key Responsibilities:

• Manage Oracle databases in production and non-production environments.
• Strong hands-on experience with Oracle GoldenGate for replication, CDC, and data synchronization.
• Lead/support database migration, upgrade, and transformation projects.
• Perform database performance tuning, backup/recovery, troubleshooting, and high availability activities.
• Work on migration planning, execution, validation, and post-migration support.
• Collaborate with application, infrastructure, and cloud teams for end-to-end migration activities.

Must-Have Skills:

• 8–15 years of strong Oracle DBA experience.
• Hands-on expertise in Oracle GoldenGate.
• Proven experience in DB migration projects.
• Strong knowledge of Oracle RAC, Data Guard, RMAN, performance tuning, and troubleshooting.
• Good understanding of Unix/Linux and SQL/PLSQL.
• Excellent communication and stakeholder-management skills.

Location: Bangalore / Hyderabad

CTC: Up to ₹24 LPA

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

Data Platform Engineer

Design, automate, and scale our data platform — this is an engineering role, not a traditional "DBA job.

Must-have :

• Data modeling & schema design (from first principles, not just maintenance)
• PostgreSQL (deep, hands-on — partitioning, replication, tuning)
• Any distributed NoSQL store (Cassandra, ScyllaDB, or similar wide-column/distributed DB) (real production experience)
• Python (automation & tooling, not just scripting)
• DevOps & CI/CD (building pipelines, not just using them)
• Terraform (infrastructure-as-code)

You'll:

• Design schemas, partitioning strategies, and lead the Postgres → Cassandra migration end-to-end
• Own PostgreSQL performance, replication, and zero-downtime schema changes
• Build Python-based automation to eliminate repetitive DB work
• Own CI/CD pipelines and Terraform-based infra provisioning
• Drive uptime, DR, monitoring, and incident response
• Own multi-tenant security (RLS, least-privilege access) and data governance

Experience: 4–9 years, data/database/platform engineering in demanding production environments.

Bonus: Kafka/Debezium (CDC), Redis, Flyway/Liquibase, GDPR/DPDP exposure.

10+ years of experience in Data Architecture, Data Engineering, or Data Platforms

• Strong expertise in IBM DB2 / On-Prem Relational Databases

• Strong expertise in PostgreSQL

• Hands-on experience with the Azure Data Ecosystem, including:

▪ Azure Data Factory (ADF)

▪ Azure Data Lake Storage Gen2 (ADLS Gen2)

▪ Azure Databricks / Synapse Analytics

▪ Azure Event Hub / Service Bus

▪ Azure Functions

This is a backend role. You won't build screens, and you don't need frontend experience. The mobile team will add a language picker and pass a locale to the backend. Everything behind that is yours: the data model, content pipelines, LLM generation, retrieval, audio, notifications, and making sure all of it holds up in production.

What you'll build

1. The language data model

• Design how language lives in the database: user language preference, per-story translations, fallback chains (e.g. pt-BR → pt → en), and versioning so a translation is marked stale when its English source changes.
• stories.translations (jsonb) already exists and nothing reads it yet. Decide whether it stays, or whether we move to a dedicated story_translations table, and write down why.
• Everything ships as new, reversible migrations. We never edit an existing migration.

2. The content translation pipeline

• Our library has already been translated into several languages using the Anthropic Batch API, with a two-pass generate-then-review process. Move this into the repo so it's idempotent, re-runnable and cheap, and so it handles only the stories that changed.
• Build a glossary and style layer: Hebrew terms, names of sages and sources, and terms that must never be translated. Add automated QA checks (completeness, glossary adherence, length drift, broken formatting) plus a sampling workflow for native-speaker review.

3. Generation in the user's language

• Reflections, bridge text, the three practices (Echo, Naming, Walking) and Path arcs are generated by Claude through shared prompt modules in our Supabase edge functions. Make them produce native, natural output in the target language. That means writing in the language directly, not translating English after the fact. Our existing rules must still hold, e.g. each practice carries a Hebrew term with its meaning explained, now explained in the user's language.
• Build a per-language evaluation harness so we can check quality before a language goes live and catch regressions when prompts change.

4. Multilingual matching

• Today, language-validation detects the language of the user's input and blocks anything that isn't English. Replace that gate with detection and routing.
• Story matching uses OpenAI text-embedding-3-large over pgvector. Measure how well non-English input retrieves the right English-indexed stories. Then decide between cross-lingual matching, per-language embeddings, or a hybrid, and back the decision with numbers.

5. Audio

• Stories and reflections are read aloud by ElevenLabs voices. Audio is currently stored per voice (audio_urls), so it has to become per voice and per language. Pick voices for each language, and plan batch pre-rendering, storage, cost and backfill.

6. Server-side copy

• Move push notification copy (including our Shabbat-aware scheduling), transactional and lifecycle emails, and database-driven home-screen messages out of the code and into a locale-aware string system with proper plurals and date formats.

7. Safe rollout

• Several app versions are live at the same time, and older builds can't be changed. Every change you make must stay backward compatible: English stays the default, current RPC signatures stay the same, and each language can be switched on independently behind a flag.
• Track cost and quality for each language: tokens, TTS credits, fallback rate and generation failures.

Our stack

• Backend: Supabase: Postgres (RLS, RPCs, pgvector, jsonb, pg_cron) and 50+ Deno/TypeScript edge functions
• AI: Anthropic Claude (Messages and Batch APIs, prompt caching), OpenAI embeddings, ElevenLabs TTS
• Data/scripts: Python and Node
• Other: RevenueCat, Resend, Expo Push/FCM. The app is Expo/React Native, but you won't need to work in it.

You'll be a fit if you have

• 5+ years of backend engineering, with strong PostgreSQL: schema design, migrations on live data, RLS, stored functions, and performance tuning.
• Production TypeScript (Deno or Node) and solid Python for data pipelines.
• Shipped LLM features to production, beyond prototypes: prompt design, structured output, batch processing, cost control, and above all evaluation. You know how to tell whether output in a language you don't speak is good.
• Built backend internationalization before: locale negotiation, fallback chains, ICU/CLDR plurals and dates, and translation workflows with versioning.
• Worked with embeddings and vector search, and can design a retrieval evaluation.
• Care about keeping production running: backward compatibility, feature flags, and rollouts that can be undone.
• Write clearly. Decisions here get written down before they get built.

Nice to have

• Experience with ElevenLabs or other TTS pipelines.
• Supabase-specific experience.