Junior - Intermediate Developer
Indexed description
Role
The Role We need a developer who wears multiple hats. No business analyst. No middleman. The developer IS the person who talks to the client, triages the problem, and builds the solution. Our clients are non-technical (therapists, billing staff, administrators), so the ability to communicate clearly and calmly is critical. The role breaks down into three areas:
Emergencies
- Respond to urgent production issues during EST business hours - top priority
- Diagnose and resolve outages quickly (recycling application pools, reviewing logs, tracing errors)
- Troubleshoot database issues (deadlocks, slow queries, data integrity problems) across client databases
- Basic AWS infrastructure troubleshooting (EC2 instance management, monitoring, restarts)
- Communicate with affected clients while resolving the issue
- Handle support tickets during business hours (billing issues, client bugs, feature requests)
- Get on Google Meet calls with clients to understand their needs (AI records the call)
- Triage: determine if it is a bug fix or a feature that requires prototyping
- Communicate directly with non-technical stakeholders
- Build quick HTML prototypes using AI tools (Cursor, Claude Code) for client review and approval
- Build approved features into the existing platform
- Work with the existing development team to maintain and improve the codebase
Our platform has evolved over many years and includes some legacy technologies. You do not need prior experience in every item below. You need to be comfortable jumping into unfamiliar code and figuring things out using AI tools and good engineering judgment.
- C# ASP.NET MVC (.NET Framework)
- Classic ASP (legacy portions of the platform)
- Microsoft SQL Server (per-client databases)
- jQuery, DevExpress (UI component library), Entity Framework
- AWS (EC2, S3)
- Git / GitHub
- AI tools available on our dev server: Claude Code, Cursor
- Strong generalist .NET or full-stack developer (junior to mid-level)
- Strong English - this person will be on calls with US clients regularly
- Fluent with AI development tools as a daily force multiplier (Cursor, Claude Code, or similar). This is a hard requirement, not a nice-to-have.
- Comfortable learning and working in unfamiliar codebases
- Comfortable debugging databases (SQL queries, performance, data investigation)
- Self-starter who asks good questions when stuck and communicates clearly while working
- Genuinely enjoys helping people solve problems (if they hate tickets, this is not the role)
- EST hours
- Comfortable with legacy technologies, outdated code, and hidden complexity
- Comfortable working directly on production databases and live environments
- A senior architect who wants to redesign everything
- Someone who avoids support work
- A developer who needs a BA to translate client needs
- Someone who gives general answers without technical depth
- A candidate whose resume matches our stack exactly but cannot operate in unfamiliar code
- Experience with healthcare billing, insurance claims, or compliance-driven software
- Familiarity with multi-tenant architectures (separate databases per client)
- Background working with government or state-funded programs
- Experience with legacy .NET Framework codebases
- Demonstrated ability to ramp up quickly on unfamiliar technologies using AI tools
- Responsible and proactive approach to work, ensuring team consultation before making decisions or implementing changes
- Awareness that small changes in complex code can have significant unintended consequences
- Agency pre-screen. Verify strong English, generalist .NET skills, and real AI tool fluency. Ask the candidate to describe a recent task where AI tools meaningfully accelerated their work and what they did when the AI got it wrong.
- Conversational interview with Aaron. Fit, communication style, understanding of the role, comfort with client-facing work.
- Paid practical test. Candidates we advance get access to our remote dev server (no prod access, sandbox environment with real code). They work through 2-3 realistic tasks over a defined window (3-4 hours, paid). Claude Code and other AI tools are available on the server. We review how they worked, not just whether they solved the problem.
- Speed of orientation in unfamiliar code
- AI tool fluency as a real working force multiplier
- Debugging approach and problem-solving instincts
- Communication while working, especially when stuck
- Judgment about when to ask for help vs. push through
Create a free Caio profile to unlock more results and save your role and location preferences.
Unlock free search