Backend Software Developer

Job Title: Backend Software Developer
Engagement Type: Contract
Location: Remote Willing to work in MST Time Zone
Duration: 6+ Months
Visa: USC Only ( NEED Genuine)
Rate:$55/hr.




LINKEDIN MUST BE OLD




MUST HAve - anyone from nuclear background .. companies like Westinghouse, Oklo, PPL, duke power etc..




About the Project
High-priority platform supporting the National Reactor Innovation Center (NRIC) at Idaho National
Laboratory. It's a nuclear design and safety-basis platform built for NRIC Launch Pad developers,
guiding users step-by-step through design and regulatory authorization workflows for advanced
reactor demonstration projects. The goal is to translate DOE nuclear safety and licensing guidance
into a structured, navigable software workflow - reducing the complexity of the authorization and
safety-basis development process.
This is a fast-moving, prototype-first engagement. We prioritize incremental delivery, parallelized
front-end/back-end development, and rapid iteration over long planning cycles.




About the Stack
The current prototype is being built in FastAPI + SQLAlchemy 2.0 (typed Mapped/mapped_column
ORM style) + PostgreSQL, and that's our working default. However, backend architecture decisions
for this project are still open. If you have deep expertise in a different backend stack (e.g.,
Node/TypeScript, Django, Go, .NET) and a strong case for it, we're genuinely open to that direction.
What You'll Work On
Design and build out the backend data layer for a multi-module platform (Design, Safety, Review
modules) - schema design, ORM/data-access layer, and migrations, in whichever stack we land on.
Build and document REST API endpoints to support CRUD-heavy form-driven screens (e.g.,
authorization pathway tracking, deliverable roadmaps, stakeholder/role assignment).
Design and implement integration adapters to external systems of record - notably DOORS
(requirements) and Windchill (design/document data) - treating those systems as source of truth
and mirroring/caching their data into ARIES rather than duplicating ownership.
Collaborate closely with a small team (front-end developer, engineering SMEs, end users).
Participate in schema and API design decisions, including data provenance tracking for records
mirrored from external tools.
Weigh in on backend architecture/stack decisions early in the engagement if you believe a different
approach better serves the project's goals.
Minimum Requirements
3+ years of professional backend software development experience.
Strong hands-on experience with Python, FastAPI (or comparable async Python web framework),
and SQLAlchemy (2.0-style typed ORM preferred).
Solid working knowledge of PostgreSQL, including schema design, migrations (Alembic or
equivalent), and relational modeling for entities with many-to-many and cross-module relationships.
Experience designing and building RESTful APIs consumed by a separate front-end application
(React/TypeScript).
Comfort working in a fast-iteration, prototype-driven environment with evolving requirements.
Ability to read and translate technical/regulatory documentation into structured data models.
Preferred Qualifications
Experience integrating with enterprise engineering tools such as IBM DOORS Next and PTC
Windchill via API.
Familiarity with data provenance / system-of-record patterns (mirroring external data without
becoming its owner).
Experience with Docker and containerized deployment workflows.
Experience with Alembic migrations specifically.
Familiarity with Pydantic for request/response schema validation in FastAPI.
Prior experience working alongside a React/TypeScript front-end team, including agreeing on API
contracts early to enable parallel development.
Working Style Expectations
Comfortable working independently with minimal day-to-day oversight, while communicating
proactively about design tradeoffs.
Able to produce clean, incrementally reviewable work (small PRs/migrations) rather than large,
infrequent deliveries - this project values fast feedback loops.
Responsive to a small, cross-functional team cadence (expect regular but lightweight syncs, not
heavyweight process).