Senior MuleSoft Developer

What's my role?

As a Senior MuleSoft Developer, you will be responsible for developing tasks, which may include enhancements to existing applications, the creation of new applications, or a combination of both. Additionally, you will be responsible for providing production support and should possess troubleshooting and debugging experience. In-depth knowledge of the Anypoint platform and Anypoint Studio is essential for this role.

What is my responsibility?

Following best practices for development/build, Quality of the Task you have executed, Ownership of the task, Task timelines and communication with the team.

How do I do my job?

Minimum:

• Develop efficient code or configuration, maintaining best practices
• Use MuleSoft-hosted Anypoint Platform to take a basic API through all the steps of its lifecycle: design, build, deploy, manage, and govern.
• Use Anypoint Studio to build, test, and debug basic integrations and API implementations.
• Connect to a range of resources including databases, files, web services, SaaS applications, and messaging queues.
• Perform basic data transformations using DataWeave 2.0.
• Control event flow and handle errors.
• Perform unit testing on your Tasks to validate the functionality.
• Run code review sessions to get feedback and implement the suggested changes.
• Troubleshoot and Debug errors/exceptions and provide production support.
• Accomplish the tasks you are given, roughly in the estimated time frame and without careless errors.
• If you need clarification for any portion of the Task, ask for it upfront.
• Be prepared to provide updates and blockers on the daily scrum call.
• If you need guidance, reach out immediately to your Consultant or IA. Do not wait until they reach out to you.
• Learn quickly and implement.

Good:

• Think about whether there is a better way to solve the problem than the exact Task you have been assigned and take that back to your team.
• Think about whether your Task addresses all possible scenarios or if there are any that need to be accounted for. Take that back to your team.
• Advanced unit testing to cover exception scenarios
• Regression testing to ensure that you did not break any other functionality.
• Research new areas proactively.
• Help your Consultant out by jumping onto demo calls and driving the demos.
• Preferably MCD certified

How do I know if I am doing a good job?

Red Flags:

• You are taking significantly longer than the generic estimate and are not able to articulate why.
• You say your Task is done, but your team always finds flaws in them.
• Your PM has to follow up with you multiple times to get updates from you.
• Best practices in the implementation are not represented in the code.

Green Flags:

• Your team feels comfortable giving you additional responsibility and more complex Tasks.
• Your team starts inviting you to client calls.
• Your team leans on you to research new areas or build quick PoCs.

How do I prepare for my next role?

As a developer, the typical next role for you would be that of a Consultant. As a Consultant, you go from executing Tasks to designing Solutions and breaking them down into Tasks (for other developers). In order to be considered for the Consultant role, build these skill sets:

• Understand the overall project, not just the portion you built.
• Help out your Consultant by looking at requirements and designing solutions yourself.
• If you don't understand anything, research and practice till you become an expert at it.
• Expand the breadth of your knowledge by reading up on (and practicing) new areas.
• Practice communication - asking pointed questions, responding to questions when put on the spot, articulating solutions and recommendations, etc.
• Prepare for and pass MCD L1 / L2 exams.