We are looking for a "Reliability-First" Engineer
to help us build and maintain robust backend data pipelines. We aren't looking
for someone who just writes scripts that work on the "happy path." We
need an engineer who cares deeply about what happens when things fail, how the
code is maintained over time, and how data moves through the system with
absolute integrity. In this role, you will work directly with our Lead Data
Engineer. This is a unique opportunity for a disciplined developer to own
meaningful tasks while receiving direct mentorship in a high-stakes data
environment.
This is a part-time role offering 10 to 25 hours per week.
We offer a flexible schedule, but you must have some overlap with our Lead
Data Engineer (on PHT timezone) for collaboration and feedback loops
Future Potential: We are looking for a long-term partner. For the right
candidate, this role has a clear path toward a full-time position as our data infrastructure grows.
Build for Failure: You will design and implement data pipelines with a "build for failure" mindset. This involves utilizing robust error handling, validation, and logging to ensure the system is self-healing or, at the very least, straightforward to debug when issues arise.
Maintain Code Quality: You are expected to maintain high code quality by writing clean, readable, and strictly typed Python. Your work should be easily understood and modified by your teammates—and your future self—long after it has been deployed.
Own the Logic: You will manage backend data flows using modern Python practices to ensure logic is sound from the start. You will take responsibility for ensuring that small mistakes in the code do not escalate into massive downstream issues for the rest of the system.
Test the Edge Cases: Testing must go beyond the "happy path." You will write meaningful tests that verify how the system behaves under pressure and in various failure states, ensuring reliability even when the unexpected happens.
Collaborate Directly: As the right hand to our Lead Data Engineer, you will take full ownership of your assigned tasks. This includes providing consistent status updates, communicating blockers early, and being accountable for the final outcome of your work.
Python Fundamentals: You possess a deep understanding of functions, classes, data structures, and async/await. You know not just how to use these core concepts, but specifically why they are the appropriate choice for a given technical problem.
The Engineer’s Mindset: You utilize proper type hinting to make your code self-documenting and reliable. Your error handling is always intentional; you never blindly suppress exceptions, but instead handle failures with purpose. Furthermore, you implement useful logging and can systematically hunt down the root cause of an issue through disciplined debugging practices.
Clean Architecture: You maintain a firm commitment to meaningful naming conventions, reasonable code structure, and the avoidance of unnecessary complexity to ensure the system remains maintainable for the entire team.
Testing Discipline: You have proven experience testing important system behaviors and complex edge cases, demonstrating that you know how to verify a system’s integrity well beyond the "happy path.
"The "Accountability" Factor: You take full responsibility for your tasks from start to finish. If a mistake occurs, you are honest about it, you take the lead on fixing it, and you ensure that you learn from the experience to improve future performance.
Problem-Solving Logic: You avoid the "Google and Copy" trap. Instead, you seek to understand the underlying "why" behind the code and the true root cause of any bug you encounter, approaching problems with step-by-step logic.
Communication: You possess the ability to explain technical problems clearly and concisely. You recognize that staying silent is the biggest blocker in a remote environment and prioritize providing proper updates and communicating blockers early.
Initiative & Curiosity: You naturally look beyond the immediate ticket on your desk. You show an interest in understanding how and why things work, often exploring ways to improve reliability, maintainability, or overall code quality.
Teachable: You view feedback as an essential tool for growth. You show a genuine curiosity to learn, accept technical critiques well, and actively look for ways to improve your craft as you progress.
No Attachments
E-commerce store. The home depot of golf cart parts, accessories, and lithium batteries. Our mission is to leverage our talents and resources to build best in class customer experiences
See current jobs and employer profileE-commerce store. The home depot of golf cart parts, accessories, and lithium batteries. Our mission is to leverage our talents and resources to build best in class customer experiences
See current jobs and employer profile