Appian Corporation
Database Engineer
About this role
Appian seeks a Database Engineer to design and maintain scalable data architectures supporting mission-critical government systems. You'll migrate legacy databases to modern cloud platforms, optimize performance, and implement enterprise-grade database solutions for Department of War initiatives.
What you'll do
- Design logical and physical data models aligned with customer contract requirements
- Analyze legacy database structures and plan migrations to cloud platforms
- Convert legacy stored procedures, triggers, and functions to target-compatible languages
- Establish and manage ETL processes to extract, transform, and load legacy data
- Configure enterprise database clusters and tune database objects for optimal performance
- Integrate database objects into CI/CD pipelines and maintain source control for database code
What they're looking for
- SQL and relational database management (RDBMS)
- NoSQL databases and query languages (MQL, CQL)
- Database platforms: Microsoft SQL Server, Oracle, PostgreSQL, MariaDB, Snowflake, Databricks
- Cloud platforms: AWS and Azure
- ETL design and data migration
- Database performance tuning and indexing
- Python, Java, or C# for scripting
- DevOps tools: Jenkins, Azure DevOps, CI/CD pipelines
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Appian Corporation
Appian builds a low-code platform for designing and deploying enterprise applications with embedded AI, workflow automation, and intelligent agent capabilities. The company is hiring software engineers, security specialists, consultants, and support professionals to build custom solutions, secure AI-powered systems, support cloud operations, and deliver digital transformations for enterprise and government clients.
- Website
- appian.com
Likely interview questions
- Describe your experience migrating legacy databases to cloud platforms—what challenges did you face and how did you resolve data compatibility issues?
- How would you approach analyzing a legacy Oracle database to identify migration risks before moving it to PostgreSQL?