Software Development Engineer
4h ago⚠️ Before applying, please carefully review all the job requirements
- Location:
- Remote - ALL USA, United States
- Work Arrangement:
- Remote
- Experience:
- REQUIRED
- Job Type:
- Full Time
- Salary:
- $129,500 to $157,400
- Posted:
- 2026-10-10
- Share:
- share to twittershare to facebookshare to linkedin
Job Overview
- A new opening is available for a Software Development Engineer. The work arrangement is listed as remote. The salary mentioned in the listing is $7. The requirements point towards PostgreSQL, SQL databases, REST APIs, Git and GitHub, .NET / C#, Artificial Intelligence and LLMs. The experience level listed is 25 years. For general context: REST APIs let the front end and back end of an application exchange data in a structured way. Git tracks code changes so teams can work on the same project without overwriting each other. Read the details below carefully and use the application link on this page if the role matches your profile.
What These Requirements Mean in Practice
- ★ PostgreSQL: A relational database where data lives in related tables; the work usually involves writing SQL and designing schemas.
- ★ SQL databases: Working with tables, relationships and queries to store and retrieve structured data.
- ★ REST APIs: Designing and consuming HTTP endpoints so a front end, mobile app or another service can exchange data.
- ★ Git and GitHub: Tracking changes, working on branches, opening pull requests and resolving conflicts so a team can share code safely.
- ★ .NET / C#: Building applications and web APIs with C# on the .NET platform.
- ★ Docker: Packaging an application and its dependencies into containers so it runs the same way everywhere.
- ★ AWS: Using cloud platform services for hosting, storage and databases instead of managing physical servers.
- ★ Artificial Intelligence: A general understanding of how AI systems learn from data, where they are useful, and where they can be unreliable.
Skills to Brush Up Before Applying
- ★ PostgreSQL: joins, indexes, transactions and constraints
- ★ SQL databases: SELECT, JOIN and GROUP BY, primary and foreign keys, normalisation basics
- ★ REST APIs: HTTP methods and status codes, authentication basics such as tokens, validation and error responses
- ★ Git and GitHub: branching and merging, pull requests and code review, resolving merge conflicts
- ★ .NET / C#: C# fundamentals, ASP.NET Core Web API, Entity Framework basics
- ★ Docker: Dockerfile basics, images versus containers, docker compose
- ★ AWS: core compute and storage services, permissions and access control, basic deployment
- ★ Artificial Intelligence: supervised versus unsupervised learning, common real-world use cases, limitations and bias
Who May Be a Good Fit for This Role?
- This role may be suitable for candidates who match the skills and experience described in the requirements. Those who are comfortable with PostgreSQL, SQL databases, REST APIs, Git and GitHub, .NET / C#, Artificial Intelligence and LLMs and enjoy building practical projects may find the requirements a good match. A remote arrangement may suit people who work well independently and communicate clearly in writing. This is editorial guidance only, and the employer makes the final decision on suitability.
Application Tips
- Applicants may want to highlight relevant experience with PostgreSQL, SQL databases, REST APIs and Git and GitHub in their CV. Because version control is mentioned, a GitHub profile with a few well-described repositories can make your skills easier to verify. If you have used AI tools or built small projects with language models, briefly describe what you built and how you checked the results. Since applications are sent by email, use a clear subject line that includes the role title and keep your message short, with your CV attached. A short, role-specific summary at the top of your CV usually reads better than a generic profile. These are general tips, not requirements stated by the employer.
Prepare for Your Interview
- These suggested questions can help you prepare for an interview by focusing on the skills, responsibilities, and technical areas relevant to this role. They are for preparation only and are not confirmed employer questions.
- Q: What is a transaction, and why do ACID properties matter?
- Q: What is the difference between INNER JOIN and LEFT JOIN, and when would you use each?
- Q: How would you handle authentication and input validation for a REST API you are building?
- Q: What is the difference between git merge and git rebase, and when would you use each?
- Q: How would you build and secure a Web API in .NET?
- Q: What problem does Docker solve, and how do an image and a container differ?
- Q: How do joins and indexes affect query performance in PostgreSQL?
- Q: How would you design tables and relationships for a simple job-board application?
- Q: How do you stay organised and communicate clearly when working remotely?
Apply by email: careers@envestnet.com