Placement papers | Freshers Walkin | Jobs daily: Software Engineer II at C2FO (Leawood, KS)


Search jobs and placement papers

Software Engineer II at C2FO (Leawood, KS)

C2FO is working to deliver a future where every company in the world has the capital it needs to grow. Our technology provides an easy, low-cost way for businesses of all sizes to increase cash flow by receiving early invoice payments. Since 2008, C2FOs online marketplace and innovative financial products have accelerated payments by more than one billion days for companies in over 180 countries.

Named one of Forbes Fintech 50, C2FO provides more than $1 billion in working capital each week for hundreds of thousands of businesses. C2FO has more than 400 employees worldwide, with headquarters in Kansas City and locations throughout Europe, Asia Pacific and Australia. For more information, visit http://bit.ly/2vaGXwm.

Job Summary:

An Engineer II will enter this level capable of taking well-defined tasks and completing them in a way that is considered by the team to be high-quality with supervision from more senior team members. The progress through this level focuses on taking tasks of increasing complexity, scope, and importance and completing them with very high quality with a lessening need for manager/tech lead oversight. This level is the bread-and-butter level of engineering growth. Engineers at this level focus on becoming great engineers, learning how to set high-quality bars for their work without sacrificing productivity.

All engineers at and above this level should religiously follow stated best practices for the team without excessive hand holding. Engineers at this level will continue to make mistakes but should be improving the speed at which they learn from these mistakes. By the time an Engineer II is ready to be promoted, they will have focused on some technology as their expertise and become capable of mentoring interns and new engineers in these areas. They will start to participate more in the technical design process, often with guidance from senior engineers. Engineers at this level are assumed to be continually making steady progress on tasks that are assigned to them and know when to ask for help when they are blocked. They can own their independent small-to-medium features through from technical design to launch. They are capable of prioritizing the work in front of them and able to make forward progress, avoiding the temptation to focus on unimportant details or excessive bikeshedding.

The impact at this level focuses on task completion and depth in a small area of the codebase. Engineers at this level should be capable of releasing responsibilities for their area as well as on-call support for simple incidents in areas with which they are familiar. They communicate well and are capable of delivering feedback to peers and their manager. When given a task with unclear requirements, they know how to ask for clarification and vet all assumptions before work starts to reduce the need for re-work. They understand how their work fits into the larger picture for their team, and use this to identify conflicting requirements to their tech lead and product manager. An essential focus of this level is developing empathy for the users of their software, whether they be internal employees, customers, or other developers on the team. A team member at this level is seeking out the context they need to understand the why of a particular feature and nurturing this empathy via that understanding.

They communicate well and are capable of delivering feedback to peers and their manager. When given a task with unclear requirements, they know how to ask for clarification and vet all assumptions before work starts to reduce the need for re-work. They understand how their work fits into the larger picture for their team, and use this to identify conflicting requirements to their tech lead and product manager. An essential focus of this level is developing empathy for the users of their software, whether they be internal employees, customers, or other developers on the team. A team member at this level is seeking out the context they need to understand the why of a particular feature and nurturing this empathy via that understanding.

Responsibilities:
* Integrate data from various back-end services and databases
* Actively participate in design thinking iterations to design new solutions
* Write clean, high-quality, high-performance, maintainable code
* Work collaboratively as part of a cross functional team that includes designers, customers, testers, internal stakeholders and other software engineers
* Research and stay current in mobile and web development practices and trends


by via developer jobs - Stack Overflow
 

No comments:

Post a Comment