[Hiring] Software Engineer I @Murj

Role Description

The best way to master a complex platform is to understand its nuances. As a Software Engineer I at Murj, you’ll be the primary investigator of our ecosystem. You will focus on resolving customer requests, squashing bugs, and clearing backlog items. This role is designed to give you a 360-degree view of the Murj platform, preparing you for deep-level feature development by making you an expert in how our system lives and breathes. Candidates based in Eastern or Central timezones are preferred.

In this role, you should be comfortable working independently, and taking the initiative to identify and address work needed but not necessarily assigned. While your initial focus will be mastering our frontend application, you will have the opportunity to gain exposure across the entire stack as you grow.

What You’ll Do

• Investigate & Resolve: Tackle bug reports, feature enhancements, and frontend maintenance tasks, ensuring a seamless experience for clinicians.
• Customer Impact: Directly address customer-requested tweaks and improvements, seeing the immediate impact of your work on their daily workflows.
• Collaborate: Work closely with our QA team to reproduce issues and our Product team to understand the "why" behind the "what."
• Modernization: Learn how to manage third-party dependencies, keeping our codebase up-to-date and free of vulnerabilities.
• Continuous Improvement: Identify patterns in recurring bugs and suggest long-term architectural improvements to prevent them.
• Deployment: Become proficient with our GitLab CI/CD pipeline and release process.
• Feedback: Iterate over your implementation by receiving feedback through code reviews or pair programming.
• Automated Testing: Write and maintain unit tests using Vitest to ensure bug fixes are durable and don't cause regressions.

What Makes You a Great Fit

• Curiosity First: You aren't satisfied with just "fixing" a bug; you want to understand the root cause and ensure it doesn't happen again.
• Adaptability: You are excited by the prospect of starting in the frontend but eventually expanding the scope of your work as the team evolves.
• Ownership: You take pride in the small wins—a UI polish or a resolved edge case—knowing they lead to a better experience for the doctors using our tools.
• Detailed Communicator: You enjoy documenting your findings and can translate complex technical bugs into clear status updates for the broader team.

What You Bring

• React Proficiency: You’ve built projects or worked professionally with React and understand its core principles.
• The Modern Tooling Kit: Experience with (or a strong desire to master) TypeScript, Vite, and MobX.
• Problem-Solving Mindset: You enjoy the "detective work" of debugging and aren't afraid to dig through logs and documentation.
• Communication Skills: You can explain technical issues clearly to non-technical stakeholders (like Product or Support).
• Quality First: You believe that code isn't finished until it's tested and verified.

Nice To Haves

• Backend Exposure: Familiarity with PHP or API design (REST/GraphQL).
• DevOps Interest: A desire to learn more about Docker, Terraform, or cloud infrastructure.
• Healthcare Tech: Experience working in a HIPAA-compliant environment or with medical data.
• CSS Mastery: A keen eye for layout, accessibility (a11y), and responsive design.
• Secure Coding Practices: Knowing best practices and/or exposure to SAST, etc.

What Success Looks Like (First 90 Days)

• In 30 Days: You have completed your first several bug fixes, successfully navigated the GitLab CI/CD pipeline, and feel comfortable navigating the frontend codebase.
• In 60 Days: You are taking ownership of "investigative" tickets independently, collaborating directly with QA to validate fixes, and contributing to code reviews for your peers.
• In 90 Days: You have a 360-degree view of the application's current frontend state. You are beginning to suggest architectural improvements and are starting to pick up "cross-over" tasks that touch our APIs or infrastructure.

Travel Expectations

• 0%: No travel required