Full Stack Software Engineers

Role Overview

We are seeking experienced Full Stack Software Engineers to join two small, agile engineering teams supporting a large, established .NET-based healthcare application. A mix of legacy and modern technologies, helping maintain and modernize the system while contributing to new feature development. The teams operate in a generalist model, meaning all engineers are expected to handle both backend and frontend tasks as needed. This role is ideal for engineers who are hands-on, flexible, and comfortable working in a collaborative, pragmatic environment where incremental improvements are the norm.

Job Responsibilities

Develop and maintain features in a .NET (C#)-based application.
Work with legacy ASPX Web Forms and participate in their gradual migration to React.
Handle tickets independently based on Jira tasks.
Write, debug, and optimize SQL queries.
Occasionally make small updates or bug fixes in Python (rare).
Use the AWS Console to troubleshoot errors, review logs, and verify service statuses.
Collaborate with a generalist team on end-to-end solutions spanning frontend and backend.
Participate in a rotating on-call schedule (approx. every 5 weeks, mostly during U.S. business hours).
Optional: assist with maintenance tasks for a React Native iOS app (small, infrequent updates).

Edit Job Responsibilities
Requirements
Technical Requirements:

Strong experience in .NET (C#) development.
Familiarity with ASPX Web Forms or willingness to learn quickly.
Professional experience with React.js in a production environment.
Solid working knowledge of SQL and relational databases
Experience using Git for version control.

Soft Skills & Team Fit:

Collaborative and easy to work with—low ego, adaptable mindset
Open to working with and improving legacy codebases.
Willing to gradually contribute to modernization initiatives.
Self-sufficient with the ability to pick up tickets and contribute quickly
Comfortable with ambiguity and evolving priorities in a small-team environment.

Technologies:

– .NET (C#)
This is the main technology used in both teams.
Candidates must be familiar with working in the .NET ecosystem using IDEs like Visual Studio.
They should be able to execute tasks based on Jira tickets independently.

– ASPX Web Forms
Legacy frontend code is often written in ASPX, and engineers will frequently work with it.
While it’s not mandatory to be an expert, basic familiarity or willingness to learn quickly is expected.

– React.js
Used for frontend development, particularly during migration projects from ASPX to React.
Candidates must have professional experience with React, though it doesn’t need to be expert level.
React work is part of team-based migration and incremental feature updates.

– SQL
Backend datastore is SQL-based.
Proficiency is strongly preferred, especially for writing queries and understanding data structures.

– Git
Git is the version control system in use.
Familiarity is expected; the team assumes all candidates should know Git.Edit Requirements

Main Technologies
Edit Main Technologies
Technologies will be a Plus
Nice-to-Have Skills

– Experience with Python for basic scripting and small updates.
– Ability to navigate the AWS Console for basic debugging and log review.
– Familiarity with React Native and Apple App Store deployments.
– Exposure to monitoring tools like Splunk or Datadog.

– Python
Used occasionally across all teams for small bug fixes or enhancements.
Active development in Python is rare, and lack of experience can be compensated with on-the-job learning.

– AWS (Amazon Web Services)
The entire application runs on AWS.
Candidates should be able to navigate the AWS Console for tasks like checking logs, verifying service status, or handling deployment-related incidents.
Common services mentioned: EC2, logs (specific services not deeply detailed).

– React Native
Used in one team’s maintenance-only mobile app (iOS).
No new development currently; tasks are limited to minor updates and App Store deployments.
Familiarity is a plus, but not required—training can be provided.

– CI/CD and Monitoring Tools
The team uses tools like Splunk and Datadog for application monitoring.
These are nice to have, not mandatory.
CI/CD systems are in place, but specifics (e.g., GitLab, Jenkins) weren’t mentioned.Edit Technologies will be a Plus

Location & Time Zone:
Remote work, with full-time availability required during U.S. East Coast hours
(EST/EDT).

On-Call Expectations:
Shared among 5 people, rotation is approximately once every 5 weeks.
Most incidents happen during U.S. business hours.
On-call includes monitoring Slack channels and participating in incident resolution.
Full training provided; engineers will not be placed on-call during the first ~3 months.

Interview Process:
Behavioral & Communication Interview
Technical Interview, including:
Light algorithm questions
Live coding session with team members

Start Timeline:
Candidates are needed as soon as possible.

Environment & Tech Use Context
The codebase is described as 10–11 years old, with incremental updates and teambased refactors.
Work involves both feature development and legacy maintenance.
Expect a 60% backend / 40% frontend split across tasks.
Engineers will need to be flexible and willing to touch both ends of the stack.
There is no strict specialization; all engineers are generalists.

Where to Apply

You can apply by clicking the button below:

Full Stack Software Engineers

Company

Contact

Subscribe