Full-Stack Engineer

Level: Middle Full-Stack Engineer, suitable for someone with at least three years of development experience and the independence to work effectively in a remote environment.

Required skills: Strong Python, backend or web application development, APIs, Git/GitHub, databases and data modeling, debugging, testing, secure coding, and clear English communication; JavaScript, TypeScript, React, cloud, AI automation, and third-party integrations are advantageous.

Relevant tasks: Building and maintaining applications, internal tools, automations, APIs, and integrations; troubleshooting production issues, improving reliability and performance, participating in code reviews and technical design, and collaborating on practical product solutions.

How would you design a Python-based API for processing prescription intake workflows?

I would separate the API, business logic, and integration layers, using clear request validation, structured error handling, and idempotent workflow operations. I would also add authentication, logging, automated tests, and monitoring to support reliability and secure handling of pharmacy data.

How would you integrate with a third-party pharmacy or insurance API?

I would isolate the integration behind a dedicated client or service, handle authentication and token refresh securely, and implement timeouts, retries with backoff, and clear error mapping. I would also log useful diagnostic information without exposing protected or sensitive data.

How would you make an automation workflow idempotent?

I would assign each incoming task a unique business or external identifier and persist its processing state. Before performing an action, the system would check whether that step was already completed, preventing duplicate submissions when requests are retried.

How would you model data for prescription, fax, and insurance-processing workflows?

I would identify core entities such as prescriptions, documents, patients, pharmacies, insurance requests, and workflow events, then define normalized relationships and appropriate indexes. I would preserve status history and audit information separately so the current state is easy to query while changes remain traceable.

How would you troubleshoot a production issue in a Python service?

I would first assess impact using logs, metrics, traces, and recent deployment history, then reproduce the issue safely if possible. After applying a targeted fix or rollback, I would add a regression test and document the root cause and preventive actions.

What practices would you use to secure healthcare-related applications?

I would enforce least-privilege access, encrypt data in transit and at rest, validate inputs, manage secrets through a secure secret store, and avoid sensitive data in logs. I would also maintain audit trails, dependency updates, code reviews, and automated security checks.

How would you test an API that coordinates multiple external services?

I would use unit tests for business rules, contract tests for API schemas, and integration tests with mocked or sandboxed third-party services. I would also test timeouts, retries, malformed responses, duplicate requests, partial failures, and recovery behavior.

How would you improve the performance and reliability of a workflow-processing system?

I would measure bottlenecks first, then use asynchronous jobs, queues, database indexes, caching, and batch processing where appropriate. Reliability would be improved with durable job state, retry policies, dead-letter handling, health checks, and monitoring of latency and failure rates.

How would you structure a full-stack feature using Python and React or TypeScript?

I would define a clear API contract first, then implement the backend validation and business logic independently from the frontend presentation. On the frontend, I would use typed API models, predictable state management, loading and error states, and component-level tests.

How would you use AI-assisted development tools responsibly on this team?

I would use them to accelerate boilerplate, test generation, debugging, and code exploration, but I would review all output for correctness, security, maintainability, and licensing concerns. I would never provide confidential pharmacy or patient data to an unapproved tool, and every change would still go through tests and code review.

TJM Labs builds AI-driven automation that helps pharmacies streamline prescription intake, fax processing, insurance workflows, and other repetitive tasks. As a Full-Stack Engineer, you’ll build internal tools, automation solutions, APIs, integrations, and product features while troubleshooting issues and improving reliability. The stack centers on Python, Git/GitHub, databases, and web applications, with opportunities to use JavaScript, TypeScript, React, cloud tools, and AI-assisted workflows. This is a fully remote, global contract role offering competitive compensation, meaningful healthcare impact, high ownership, and strong opportunities to grow with a collaborative startup team.