Senior fullstack (dotnet/angular/azure)

[icecoder]

Software Developer – Remote (South Africa) – SaaS Compliance Platform
Monthly salary: ZAR 110 000


About us
I represent a Danish-based company offering a SaaS integrated Quality Management solution covering compliance .
We enable companies in regulated markets to “get and stay compliant” by digitalising incident handling, document control, risk management, supplier management, pre- and post-market workflows and more. mybluelabel.com+1
You’ll be joining a company that is established, commercially successful and focussed on growing further.


The role
We’re looking for a capable developer who can take full ownership of our platform’s day-to-day support and also drive a major refactoring/migration project. Key aspects:

• You will provide ongoing operational support : troubleshoot issues, maintain application stability, respond to customer support tickets or escalations, and ensure the SaaS platform remains available and performant.
• You will lead the transition/refactoring of the legacy code-base: currently built on .NET Framework and Angular hosted in Azure + Azure DevOps. We intend to migrate to GitHub for version control and move to a modern front-end (Angular latest version or equivalent) and upgrade back-end as needed.
• You must be comfortable working in a relatively unstructured environment: the product is mature but has accumulated technical debt and the business needs someone who can think outside the box, pick up loose ends, introduce rigour, propose improvement paths and deliver.
• You’ll work fully remote (flexible hours) but will coordinate with our Danish team, so good communication in English is required.
• This role is crucial for our next phase of growth, so we expect someone with initiative, ownership and a strong track-record.

Requirements

• Strong experience on .NET (legacy code included) and willingness/ability to upgrade to .NET 9 or equivalent newer stack.
• Proven experience with Angular (legacy) and modern Angular (or comparable front-end frameworks) — you should be comfortable refactoring front-end code, migrating versions, restructuring modules.
• Experience with Azure cloud services (hosting, app services, SQL, DevOps pipelines) and willingness to migrate version control to GitHub and adopt newer CI/CD workflows.
• Experience providing support/maintenance to live SaaS applications (customer-facing): bug-fixing, monitoring, SLA adherence, patching, deploying updates.
• Able to thrive in a less-structured environment: you’ll encounter legacy code, technical debt, unclear documentation, and you’ll need to map out your own path for improvements.
• Excellent English communication skills (written + spoken).
• Self-starter attitude, ownership mindset, comfortable working remotely with minimal supervision.
• Extensive experience working with LLMs or AI-code-assist tools (e.g., Cursor or comparable) — you will be expected to integrate and use these tools daily to boost productivity, code quality and accelerate refactoring/support.

Nice to have

• Experience with regulatory compliance software, quality management systems, document management etc.
• Familiarity with ISO standards (9001, 13485, 27001), FDA or MDR/UKCA compliance workflows (though not strictly required).
• Experience migrating from Azure DevOps to GitHub, or modernising legacy enterprise SaaS products.

What we offer

• Competitive remote salary (ZAR 110k/month) for the right candidate.
• Fully remote
• Opportunity to take ownership, shape a critical piece of infrastructure, and grow with a company that helps regulated businesses digitise compliance.
• Significant autonomy, visible impact and responsibility — you will be a key player.

How to apply
Send your CV + brief cover letter confirming you meet the key requirements to [email protected] with subject “SA Software Developer – Compliance Platform”. Please include details of relevant projects: legacy refactoring, .NET Framework to newer .NET upgrade, front-end migrations, Azure hosting etc.

 

[Benedict A55h0le not]

There is a mentality problem with companies thinking they need "fullstack" developers. It is far more beneficial today to have dedicated cloud/backend developers and dedicated frontend developers. Fullstack is a 100% disadvantage for the company when there is more than 1 developer. It is old school and dumb. It is a clear sign of some stupidity at the higher up decision making level:

Key disadvantages of "full stack" developers include the risk of being a "jack of all trades, master of none," constant context switching that hinders productivity, heavy workloads leading to burnout, and difficulty in keeping up with the rapid, vast technological changes across the entire stack.

For the Developer

• Lack of Deep Expertise: While they have broad knowledge, a full stack developer's expertise in any single area (e.g., front-end, back-end, databases) will likely not be as deep as that of a dedicated specialist. This can be a disadvantage when tackling highly complex or niche problems.
• Constant Learning Curve: The technology landscape evolves at a rapid pace on all fronts. Juggling the need to stay current with new tools and best practices for both front-end and back-end simultaneously can be overwhelming and time-consuming.
• Burnout and Stress: The demanding nature of managing multiple aspects of a project, often with tight deadlines and high expectations, increases the risk of exhaustion and burnout.
• Context Switching: Frequently switching between different programming languages, frameworks, and mindsets (e.g., from visual UI design to server-side logic and data management) can kill productivity and focus.
• Responsibility Overload: Full stack developers often bear the primary responsibility for the entire application's functionality and bug fixing, which can be a significant burden.
• Perception as "Master of None": Some employers, especially in larger companies, may prefer deep specialists for specific roles, viewing generalists as less qualified for advanced positions within a narrow field.

Pros and Cons of being a fullstack developer : r/dotnet - Reddit
Jun 27, 2021 — * Context switching. It can kill productivity. * You get pulled in to more stuff. It is hard to say no, it really is. ...

For the Company

• Potential for Suboptimal Code: Due to a broader, but less deep, skill set in each area, a full stack developer might not always write the most optimized or elegant code for a specific layer compared to a specialist.
• Difficulty with Large-Scale Projects: As applications scale and become more complex, specialized teams often become necessary to manage the intricacies of each component effectively. A single developer may struggle to manage the entire application at a large scale.
• Hiring Challenges: It can be difficult to find a truly proficient and experienced full stack developer who is an expert in all areas. Vague job descriptions and high salary expectations can complicate the recruitment process.
• Single Point of Failure/Bus Factor: Relying heavily on one full stack developer for an entire project can create a bottleneck and significant problems if that developer leaves the team or goes on vacation.

 

[OCP]

I can see why you are looking for a full stack dev

 

[icecoder]

dd

I can see why you are looking for a full stack dev

Hahaha Thats really funny I think that more of a frontend issue. This my private domain and not related to the company at all and does not reflect their current implementation....well maybe in some sense

 

[Herr der Verboten]

So full stack vibe coder

 

[icecoder]

There is a mentality problem with companies thinking they need "fullstack" developers. It is far more beneficial today to have dedicated cloud/backend developers and dedicated frontend developers. Fullstack is a 100% disadvantage for the company when there is more than 1 developer. It is old school and dumb. It is a clear sign of some stupidity at the higher up decision making level:

Key disadvantages of "full stack" developers include the risk of being a "jack of all trades, master of none," constant context switching that hinders productivity, heavy workloads leading to burnout, and difficulty in keeping up with the rapid, vast technological changes across the entire stack.

For the Developer

• Lack of Deep Expertise: While they have broad knowledge, a full stack developer's expertise in any single area (e.g., front-end, back-end, databases) will likely not be as deep as that of a dedicated specialist. This can be a disadvantage when tackling highly complex or niche problems.
• Constant Learning Curve: The technology landscape evolves at a rapid pace on all fronts. Juggling the need to stay current with new tools and best practices for both front-end and back-end simultaneously can be overwhelming and time-consuming.
• Burnout and Stress: The demanding nature of managing multiple aspects of a project, often with tight deadlines and high expectations, increases the risk of exhaustion and burnout.
• Context Switching: Frequently switching between different programming languages, frameworks, and mindsets (e.g., from visual UI design to server-side logic and data management) can kill productivity and focus.
• Responsibility Overload: Full stack developers often bear the primary responsibility for the entire application's functionality and bug fixing, which can be a significant burden.
• Perception as "Master of None": Some employers, especially in larger companies, may prefer deep specialists for specific roles, viewing generalists as less qualified for advanced positions within a narrow field.

Pros and Cons of being a fullstack developer : r/dotnet - Reddit
Jun 27, 2021 — * Context switching. It can kill productivity. * You get pulled in to more stuff. It is hard to say no, it really is. ...

For the Company

• Potential for Suboptimal Code: Due to a broader, but less deep, skill set in each area, a full stack developer might not always write the most optimized or elegant code for a specific layer compared to a specialist.
• Difficulty with Large-Scale Projects: As applications scale and become more complex, specialized teams often become necessary to manage the intricacies of each component effectively. A single developer may struggle to manage the entire application at a large scale.
• Hiring Challenges: It can be difficult to find a truly proficient and experienced full stack developer who is an expert in all areas. Vague job descriptions and high salary expectations can complicate the recruitment process.
• Single Point of Failure/Bus Factor: Relying heavily on one full stack developer for an entire project can create a bottleneck and significant problems if that developer leaves the team or goes on vacation.

Thanks for your detailed feedback. I want to clarify my perspective, because I believe context matters a lot in these discussions.


You’re absolutely right that hiring someone labelled “full-stack” can be problematic in many companies. The issues you raised overloading one person, lack of depth, constant context switching are all valid and well-documented, and I am living in that world too.

That said, in our case the situation is different. We have an 8-year-old SaaS product built on legacy tech (legacy front-end + back-end) with no large specialist team behind it right now. I have about 25 years’ experience as a developer (you can check my LinkedIn: https://www.linkedin.com/in/davidwinslow/) and I’ve seen both models work and fail. In this company at this time we need someone who spans the stack rather than someone who only lives in one layer.


Here’s what we expect:

• They’ll be responsible for day-to-day live system support: bug fixes, performance issues, updates, customer tickets.
• They’ll step into a legacy code-base and incrementally refactor it. No green-field perfection. Pragmatic improvements matter more.
• Good practices count: readable code, tests where reasonable, reliable deployments. But we’re not asking for reinventing the wheel or perfection in architecture.
• They’ll work remotely, with autonomy, with our Danish team in coordination.

In short, we’re looking for breadth plus pragmatism, not perfection in every layer. If a specialist front-end or back-end role made sense for us right now, we’d go that route but it doesn’t.


If you’re comfortable with that kind of role and mindset, great. If your interest is in a highly specialised domain, or you prefer working in a context where you’re not supporting a legacy system while refactoring, then we’re probably not the best fit.


Thanks again for your time and insights.

 

[B-1]

Thanks for your detailed feedback. I want to clarify my perspective, because I believe context matters a lot in these discussions.


You’re absolutely right that hiring someone labelled “full-stack” can be problematic in many companies. The issues you raised overloading one person, lack of depth, constant context switching are all valid and well-documented, and I am living in that world too.

That said, in our case the situation is different. We have an 8-year-old SaaS product built on legacy tech (legacy front-end + back-end) with no large specialist team behind it right now. I have about 25 years’ experience as a developer (you can check my LinkedIn: https://www.linkedin.com/in/davidwinslow/) and I’ve seen both models work and fail. In this company at this time we need someone who spans the stack rather than someone who only lives in one layer.


Here’s what we expect:

• They’ll be responsible for day-to-day live system support: bug fixes, performance issues, updates, customer tickets.
• They’ll step into a legacy code-base and incrementally refactor it. No green-field perfection. Pragmatic improvements matter more.
• Good practices count: readable code, tests where reasonable, reliable deployments. But we’re not asking for reinventing the wheel or perfection in architecture.
• They’ll work remotely, with autonomy, with our Danish team in coordination.

In short, we’re looking for breadth plus pragmatism, not perfection in every layer. If a specialist front-end or back-end role made sense for us right now, we’d go that route but it doesn’t.


If you’re comfortable with that kind of role and mindset, great. If your interest is in a highly specialised domain, or you prefer working in a context where you’re not supporting a legacy system while refactoring, then we’re probably not the best fit.


Thanks again for your time and insights.

For context what does this mean? Is that a technical team or a business team?

• They’ll work remotely, with autonomy, with our Danish team in coordination

 

[icecoder]

For context what does this mean? Is that a technical team or a business team?

• They’ll work remotely, with autonomy, with our Danish team in coordination

Its a business team, and a remote technical team that have carried the solution this far but dont have the technical skills to carry the project further. I have been part of the auditing of the current solution and will be part of the journey going forward in a capacity that is yet to be decided. What I can say is that its an amazing business team that have had a bad ride with their choice of development team in the past, and despite that they managed to build a succesful business.

 

[B-1]

Its a business team, and a remote technical team that have carried the solution this far but dont have the technical skills to carry the project further. I have been part of the auditing of the current solution and will be part of the journey going forward in a capacity that is yet to be decided. What I can say is that its an amazing business team that have had a bad ride with their choice of development team in the past, and despite that they managed to build a succesful business.

Sorry for the 3rd degree but if there is a small tech team I think its worth mentioning them and how the role will interact with them.
Right now it reads as if this person is a one man band that is expected to do 1st line support, fix operational issues, manage release pipelines, architect the new solution, set roadmap for migrations, implement the new solution (frontend, middleware, back end, release) etc etc.
If there is a small team and its mainly oversight, leadership, stepping in technically to fill gaps and improve progress that is quite a different picture.

 

[Herr der Verboten]

Sorry for the 3rd degree but if there is a small tech team I think its worth mentioning them and how the role will interact with them.
Right now it reads as if this person is a one man band that is expected to do 1st line support, fix operational issues, manage release pipelines, architect the new solution, set roadmap for migrations, implement the new solution (frontend, middleware, back end, release) etc etc.
If there is a small team and its mainly oversight, leadership, stepping in technically to fill gaps and improve progress that is quite a different picture.

but claude will give him/her/it the power of 10 devs!!!

 

[icecoder]

Sorry for the 3rd degree but if there is a small tech team I think its worth mentioning them and how the role will interact with them.
Right now it reads as if this person is a one man band that is expected to do 1st line support, fix operational issues, manage release pipelines, architect the new solution, set roadmap for migrations, implement the new solution (frontend, middleware, back end, release) etc etc.
If there is a small team and its mainly oversight, leadership, stepping in technically to fill gaps and improve progress that is quite a different picture.

Hi B-1,


That’s a really fair question and I appreciate you pushing for clarity (on a saturday no less ) . It’s not a one-man-band setup, but it is a hands-on role.


There’s a remote technical team that currently maintains the platform and handles basic fixes, but their depth in architecture and modernisation is limited. The person we’re hiring will step in as the technical anchor — someone who can stabilise, guide, and gradually refactor the system while still being close enough to the code to understand what’s really going on.


It’s less about doing everything personally and more about taking ownership and steering direction: deciding what to fix, what to refactor, how to modernise, and when to lean on external or support resources. Over time, this person will likely help shape how we expand or restructure that technical team, but for now, they’ll need to be comfortable wearing a few hats while bringing structure and discipline to what exists.


I’ve worked in software for about 25 years and I know the danger of overloading one developer! this isn’t that. The focus is on leadership through example and incremental improvement, not hero coding.


Thanks again for the thoughtful challenge it’s exactly the kind of conversation that helps frame the role clearly.

 

[Herr der Verboten]

Hi B-1,


That’s a really fair question and I appreciate you pushing for clarity (on a saturday no less ) . It’s not a one-man-band setup, but it is a hands-on role.


There’s a remote technical team that currently maintains the platform and handles basic fixes, but their depth in architecture and modernisation is limited. The person we’re hiring will step in as the technical anchor — someone who can stabilise, guide, and gradually refactor the system while still being close enough to the code to understand what’s really going on.


It’s less about doing everything personally and more about taking ownership and steering direction: deciding what to fix, what to refactor, how to modernise, and when to lean on external or support resources. Over time, this person will likely help shape how we expand or restructure that technical team, but for now, they’ll need to be comfortable wearing a few hats while bringing structure and discipline to what exists.


I’ve worked in software for about 25 years and I know the danger of overloading one developer! this isn’t that. The focus is on leadership through example and incremental improvement, not hero coding.


Thanks again for the thoughtful challenge it’s exactly the kind of conversation that helps frame the role clearly.

"pushing for clarity"

Ohai chatgpt / grok

 

[Dark Agent]

I was once offered a role at a software development company that sounded promising — until I found out I was the only actual developer on the team. The only other “technical” staff were two people who had just completed a 6-month Node.js course and had about 6 months of experience.


The company was convinced they were innovating, but the reality was very different. I built a solid program for them — fully functional, cleanly structured, 100% unit tested, and scalable. After about three months, the boss called me a liar and claimed “nothing was getting done.”


One day, we needed to implement CSS changes. I integrated a clean library and handled it properly, but I didn’t have hosting access. Later that same day, one of the junior guys hosted the library I built and claimed credit for the work — and I was blamed for “doing nothing.”


I eventually resigned. They brought in a consultant afterward, and he confirmed exactly what I had said:

The code was 100% solid, there were no implementation issues, and the problem was simply that the person responsible for integration didn’t know how.

I moved on, and honestly, it was the best decision or rather say my worst 4 months of my life.
For the past two years, I’ve been working on massive-scale legacy-to-.NET 8 upgrades — building everything to be .NET 9 and .NET 10 ready.


So when people talk about these “one-man full-stack” roles, I completely agree: you need to be honest about what you’re actually looking for, what the team structure is, and what technical roles exist. A single developer can do a lot — but not everything, all at once.

I’m a .NET Core specialist, and I also work comfortably with Angular, Flutter, and React.
I know HTML and CSS, though I’ll admit — I’m not a designer. I was advised back in my third year of university to never become a web designer and I’ve stuck with that advice!

The pay you offering is more then 40% What I get, its really a good pay. The job is really interesting and challenging. Base on second post, I say you looking for Technical Lead with A solid experience in Angular and .Net Core. What will help is to break down the team and add a day to day responsibility.

 

[icecoder]

Thanks for the feedback and the "push for clariity". I have subsequently thought about the possibility of hiring more than one resource for the project, however due to the high complexity in getting the train back on track it does not make sense at this stage to hire the full team. It is however the vision to have a team of 3-4 developers composed of specialists in the areas needed (frontend,backend, devops, architecture) however it requires som fundamentals to be in place.
So this is a case of a development team being phased out and a new path needs to be created, in order for developent to take place.
I am open for suggestions to how this can be solved in other ways, including a existing team/company which the right resources to solve this.

 

[icecoder]

I was once offered a role at a software development company that sounded promising — until I found out I was the only actual developer on the team. The only other “technical” staff were two people who had just completed a 6-month Node.js course and had about 6 months of experience.


The company was convinced they were innovating, but the reality was very different. I built a solid program for them — fully functional, cleanly structured, 100% unit tested, and scalable. After about three months, the boss called me a liar and claimed “nothing was getting done.”


One day, we needed to implement CSS changes. I integrated a clean library and handled it properly, but I didn’t have hosting access. Later that same day, one of the junior guys hosted the library I built and claimed credit for the work — and I was blamed for “doing nothing.”


I eventually resigned. They brought in a consultant afterward, and he confirmed exactly what I had said:


I moved on, and honestly, it was the best decision or rather say my worst 4 months of my life.
For the past two years, I’ve been working on massive-scale legacy-to-.NET 8 upgrades — building everything to be .NET 9 and .NET 10 ready.


So when people talk about these “one-man full-stack” roles, I completely agree: you need to be honest about what you’re actually looking for, what the team structure is, and what technical roles exist. A single developer can do a lot — but not everything, all at once.

I’m a .NET Core specialist, and I also work comfortably with Angular, Flutter, and React.
I know HTML and CSS, though I’ll admit — I’m not a designer. I was advised back in my third year of university to never become a web designer and I’ve stuck with that advice!

The pay you offering is more then 40% What I get, its really a good pay. The job is really interesting and challenging. Base on second post, I say you looking for Technical Lead with A solid experience in Angular and .Net Core. What will help is to break down the team and add a day to day responsibility.

Thanks for the feedback, I replied further down, but you are absolutely right that this is more of a technical lead / architectual role, which also can roll up the sleeves and take action on doing the initial phasing out of the existing dev team. This means at some point access to source control / azure resources. dns etc will need to be cut of and the company essentially will be on their own until we have a plan put in place to move forward and hire the correct resources.