About the role

Analytical contributor designing and building shared storage infrastructure for Autodesk Construction Solutions. Engaging in backend software engineering and API management to enhance project outcomes.

Responsibilities

Build and maintain the Structured Record Access API layer: the abstraction between engineering teams and the managed Postgres and DynamoDB fleet across all production regions
Implement and operate Kafka-based semantic event emission from the SRS abstraction layer, replacing raw CDC stream consumption downstream
Contribute to the schema catalog and runtime connection management service, giving teams consistent metadata access without environment-specific configuration
Write code-first schema migrations with mandatory test coverage and validated rollback, deployed via the database platform API
Build developer tooling and SDKs that reduce per-team provisioning and schema management toil
Continuously assess cloud platform needs across the SRS fleet, identify risks and gaps before they become incidents
Drive improvements in capacity management, monitoring/alerting, query tuning, load optimization, and data replication for reporting workloads
Create and institutionalize best practices and health models across the database fleet, using observability tooling and AWS automation to enforce standards consistently
Consult directly with engineering teams and group leads on storage readiness and risk
Build a network of storage champions across the division to distribute expertise and raise the floor on database hygiene
Curate training opportunities for engineering teams in database technologies and management
Provide tactical support during production emergencies

3+ years of backend software engineering in a distributed systems or platform context
3+ years of Kubernetes architecture at scale
5+ years of Terraform experience
5+ years of experience with cloud data technologies
Strong hands-on experience with Postgres or DynamoDB: schema design, query optimization, migrations
ORM experience in a backend platform context, particularly patterns that intercept entity state changes to drive semantic event emission
Exposure to event streaming (Kafka, Kinesis, or equivalent) in a production system
Experience building and operating APIs in AWS: REST or gRPC, not just consumption
Proficiency in Python, Go, or Java; fluency in one and willingness to work in others is acceptable
Comfortable operating in a multi-region, multi-partition AWS environment
Strong communication and organizational skills