Full Stack Engineer

Gridtractor • Full-time • Remote (California, United States, US) • $130k - $150k / year • 5m ago

Company Description

Gridtractor is a team of experts at the intersection of agriculture, energy, and technology, with a mission to electrify the world's fleet of tractors and diesel-powered farm equipment. By transitioning to electric power, farmers can produce their own energy, buy from the grid when prices are low, store energy in batteries, and even sell back to the grid when prices are high. Gridtractor aims to create sustainable and profitable farming practices by turning tractors and farm equipment into multi-purpose tools for the grid.

Role Description

This is a full-time remote role for a Full Stack Engineer at Gridtractor. The Full Stack Engineer will be responsible for both front-end and back-end web development, as well as software development. They will be involved in the entire development process, from designing and implementing user interfaces to developing server-side logic. This role requires a strong understanding of full-stack development and expertise in Cascading Style Sheets (CSS).

Qualifications

Experience building a full stack software solution using .NET 6+ - This is defined as having experience building the following on:
Implement document (nosql) databases like CosmosDb and MongoDb
How to design middle layer of application architecture and how to design and expose API services (onion application architecture experience preferred but not required)
How to design and implement unit and integration testing
Experience building UI in a full stack solution using Blazor, Angular or React (Blazor preferred but not required)
Knowledge of component-based design helpful but not required
Experience with UI frameworks like MudBlazor, Radzen helpful but not required (paid vendors like DevExpress and Telerik are acceptable too)
Experience with state management and SignalR helpful
Experience with UI display for different device form factors helpful
Knowledge in designing and implementing a Document (nosql) database is required
(Azure CosmosDb experience preferred but not required):
Knowledge of how to design entities and their relationships including partitioning (data modeling)
Knowledge of how to version entities over time
Some knowledge on how to move data from one environment to the another
Some knowledge of data integration helpful (Cloud-based tool knowledge like Azure Data Factory or AWS Glue is helpful but required)