Add placeholder and high-level statement for Senior Engineer role

[tathamoddie]

To start to introduce the technical/alternate career path, @mridsdale16 and I have worked on the high-level statement for a "Senior Engineer" role.

More discussion at https://readify.slack.com/archives/general/p1432181660000133

Adding this in to MadSkillz so we can then flesh out the skills + behaviours underneath it

[aaronpowell]

Would this fit into the same file or should it be separate? The way I read Consulting.md is that it's hierarchical, D -> SD -> SC -> LC -> PC.

Have SE in the place that it sits makes me read it as SE is a step between SC and LC, which I don't think is the intention.

[RaphHaddad]

@tathamoddie is it possible to make placeholders for all the new technical roles? Not just SE?

I think they are

SE == Senior Engineer LE == Lead Engineer PE == Principle Engineer.

[tathamoddie]

See https://readify.sharepoint.com/the-way-we-work/Pages/Consulting%20Roles.aspx for the stepping path and further titles. For now, we just want to start with defining SE. We're about to post something around what comes after SE (and wanting to define that a bit later). So, consciously just the one placeholder for now.

[tathamoddie]

@aaronpowell If you can see a nice way to represent it in the file structure / order that is similar to the https://readify.sharepoint.com/the-way-we-work/Pages/Consulting%20Roles.aspx layout, I'm all ears.

[aaronpowell]

@tathamoddie Engineering.md

[RaphHaddad]

how about Consulting.html

[tathamoddie]

@aaronpowell Updated accordingly.

[aaronpowell]

Cool, like that way, as it indicates that there is a break in the streams.

[tathamoddie]

I wouldn't want to be the guy responsible for crossing the streams.